Difference between revisions of "Inkscape Release checklist"

From Inkscape Wiki
Jump to navigation Jump to search
 
Line 9: Line 9:
  
 
#Open Development
 
#Open Development
**Implement new build system
+
#*Implement new build system
**Begin switching packaging to use new build system
+
#*Begin switching packaging to use new build system
 
#Chill
 
#Chill
**Development focuses on wrapping up
+
#*Development focuses on wrapping up
**Post inkscape-0.##-pre0.tar.gz
+
#*Post inkscape-0.##-pre0.tar.gz
**Disable features that aren't finished
+
#*Disable features that aren't finished
**Identify 'make distcheck' issues
+
#*Identify 'make distcheck' issues
**Identify remaining writing needed for Release Notes
+
#*Identify remaining writing needed for Release Notes
**Identify any release blocker bugs
+
#*Identify any release blocker bugs
**Recruit Release Wardens for Freeze
+
#*Recruit Release Wardens for Freeze
 
#Frost
 
#Frost
**Only production-ready code committed to Mainline
+
#*Only production-ready code committed to Mainline
**Finalize any major changes to platform packaging
+
#*Finalize any major changes to platform packaging
**Inkscape must pass 'make distcheck'
+
#*Inkscape must pass 'make distcheck'
**Finalize Release Notes except Known Issues
+
#*Finalize Release Notes except Known Issues
**Start an About Screen contest
+
#*Start an About Screen contest
**Post additional inkscape-0.##-pre*.tar.gz releases
+
#*Post additional inkscape-0.##-pre*.tar.gz releases
**Packagers test creating pkgs of the -pre* releases
+
#*Packagers test creating pkgs of the -pre* releases
 
#Freeze
 
#Freeze
**Stable Branch is forked from Mainline
+
#*Stable Branch is forked from Mainline
**Regular development resumes on Mainline
+
#*Regular development resumes on Mainline
**Only Release Wardens can commit to Stable Branch
+
#*Only Release Wardens can commit to Stable Branch
**Cherrypick bug fixes from Mainline to Stable
+
#*Cherrypick bug fixes from Mainline to Stable
**Complete any late work under advisement of Wardens
+
#*Complete any late work under advisement of Wardens
**Focus on release-critical bug fixing
+
#*Focus on release-critical bug fixing
**No further string changes allowed on Stable Branch
+
#*No further string changes allowed on Stable Branch
**Translators work on translations
+
#*Translators work on translations
**Finalize all extensions
+
#*Finalize all extensions
**Finalize codebase translations
+
#*Finalize codebase translations
**Finalize about screen
+
#*Finalize about screen
**Finalize Known Issues section of Release Notes
+
#*Finalize Known Issues section of Release Notes
**Finalize packaging scripts
+
#*Finalize packaging scripts
**Post additional inkscape-0.##-pre*.tar.gz releases
+
#*Post additional inkscape-0.##-pre*.tar.gz releases
 
#Release
 
#Release
**Post inkscape-0.92.tar.gz to website
+
#*Post inkscape-0.92.tar.gz to website
**Post package to launchpad project ppa
+
#*Post package to launchpad project ppa
**Post Windows build, MSI or EXE installer to website
+
#*Post Windows build, MSI or EXE installer to website
**Post MacOSX build, dmg installer to website
+
#*Post MacOSX build, dmg installer to website
**Make Debian build available in stable ppa or distribution archive
+
#*Make Debian build available in stable ppa or distribution archive
**Make Fedora build available in stable yum repository or distribution archive
+
#*Make Fedora build available in stable yum repository or distribution archive
**Post official announcements
+
#*Post official announcements
**Plan 0.##.1+ release(s), if needed
+
#*Plan 0.##.1+ release(s), if needed

Latest revision as of 01:08, 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
  2. 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
  3. 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
  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
    • 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
  5. 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