Difference between revisions of "Release Details/4.3-Release-planning"
m (Created page with '= Overview = During July 2nd, 2013 developer hangout, we came up with a plan for the long-waited 4.3 release ! >> The 4.3 release is planned fo…') |
m |
||
Line 7: | Line 7: | ||
>> Between now and the release, all nightly packages should be considered as release candidates. | >> Between now and the release, all nightly packages should be considered as release candidates. | ||
This means NO commits to the slicer svn unless they are part of a tracked bug report tagged for the 4.3 release. | This means NO commits to the slicer svn unless they are part of a tracked bug report tagged for the 4.3 release. | ||
− | (Commit | + | (Commit of type COMP or STYLE are not expected to be associated with an issue.) |
>> Every TTT (Tutorial Testing Tuesday), developers are expected to test as many tutorial as possible and report the results on [[Documentation/Labs/TutorialTesting/4.3-Release|this page]]. | >> Every TTT (Tutorial Testing Tuesday), developers are expected to test as many tutorial as possible and report the results on [[Documentation/Labs/TutorialTesting/4.3-Release|this page]]. |
Latest revision as of 18:29, 3 July 2013
Home < Release Details < 4.3-Release-planningContents
Overview
During July 2nd, 2013 developer hangout, we came up with a plan for the long-waited 4.3 release !
>> The 4.3 release is planned for September 2nd.
>> Between now and the release, all nightly packages should be considered as release candidates. This means NO commits to the slicer svn unless they are part of a tracked bug report tagged for the 4.3 release. (Commit of type COMP or STYLE are not expected to be associated with an issue.)
>> Every TTT (Tutorial Testing Tuesday), developers are expected to test as many tutorial as possible and report the results on this page.
>> As soon as possible, developers are expected to review their assigned bug targeted for 4.3 and (1) tell us if they won't have time to fix it before August 20th. Reminder will be send weekly. (2) contact the reporter / developers if the issue is in feedback mode
Schedule
July 9th
TTT (Testing Tutorial Tuesday)
Developer: check assigned bugs. If you know you won't have time to fix it. Send an email at jchris [dot] fillionr [at] kitware [dot] com pieper [at] bwh [dot] harvard [dot] edu
Developer hangout - Review dashboard Markup module: Expected Slicer integration (See 4.3 Release FAQ) Unit/Dimensionality feature: Review integration status (See 4.3 Release FAQ)
July 16th, 23rd, 30th
TTT (Testing Tutorial Tuesday)
Developer: check assigned bugs. If you know you won't have time to fix it. Send an email at jchris [dot] fillionr [at] kitware [dot] com pieper [at] bwh [dot] harvard [dot] edu
Developer hangout - Review dashboard
August 6th, 13th, 20th
TTT (Testing Tutorial Tuesday)
Developer: check assigned bugs. If you know you won't have time to fix it. Send an email at jchris [dot] fillionr [at] kitware [dot] com pieper [at] bwh [dot] harvard [dot] edu
Developer hangout - Review dashboard - GREEN dashboard expected
August 26th
Create 4.3 wiki pages (Jc)
Copy midas data into 4.3 folder (Jc)
August 27th
TTT (Testing Tutorial Tuesday)
Developer: check assigned bugs. If you know you won't have time to fix it. Send an email at jchris [dot] fillionr [at] kitware [dot] com pieper [at] bwh [dot] harvard [dot] edu
Developer hangout - Review dashboard - GREEN dashboard expected
September 2nd
Tag repository
Create 4.3 packages
September 4th
Eventually create a patch or tweak release
Release FAQ
Can I quickly merge the major feature (depending on refactoring of core functionality) I have been working on for month ?
Starting today and until the release is completed, no feature or UI changes should be introduced into Slicer trunk unless it is on the 4.3 roadmap and has been discussed on a hangout or on the slicer-devel list.
http://na-mic.org/Bug/roadmap_page.php
What the status regarding the new "Markup" module, will it be part of the release ?
Markup module will be integrated before July 9th and will be associated to a "Preview" category. Doing so will allow extension developer to depends on it while keeping the current UI consistent with existing tutorials.
What the status regarding the "Unit / dimensionality" functionality ?
Before July 9th, we will have a better idea of both the work required to finalize the work and also the implication on the core functionality of Slicer. This will allow us to decide if the current work should be integrated or not.
As a user or developer, if you believe this is a critical feature, make sure to let us know before July 9th.
See here for more details.