[Design] Last Call - 0.7 alpha non-code deliverables plan

[Sheila Mooney]

I sent an email a couple of weeks ago about the expectations around  
non-code deliverables for our 0.7 alpha releases. Since work on Alpha  
2 has officially started, I want to close on the requirements for the  
non-code release goals so we can factor this into the schedule with  
everything else. Based on the minimal feedback we got so far, this is  
the proposal we want to move forward with.

Proposal:

+ 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 "alpha1", alpha2"  
etc.

+ The main release number and the download link (big button) on the  
main page would NOT change. It would only change if there was another  
0.6.x. Instead there would be a secondary link below the "big button"  
that points to a download of the 0.7alphax.

Rationale: There has been some debate about whether we want to  
replace the main download link with the alpha release and whether  
it's practical or necessary to have a 0.6.x if we are wanting  
dogfooders to get the latest alpha. First of all, the alpha is not an  
official release. Although we want to have the bar really high on  
these alphas, there are some fundamental differences in the  
completeness of the packaging. I think it makes sense, to keep a link  
to whatever the last official release is. If we change the numbering  
on the main page and the "big button" download, this implies we need  
to update the main page text, the readme, developer docs etc. This  
then turns into a major non-code release project and this is not  
practical to do every 2 months. We would give the user a choice to  
get the last official version or something more experimental and up  
to date.

+ A news section or news link (design TBD) would be added to the main  
project page to highlight the alpha release and associated  
documentation.

+ 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, screen shots etc. for an alpha release.  
The existing demos/screens shots for 0.6 would remain on the project  
page.

+ 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.

Please send replies to the list by end of day Monday (Mar 6th).

Sheila


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060303/935accc9/attachment.htm