Menu

ReleaseCheckList

Joseph Koshy

About

This page lists the steps needed to prepare the source tree for a release. See also: [Releases].

Steps

  1. Ensure that trunk/ builds and passes tests on all target platforms.
  2. Turn on version control system keyword expansion for source files:
    • Each source file should have a svn:keywords property, containing the string "Id".
    • Each source file should contain a $Id$ line, placed in the appropriate context.
  3. If a new branch is needed, create an SVN branch under branches/ with the appropriate branch name.
    On this branch:
    • Modify the invocation of the toolchain version script to reflect the new branch name.
    • Modify the release notes and build instructions to describe the branch. Keep the minor version number for the release upto-date.
  4. Build and test the branch.
  5. Tag the source tree for the release.
  6. Prepare a source tarball using svn export.
  7. Upload the tarball to SF.Net's file release system.
  8. Upload the test logs to the project's test-log archive.
  9. Update news items:
    • Add a news item to SF.Net's "project news" feed.
    • Update the entry on FreeCode. (FreeCode has become "read-only").
  10. Update the wiki:
    • Create a wiki page for the release.
    • Update status of components on the main page.
  11. Note the release date in the [AdminChanges] wiki page.

Related

Wiki: AdminChanges
Wiki: Releases

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.