Difference between revisions of "Inkscape Release checklist"

From Inkscape Wiki
Jump to navigation Jump to search
(Created page with "Is there a checklist for the pre/release steps? Sort of. See: *http://inkscape.13.x6.nabble.com/0-92-2-plan-td4978988.html *http://inkscape.13.x6.nabble.com/inkscape-0-92-2pre...")
 
Line 7: Line 7:
 
For major releases:
 
For major releases:
 
*https://inkscape.org/en/develop/next-release/
 
*https://inkscape.org/en/develop/next-release/
 +
 +
#Open Development
 +
**Implement new build system
 +
**Begin switching packaging to use new build system
 +
#Chill
 +
**Development focuses on wrapping up
 +
**Post inkscape-0.##-pre0.tar.gz
 +
**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 Freeze
 +
#Frost
 +
**Only production-ready code committed to Mainline
 +
**Finalize any major changes to platform packaging
 +
**Inkscape must pass 'make distcheck'
 +
**Finalize Release Notes except Known Issues
 +
**Start an About Screen contest
 +
**Post additional inkscape-0.##-pre*.tar.gz releases
 +
**Packagers test creating pkgs of the -pre* releases
 +
#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
 +
**No further string changes allowed on Stable Branch
 +
**Translators work on translations
 +
**Finalize all extensions
 +
**Finalize codebase translations
 +
**Finalize about screen
 +
**Finalize Known Issues section of Release Notes
 +
**Finalize packaging scripts
 +
**Post additional inkscape-0.##-pre*.tar.gz releases
 +
#Release
 +
**Post inkscape-0.92.tar.gz to website
 +
**Post package to launchpad project ppa
 +
**Post Windows build, MSI or EXE installer to website
 +
**Post MacOSX build, dmg installer to website
 +
**Make Debian build available in stable ppa or distribution archive
 +
**Make Fedora build available in stable yum repository or distribution archive
 +
**Post official announcements
 +
**Plan 0.##.1+ release(s), if needed

Revision as of 01:06, 10 August 2017

Is there a checklist for the pre/release steps? Sort of. See:

formalized checklists

For major releases:

  1. Open Development
    • Implement new build system
    • Begin switching packaging to use new build system
  1. Chill
    • Development focuses on wrapping up
    • Post inkscape-0.##-pre0.tar.gz
    • 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 Freeze
  1. Frost
    • Only production-ready code committed to Mainline
    • Finalize any major changes to platform packaging
    • Inkscape must pass 'make distcheck'
    • Finalize Release Notes except Known Issues
    • Start an About Screen contest
    • Post additional inkscape-0.##-pre*.tar.gz releases
    • Packagers test creating pkgs of the -pre* releases
  1. 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
    • No further string changes allowed on Stable Branch
    • Translators work on translations
    • Finalize all extensions
    • Finalize codebase translations
    • Finalize about screen
    • Finalize Known Issues section of Release Notes
    • Finalize packaging scripts
    • Post additional inkscape-0.##-pre*.tar.gz releases
  1. Release
    • Post inkscape-0.92.tar.gz to website
    • Post package to launchpad project ppa
    • Post Windows build, MSI or EXE installer to website
    • Post MacOSX build, dmg installer to website
    • Make Debian build available in stable ppa or distribution archive
    • Make Fedora build available in stable yum repository or distribution archive
    • Post official announcements
    • Plan 0.##.1+ release(s), if needed