0.7 Alpha Non-Code Release Process
This page describes the process for pulling together all of the non-code pieces for each individual alpha release. Since these alphas are frequent and represent partially implemented features, we want to keep the release overhead as minimal as possible. We will not be spending the time we normally do on fine-tuning changes to the landing page or adding the depth of information we have in support of a full release. The goal is to make very minimal changes to the main landing page and text and instead have secondary pages for most of the information. The full non-code release process will be in place when we release 0.7. The following is the proposal we closed on for landing page requirements for alpha releases.
Proposal:
- The alpha changes will be limited to the landing page (and subsequent pages) and wiki etc. We will not have a new welcome note or modify anything in the About Chandler dialog (the version number is updated automatically). The icon, look and feel will all stay the same.
- The chandler.osafoundation.org would continue to be used as the project page for Chandler and updated per alpha release (detailed below).
- We will update the Chandler splash screen to say "0.7alpha1", 0.7alpha2" etc.
- The main release number on the main page timeline would not change. The text and screenshots will also stay the same. The download link will switch from a one-click download to a link for a secondary download page that gives the user a list of versions to download (ie: more stable 0.6.1 and less stable 0.7alpha2). This page would have to explain the differences between the versions and a migration path for users that want to upgrade. (Not sure if we want to link to a readme or just add all the info here).
- A secondary news section page would be added to the main project page to highlight the alpha release and associated documentation. Much of this information would be repeated on the download page as well so I am not sure if we need a separate page or will just link to the page above.
- Every alpha will have a self-contained readme page with information. The level of content is similar to the milestone report cards we had for 0.6 milestones.
- There is a link to any relevant documentation.
- There is a list of features that work, don't work or are experimental.
- There is no detailed step-by-step instructions on how to use certain features.
- Major bugs and regressions are listed.
- There are no special demos for each alpha release. We may try and add in some screen shots of new features although these will in no way be a blocker for the release.
- The alpha release will be announced on the lists and the blog
- Developer documentation (if appropriate) will be scheduled for the alpha release like any other feature. We will not consider the lack of documentation a blocker for the alpha either.
Release Documentation
The following documents need to be created or updated for 0.7alpha2.
Distro/Code Items
These items or tasks are part of the distribution or code for the release.
| What | Responsibile | Review/Help | Dependency | Status | Bug# |
|---|
| Modify repository message with link to migration instructions | Sheila | Pieter/Mikeal | | Working with Bear on the right solution | |
| README.osx.txt | Sheila | Mikeal | | Coordinating with Bear | |
| README.linux.txt | Sheila | Mikeal | | Coordinating with Bear | |
| README.windows.txt | Sheila | Mikeal | | Coordinating with Bear | |
Wiki and/or Landing page items
Announcements
Existing Docs to Update
Developer Documentation
- No tasks identified for Alpha2.
The following links need to change to the 0.6 release:
- release info
- download link
- tech docs link
--
SheilaMooney - 28 Apr 2006
