[Cosmo-dev] Cosmo 0.7 release meeting notes (2007-06-14 and 2007-06-21)

[Jared Rhine]

(Apologies for any dup; my first copy did not have proper email headers).

Below are notes for the last two Cosmo 0.7 release meetings.

The notes are not in exact order; primary decisions have been pulled out 
to the top of each meeting's notes.



Thursday June 14th 2pm PDT
- This was the "release meeting kickoff" for Cosmo 0.7 release cycle.

- Decision: We decided we'd have a release meeting every week at least. 
  (In general, would be every other week, but already into 
at-least-weekly mode).  Meetings will be at 3pm Thursdays.

- Decision: General consensus that the diagram on this page:

   http://chandlerproject.org/Projects/CosmoReleaseZeroDotSeven

reflects the Cosmo 0.7 release process.  There will be a well-defined 
"feature complete" stage, after which a release will be cooked to drive 
QA testing of features.  After all issues requiring code changes have 
been resolved, we'll be at the "code complete" stage.  Release 
candidates will technically be cooked whenever we're at zero known 
issues targeted for Cosmo 0.7.

- Discussed: What is a release meeting exactly?  It differs from a 
engineering meeting by being focused on process, checklists, and 
ensuring that dev+qa+pm+service inter-group issues are discussed.  Ted 
proposes that release meetings might include design reviews during the 
design phase of future releases.

- Status: Bug councils have gone up in frequency.  Let's continue them 
on IRC, seems to be working well.

- Open issue: The "non-code deliverable" part of earlier releases hasn't 
been perfect.  We're looking to improve that with 0.7 release.  We'll 
track all non-code deliverables as bugzilla items.  (Wiki used too, but 
not authoritative).  Ted suggested looking at the Cosmo 0.6 list.  Jared 
and Sheila to meet to discuss Cosmo 0.7 non-code tracking.

- Open issue: The test specification for Cosmo 0.7 should be available 
for review and will be a "check off" item for code complete.  Mikeal and 
Jared to meet to review the QA checklists.  We need another checklist 
item to ensure all automated tests are run during validation.

- Status: There's a 10am checkin happening on IRC until feature complete 
is achieved.

- Todo: Some non-code deliverable items should be looked at to see if 
graphics or copy can be produced so as to be available as soon as devs 
are done with feature complete.



Thursday June 21st 2pm PDT
- Decision: We'll proceed with a Cosmo 0.6.1.1 release to fix 9537. 
Jared to coordinate.

- Decision: We'll use the "documentation" component of Cosmo's bugzilla 
for tracking most non-code deliverables.

- Decision: The standing queries on CosmoReleaseZeroDotSeven should be 
used for coordination and confirming we're at particular stages of 
release, or the queries should be updated until they are accurate and 
useful.

- Status: Bug 9537, EXDATE length support.  Have seen this on 
hub.chandlerproject.org for early adopters.  All known instances 
currently worked around, but might happen again.  Consensus was that 
people would be more comfortable having this deployed on Hub, using a 
Cosmo 0.6.1.1 release.  QA would check the change on qacosmo.

- Status: Feature complete possible for Monday 2007-06-25 but likely too 
aggressive.

- Status: Sheila has scrubbed the non-code deliverables quite a bit, and 
are close to reflecting what needs to be done specifically for Cosmo.

- Todo: Jared to check with Randy to see if "data migration" feature 
on-track for feature-complete inclusion (and not waiting to be done 
after feature complete).

- Resource: http://chandlerproject.org/Projects/CosmoReleaseZeroDotSeven 
includes decent list of bugzilla queries now, and a handy bugzilla table.

-- Jared