0.6 Non-Code Release Process

This page describes the process for pulling together all of the non-code pieces for the 0.6 release, currently scheduled for the end of November 2005.

Most of the pieces are documentation, described on the checklist below.

1. Examine the user experience for developers.
2. Examine the checklist to determine what is and what is not applicable for the release. This needs to happen several times over the release cycle, first at the end of the previous release cycle, somewhere in the middle, again about two weeks before release, and as needed after that. (Sheila/Pieter)
3. Figure out if there are any things that are not on the checklist that should be. Add them to the checklist. This should happen at the same time as the "examine the checklist" step. (Sheila/Pieter)
4. Add detailed tasks to Bugzilla. This should happen as early as possible.
5. Do the tasks. (as appropriate)

In addition, someone needs to arrange for the party. This should happen about two days before the release.

• Order food for delivery. (Blue)
• Determine who outside of OSAF staff and volunteers should get an invitation to the party. This list could include press, analysts, distinguished guests, and other "outsiders" if appropriate. (Mitch/Pieter)
• For odd-numbered releases (like 0.5), order some schwag. (Pieter)
• Remind people -- particularly those who don't regularly come into the office -- that a party is coming up.

Release Documentation Process

The following documents need to be created or updated for 0.5. The superbug task to track this is Bug:4167.

Distro/Code Items

These items or tasks are part of the distribution or code for the release. Most of these tasks are due 2-3 weeks prior to the release date.

End User Documentation

Existing Docs to Update

Developer Documentation

Katie is tracking the developer documentation deliverables for 0.6 and has created a project page for this. See link below for more details.

Other Release Tasks and Docs

The following links need to change to the 0.6 release:

• release info
• download link
• tech docs link

Schedule

• Skeleton wiki pages should exist on T minus 10 days (so can build navigation structure)
• The docs should be ready by T minus one week so that they can get an internal review.
• First pass of docs that go in the builds by November 9th, 2005
• Docs that go in the builds complete by November 16th, 2005
• First pass for docs that don't go in the build by November 16th, 2005
• Docs that don't go in the builds complete by November 29th, 2005
• Final release currently scheduled for November 30th, 2005

See ZeroPointFiveNonCodeReleaseActionItems for what we did last time.