Re: [Inkscape-devel] Proposal for release plan
Any other comments on the plan?
If there's no objections, then I'd like to propose we begin Chill in a week, on Dec 28th.
Between now and then would be a good opportunity to focus on bug triage. In particular, it would be helpful to get all bugs assigned a priority.
Bryce
On Wed, Dec 18, 2013 at 11:21:49PM -0800, Bryce Harrington wrote:
Hi all,
Josh and I have been discussing plans for the upcoming release; below is what we've come up with so far. This is loosely based on past 0.4x plans. I'll follow up this email with explanations for the major differences. Meanwhile, feedback would be appreciated.
# Period Tasks Notes
Open development. Triage and prioritize bugs report this year Itemize regression bugs found since last release
Chill. Development focuses on wrapping up Disable features that aren't finished Identify 'make distcheck' issues Identify any critical OSX/Win32 packaging issues P Identify remaining writing needed for Release Notes. Regressions Bug Hunt: 500 points H Update tutorials and other docs
Frost. Experimental Branch is forked B Mainline Branch focuses on stabilization B Only production-ready code committed to Mainline B Post inkscape-0.91-pre0.tar.gz Finalize any major changes to platform packaging P Release Notes should be >90% filled in. Inkscape must pass >90% of 'make distcheck' Start an About Screen contest A General Bug Hunt: 1500 points H Post additional inkscape-0.91-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases P
Feature Freeze. Stable Branch is forked from Mainline B Regular development resumes on Mainline. B Avoid major refactorings on Mainline. B Only bug fixes committed to Stable Branch. B Bug fixes are cherrypicked from Mainline. B Inkscape must pass 'make distcheck' String Freeze No further string changes allowed on Stable Branch. T Finalize tutorials to be shipped with release Finalize other docs included in the release Finalize about screen A Finalize Release Notes except Known Issues Translators work on translations. T Recruit Release Wardens for Hard Freeze
Hard freeze. Only Release Wardens can commit to Stable Branch B Cherrypick bug fixes from Mainline to Stable B Complete any late work under advisement of Wardens Focus on release-critical bug fixing. Finalize all extensions Finalize codebase translations T Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.91-pre*.tar.gz releases
Release. Post inkscape-0.91.tar.gz Post packages Post official announcements Plan 0.91.1+ release(s), if needed
Open development.
Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Where does checking branches to merge them with trunk fit in the scheme? In Chill or Frost? It would be good that there is more joint attention on merging branches (if possible and in good state off course) ... See also Jabiertxo Arraiza Cenoz's message in the thread "info to devel groups".
Same for merging the patches from bug reports (http://tinyurl.com/nlddjqy) ...
Bryce Harrington schreef op 23/12/2013 23:16:
Any other comments on the plan?
If there's no objections, then I'd like to propose we begin Chill in a week, on Dec 28th.
Between now and then would be a good opportunity to focus on bug triage. In particular, it would be helpful to get all bugs assigned a priority.
Bryce
On Wed, Dec 18, 2013 at 11:21:49PM -0800, Bryce Harrington wrote:
Hi all,
Josh and I have been discussing plans for the upcoming release; below is what we've come up with so far. This is loosely based on past 0.4x plans. I'll follow up this email with explanations for the major differences. Meanwhile, feedback would be appreciated.
# Period Tasks Notes
Open development. Triage and prioritize bugs report this year Itemize regression bugs found since last release
Chill. Development focuses on wrapping up Disable features that aren't finished Identify 'make distcheck' issues Identify any critical OSX/Win32 packaging issues P Identify remaining writing needed for Release Notes. Regressions Bug Hunt: 500 points H Update tutorials and other docs
Frost. Experimental Branch is forked B Mainline Branch focuses on stabilization B Only production-ready code committed to Mainline B Post inkscape-0.91-pre0.tar.gz Finalize any major changes to platform packaging P Release Notes should be >90% filled in. Inkscape must pass >90% of 'make distcheck' Start an About Screen contest A General Bug Hunt: 1500 points H Post additional inkscape-0.91-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases P
Feature Freeze. Stable Branch is forked from Mainline B Regular development resumes on Mainline. B Avoid major refactorings on Mainline. B Only bug fixes committed to Stable Branch. B Bug fixes are cherrypicked from Mainline. B Inkscape must pass 'make distcheck' String Freeze No further string changes allowed on Stable Branch. T Finalize tutorials to be shipped with release Finalize other docs included in the release Finalize about screen A Finalize Release Notes except Known Issues Translators work on translations. T Recruit Release Wardens for Hard Freeze
Hard freeze. Only Release Wardens can commit to Stable Branch B Cherrypick bug fixes from Mainline to Stable B Complete any late work under advisement of Wardens Focus on release-critical bug fixing. Finalize all extensions Finalize codebase translations T Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.91-pre*.tar.gz releases
Release. Post inkscape-0.91.tar.gz Post packages Post official announcements Plan 0.91.1+ release(s), if needed
Open development.
Thanks Kris
El mar, 24-12-2013 a las 17:22 +0100, Kris De Gussem escribió:
See also Jabiertxo Arraiza Cenoz's message in the thread "info to devel groups".
Same for merging the patches from bug reports (http://tinyurl.com/nlddjqy) ...
On Tue, Dec 24, 2013 at 05:22:47PM +0100, Kris De Gussem wrote:
Where does checking branches to merge them with trunk fit in the scheme? In Chill or Frost? It would be good that there is more joint attention on merging branches (if possible and in good state off course) ... See also Jabiertxo Arraiza Cenoz's message in the thread "info to devel groups".
Thanks for raising this point. For branches that add features and are done and ready to go, Chill is the right phase to do this review and integration. In fact it may be a good idea to include that as a distinct effort in Chill.
During Frost, branches that add features will be integrated into the experimental branch where they can be tested. If they're found to be 100% finished and solid, and get thorough testing and review to the extent we're certain they're without risk, IOW are production-ready, the branch can be promoted to mainline and included in the release.
Same for merging the patches from bug reports (http://tinyurl.com/nlddjqy) ...
These also should receive review attention during Chill, but bug fix branches are also fine to include during Frost.
These are also ok to be merged during Freeze, although note that they should be committed to Mainline, and then cherrypicked to Stable.
Same thing during Hard Freeze, except you'd merge to Mainline and a Release Warden would do the cherrypick.
Bryce
Bryce Harrington schreef op 23/12/2013 23:16:
Any other comments on the plan?
If there's no objections, then I'd like to propose we begin Chill in a week, on Dec 28th.
Between now and then would be a good opportunity to focus on bug triage. In particular, it would be helpful to get all bugs assigned a priority.
Bryce
On Wed, Dec 18, 2013 at 11:21:49PM -0800, Bryce Harrington wrote:
Hi all,
Josh and I have been discussing plans for the upcoming release; below is what we've come up with so far. This is loosely based on past 0.4x plans. I'll follow up this email with explanations for the major differences. Meanwhile, feedback would be appreciated.
# Period Tasks Notes
Open development. Triage and prioritize bugs report this year Itemize regression bugs found since last release
Chill. Development focuses on wrapping up Disable features that aren't finished Identify 'make distcheck' issues Identify any critical OSX/Win32 packaging issues P Identify remaining writing needed for Release Notes. Regressions Bug Hunt: 500 points H Update tutorials and other docs
Frost. Experimental Branch is forked B Mainline Branch focuses on stabilization B Only production-ready code committed to Mainline B Post inkscape-0.91-pre0.tar.gz Finalize any major changes to platform packaging P Release Notes should be >90% filled in. Inkscape must pass >90% of 'make distcheck' Start an About Screen contest A General Bug Hunt: 1500 points H Post additional inkscape-0.91-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases P
Feature Freeze. Stable Branch is forked from Mainline B Regular development resumes on Mainline. B Avoid major refactorings on Mainline. B Only bug fixes committed to Stable Branch. B Bug fixes are cherrypicked from Mainline. B Inkscape must pass 'make distcheck' String Freeze No further string changes allowed on Stable Branch. T Finalize tutorials to be shipped with release Finalize other docs included in the release Finalize about screen A Finalize Release Notes except Known Issues Translators work on translations. T Recruit Release Wardens for Hard Freeze
Hard freeze. Only Release Wardens can commit to Stable Branch B Cherrypick bug fixes from Mainline to Stable B Complete any late work under advisement of Wardens Focus on release-critical bug fixing. Finalize all extensions Finalize codebase translations T Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.91-pre*.tar.gz releases
Release. Post inkscape-0.91.tar.gz Post packages Post official announcements Plan 0.91.1+ release(s), if needed
Open development.
Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (3)
-
Bryce Harrington -
Jabiertxo Arraiza Cenoz -
Kris De Gussem