Lazarus 0.9.30.2 release plan

Release preparation

edit
  • Gather list of todos from developers
  • Add new LazTarget to the mantis for so we can postpone issue one release.

Bugs to be fixed

edit
  • Go over the list of new issues and determine if there are regressions among them

Things that need to be fixed before tagging:

Ask for testing

edit
  • Informally announce (IRC, mailing list) a pending release (+/- week before actual release), so that people can test for regressions. (Vincent)

Merge revisions from trunk

edit

Submitted by developer / committer

edit

The following revisions contain bug fixes and need to be merged from trunk to the fixes_0_9_30 branch.

  • 31291

Postponed merge requests

edit

User requested merges

edit

Tagging release

edit
  • Set version to 0.9.30.2 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 fixes_0_9_30 branch to tags/release_0_9_30 (Vincent)
  • Set version to 0.9.30.3 in fixes_0_9_30 branch (Vincent)

Building release

edit
  • source (Vincent)
  • html docs (Vincent)
  • chm docs (Vincent)
  • win32 (Vincent)
  • win32 for arm-wince (Vincent)
  • win64 (Vincent)
  • linux source rpm (Vincent)
  • linux i386 rpm (Vincent)
    • crosswin32 rpm (Mattias)
  • linux x86_64 rpm (Vincent)
  • linux i386 deb (Vincent)
    • crosswin32 deb (Mattias)
  • linux x86_64 deb (Vincent)
  • Mac OS X powerpc (Vincent)
  • Mac OS X i386 (Vincent)
  • Add debs to ubuntu repo (Vincent)

Announcements

edit

After release

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

Further

edit
  • Relax (all)
  • Plan next release