[General] Preview countdown: milestone review (readme! important!)

[Katie Capps Parlante]

Ok, I finally got a chance to sit down and review the Preview 
deliverables more carefully. We have many moving parts here, and I want 
to make sure we have the consolidated list of major milestones. 
(Apologies for any repetition or if I'm missing details we've already 
covered several times.)

I hit the virtual *triage* button on the Preview Countdown page, moving 
all of the DONE items out of view so that we can focus on what is left.

I'd like to refactor the remaining items to be tracking the big 
milestones that we need to watch. I need help getting them right.

http://chandlerproject.org/Planning/PreviewReleaseCountdown

Desktop Release Countdown
-------------------------

+ Code Complete (*done* July 15)
+ Code Dependent Branding/Docs (*done* July 20)
+ qacosmo running 0.7 Server (*done* July 23)
+ Zero Bug Release (eta: August 6)
    - Create 0.7 branch
    - Create daily release candidates
+ Release (eta: August 13)

Questions for desktop team:
- *Philippe* and *Aparna*, do you agree with these dates?
- Do we need to note/track any other milestones?

Server/Hub Release Countdown
----------------------------

+ Feature Complete (*done* ~July 5)
+ 0.6.1.1 on Hub (*done* July 11)
+ 0.7 Code Depenedent Branding/Docs (eta: ?)
+ 0.7 Code Complete (eta: ?)
+ 0.7 Release (+1 wk)
+ Hub updated to 0.7 (+1.5 wk)
+ Preview launch (+1 wk)

One item left for for code dependent branding/docs: final copy review

Questions for Server/Hub team:
- *Ted*, what is eta for CC?
- *Ted*, *Jared*, *Aparna*: do I have the right deltas for setting the 
remaining milestones? I'm basing this on the deltas in Sheila's list. If 
we need to renegotiate, lets do that, and do our best to have 
reality-based estimates.
- *Jared*: you are tracking a more detailed list. Any high level 
milestones that are missing?

Non-Code Deliverables
---------------------
We don't have the same dependency chain of milestones for these (with 
possibly the exception of the Hub-related items). The big ticket 
deliverables:

+ Product FAQ
+ Feature List
+ Known Issues
+ Quickstart guide
+ Screencasts
+ Release Notes

+ Hub branding/doc
+ Terms of Service, Privacy Policy
+ NOC Run Book

+ Vision document
+ OSAF FAQ
+ OSAF website (push out)
+ Sundry blog/wiki/website details

+ Announcements, blending into launch plan

*Jared*: I think I need a more clear picture of Hub branding/doc tasks, 
beyond updating the FAQ. I know we've talked about them, but a pointer 
to a clear summary would help me.

*All*: Any missing big ticket items? Perhaps the thing to do is set 
dates for completed draft and final copy.

Launch Plan Countdown: I'll integrate Ted's proposal, and follow up with 
any questions after I've done that.

Cheers,
Katie