Edgewall Software

Version 27 (modified by Christian Boos, 14 years ago) ( diff )

additional pages to check before a major release

Checklist of things to do before a release

Preparing a minor release 0.x.y

2 weeks before

Announce a string freeze on Trac-dev, so that the translators can catch up with the last changes.

Update the TracDev/ReleaseTesting page, ask for testers.

1 week before

Prepare the rc1 packages according to the procedure described below in Release steps, test and upload them.

Testing period. Only critical or no risk fixes.

Preparing a major release 0.X

1 month before

Announce a string freeze on Trac-dev.

2 weeks before

Prepare the rc1 packages.

Testing period. Only critical or no risk fixes.

Release steps

Check the t.e.o wiki

Check the source

(replace trunk below with the corresponding branches/0.1X-stable when preparing a minor releases)

Wiki related files

Other repository files

Create dist packages

Note: be sure to use Python 2.6.5 on Windows

  • Check out trunk (or the release branch) to a clean sandbox
  • Build source tarballs:
    • On Unix:
      python setup.py sdist
      
      in order to get the files in a .tar.gz, with the proper LF line endings.
    • On Windows:
      python setup.py sdist
      
      in order to get the files in a .zip, with the proper CRLF line endings. Verify with zipinfo that the content is OK as once the templates were missing…
  • Build Windows installer
    • .exe win32 installer
      python.exe setup.py bdist_wininst
      
  • Test installation on all target platforms.
    Install on a clean system. Remove any old Trac installation before testing.
  • Smoke test:
    • create an environment with trac-admin, test it with tracd
    • upgrade an environment created with the previous release' trac-admin, test it with tracd

Finalize the release

(*) not for beta or rc releases


See also: TracDev

Note: See TracWiki for help on using the wiki.