Lazarus 0.9.28 release plan

Release preparation

• Gather list of todos from developers (Vincent)
• Add LazTarget (0.9.30) to the mantis, so we can postpone issues one release.

Before tagging

• Informally announce (IRC, mailing list) a pending release (+/- week before actual release), so that people can test for regressions (Vincent)
• Create fixes_0_9_28 branch for the final fixes before tagging (Vincent)

Bugs to be fixed

Things that need to be fixed before tagging:

• A list of bugs with target 0.9.28.

Tagging release

• Set release version in fixes_0_9_28 (Vincent)
  • lazarus/ide/version.inc
  • lazarus/lcl/lclversion.pas
  • lazarus/debian/changelog
  • lazarus/lazarus.app/Contents/Info.plist
• Tag fixes_0_9_28 to tags/release_0_9_28 (Vincent)
• Increase version number in fixes to 0.9.28.1 (Vincent)

Building and uploading release

Building

• source (Mattias)
• win32 (Vincent)
• win32 based on qt (Vincent)
• win32 for arm-wince (Vincent)
• win64 (Vincent)
• linux source rpm (Mattias)
• linux i386 rpm (Mattias)
• linux x86_64 rpm (Mattias)
• linux i386 deb (Mattias)
• linux x86_64 deb (Mattias)
• Mac OS X powerpc (Vincent)
• Mac OS X i386( Vincent)

Uploading

• Ubuntu repo i386 (Vincent)
• Ubuntu repo x86_64 (Vincent)
• Set file releases from Hidden to Active on SourceForge and send email to people monitoring the package (Vincent) (I am not sure that is still necessary with the new file release system)

Announcements

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

After release

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

Further

• Relax (all)
• Plan next release (Paul)