From Lazarus-ccr

Release preparation

• Gather list of todos from developers (Vincent)
• Add LazTarget (0.9.28) 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)
  • Blog posts (Vincent)
  • Email to lazarus list (Paul)

Bugs to be fixed

Things that need to be fixed before tagging:

• A list of bugs with target 0.9.26.

Tagging release

• Set release version in trunk (Vincent)
  • lazarus/ide/version.inc
  • lazarus/lcl/lclversion.pas
  • lazarus/debian/changelog
• Tag trunk to tags/release_0_9_26 (Vincent)
• Increase version number in trunk to 0_9_27(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)

Announcements

• Wiki: downloading, installation, getting source hints (Mattias)
• List of changes: Lazarus 0.9.26 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)
• Create fixes branch (Vincent)

Further

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