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 > -------------------------------------------------------------------------------- > 1. Open development. > Triage and prioritize bugs report this year > Itemize regression bugs found since last release > > 2. 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 > > 3. 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 > > 4. 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 > > 5. 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 > > 6. Release. Post inkscape-0.91.tar.gz > Post packages > Post official announcements > Plan 0.91.1+ release(s), if needed > > 7. 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.... > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel ------------------------------------------------------------------------------ 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.... _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel