Sounds like a good plan unless everyone is away in june/july on vacation ;) -- Christoffer Holmstedt

2015-04-28 6:40 GMT+02:00 Bryce Harrington <bryce@...961...>:

Hi all,

Last release we discussed switching to a more rapid release cycle starting with 0.92. So here's a proposal for a plan to do this.

Even though it's been a short time since our last release, already we've accumulated a number of features, thanks in large part to Jabier's many LPE's:

http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92

Please make sure any other added features are included in the release notes soon.

I'd like to propose the following release plan, which is based on the 0.91 plan, but simplified and with more focus on changes to packaging, no bug hunt, and no experimental branch. We simplify to a single Freeze phase. We cut a pre0 release before starting the build system hacking, so testers will have something to test. We move the about screen contest up so it can get done sooner, and so that we can string freeze earlier to give translators time. This should drop a number of the more time consuming bits yet keep the important steps in the checklist.

Please let me know what you think, and esp. if you see some areas that need tweaking.

Bryce

# Period Tasks

1. Open development. Post inkscape-0.92-pre0.tar.gz (w/ old build sys) Start an About Screen contest Decide new unit testing system Decide new build system Implement new build system Integrate new swatch dialog Begin switching packaging to use new build system Begin tracking % translated Migrate mailing lists off sourceforge (Other bits off roadmap...)

2. Chill. Development focuses on wrapping up Disable features that aren't finished Identify 'make distcheck' issues Identify remaining writing needed for Release Notes. Identify any release blocker bugs Recruit Release Wardens for Hard Freeze

3. Frost. Only production-ready code committed to Mainline Finalize any major changes to platform packaging Inkscape must pass 'make distcheck' Ensure packaging for all platforms installs Ensure packaging for all platforms uninstalls Finalize tutorials to be shipped with release Finalize other docs included in the release Finalize about screen Finalize Release Notes except Known Issues Post additional inkscape-0.92-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases Post % translated per language for each release

4. Freeze. Stable Branch is forked from Mainline Regular development resumes on Mainline. Only Release Wardens can commit to Stable Branch Cherrypick bug fixes from Mainline to Stable Complete any late work under advisement of Wardens Focus on release-critical bug fixing. String Freeze No further string changes allowed on Stable Branch. Translators work on translations. Finalize all extensions Finalize codebase translations Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.92-pre*.tar.gz releases Post % translated per language for each release

5. Release. Post inkscape-0.92.tar.gz Post packages Post official announcements Plan 0.92.1+ release(s), if needed

6. Open development.

As far as timing goes, I'm thinking we give a few weeks to open development (step 1), and then a week each for all the subsequent steps. This would see 0.92 released in a June/July timeframe.

---

One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel