0.5 Non-Code Release Process

This page describes the process for pulling together all of the non-code pieces for the 0.5 release, currently scheduled for

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 entire user experience for developers needs to be examined. That will affect the list below. Note that the list below should also be visible in Bugzilla as the dependency tree for Bug ???.

The following documents need to be created or updated for 0.5:

Note for 0.5: someone needs to send out email with the location of this page.

The following links need to change to the 0.5 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 complete @@@5 PM 22 February.
• Docs that go in the builds complete @@@24 March 2004.
• First pass for docs that don't go in the build @@@5 PM 22 March 2004.
• Docs that don't go in the builds complete @@@5 PM 28 March 2004.
• Final release currently scheduled at @@@29 March 2004

See ZeroPointFourNonCodeReleaseActionItems for what we did last time.

-- DuckySherwood - 24 Nov 2004