From: Andreas K. <aku...@sh...> - 2015-12-10 06:46:19
|
I have now created the branch "tcllib-1-18-rc" for final work on the upcoming 1.18 release of Tcllib. Over the next few days I will run Tcllib through its testsuite, against the heads of the main branches of the Tcl/Tk core, i.e. 8.4, 8.5 and 8.6. My tests will only be done on the Linux/64 platform. I ask anybody with time on their hands to perform testing of the same on the platforms they have access to. Beyond that I will start working on the README to provide information on the overall changes since 1.17 was released (April 30, 2015). As I will go into vacation on Dec 18, i.e. Friday next week, until new year, I do _not_ expect to actually make the release in December. My hope is that I can make it happen within the first two weeks of January however. This should really give anybody with interest enough time to do their own tests and report back to me. Note: While I am willing to fix bugs in the release period I expect such bugs to - have a ticket to refer to, see http://core.tcl.tk/tcllib/reportlist (*) - have a patch fixing that bug - have that patch update the testsuite to demo bug and fix - have that patch update the documentation, if appropriate IOW, such bugs should have everything to make application and verification of the fix as easy as possible. (Ad *) To enter a ticket you must be logged in, at least as anonymous. Regarding new features, please provide either a branch which can be merged into the release, or a fossil bundle. Remember to provide a testsuite and documentation. If you have no time for both, I strongly prefer to have a testsuite. In that case the first ticket entered against the feature will be the request for the documentation. The release will be made from branch "tcllib-1-18-rc", when that branch is considered to be in a good enough shape. This means that the trunk is kept open for development, and changes on trunk may be cherrypicked over into the release as needed and/or suitable. -- So long, Andreas Kupries <aku...@sh...> <http://core.tcl.tk/akupries/> Developer @ Hewlett Packard Enterprise ------------------------------------------------------------------------------- |
From: Lars H. <Lar...@re...> - 2016-01-22 08:30:45
|
Andreas Kupries skrev 2015-12-10 07.31: > > I have now created the branch "tcllib-1-18-rc" for final work on the > upcoming 1.18 release of Tcllib. Am I right in suspecting that this release hasn't happened yet? If so, then good, since I just noticed I have a bugfix that hadn't made it into the repository (discovered the bug at a point where I didn't have commit access, and only fixed it in a local version). Will probably need a calm couple of hours with good internet connection to get the fixed code uploaded to core.tcl.tk properly. (Well, the upload is probably no big deal. But I probably need to RTFM to make sure I do the right things with fossil.) Lars Hellström > Over the next few days I will run Tcllib through its testsuite, > against the heads of the main branches of the Tcl/Tk core, i.e. 8.4, > 8.5 and 8.6. My tests will only be done on the Linux/64 platform. I > ask anybody with time on their hands to perform testing of the same on > the platforms they have access to. > > Beyond that I will start working on the README to provide information > on the overall changes since 1.17 was released (April 30, 2015). > > As I will go into vacation on Dec 18, i.e. Friday next week, until new > year, I do _not_ expect to actually make the release in December. My > hope is that I can make it happen within the first two weeks of > January however. > > This should really give anybody with interest enough time to do their > own tests and report back to me. > > Note: While I am willing to fix bugs in the release period I expect > such bugs to > > - have a ticket to refer to, see http://core.tcl.tk/tcllib/reportlist (*) > - have a patch fixing that bug > - have that patch update the testsuite to demo bug and fix > - have that patch update the documentation, if appropriate > > IOW, such bugs should have everything to make application and > verification of the fix as easy as possible. > > (Ad *) To enter a ticket you must be logged in, at least as anonymous. > > Regarding new features, please provide either a branch which can be > merged into the release, or a fossil bundle. Remember to provide a > testsuite and documentation. If you have no time for both, I strongly > prefer to have a testsuite. In that case the first ticket entered > against the feature will be the request for the documentation. > > > The release will be made from branch "tcllib-1-18-rc", when that > branch is considered to be in a good enough shape. This means that the > trunk is kept open for development, and changes on trunk may be > cherrypicked over into the release as needed and/or suitable. > |