Lazarus 0.9.30 release plan

Release preparation

• Gather list of todos from developers
• Add new LazTarget to the mantis for so we can postpone issue one release. Postponed issues can be set to 1.0 or 1.2.

Bugs to be fixed

Things that need to be fixed before tagging:

Creating branch for release

• Create fixes_0_9_30 branch
• Set version number 0.9.31 in trunk
  • lazarus/ide/version.inc
  • lazarus/lcl/lclversion.pas
  • lazarus/debian/changelog
  • lazarus/lazarus.app/Contents/Info.plist
  • open lazarus/lazarus.lpi in the IDE and change the version numbers in the project options dialog

Create snapshots for new branch

• <list of targets>

Tagging release

• Set release version in fixes_0_9_30 branch (Vincent)
  • lazarus/ide/version.inc
  • lazarus/lcl/lclversion.pas
  • lazarus/debian/changelog
  • lazarus/lazarus.app/Contents/Info.plist
  • open lazarus/lazarus.lpi in the IDE and change the version numbers in the project options dialog
• Tag trunk to tags/release_X_Y_Z (Vincent)
• Increase version number in trunk (Vincent)

Building release

• win32 (Vincent)
• source (Mattias)
• linux source rpm (Mattias)
• linux i386 rpm (Mattias)
• linux i386 deb (Mattias)
• linux x86_64 rpm (Vincent)
• Mac OS X powerpc (Vincent)

Announcements

• List of changes (Mattias)
• Mailing lists (Mattias)
• News item on www.lazarus.freepascal.org (Vincent)
• Sourceforge (Mattias)
• Freshmeat (Vincent)
• Wiki: downloading, installation, getting source hints (Mattias)
• Change IRC topic (Marc)
• New versions in Mantis (Marc)

After release

• Make sure snapshots are created correctly for the new version (Vincent)

Further

• Relax (all)
• Plan next release