[Cosmo-dev] Cosmo release meeting notes from 2007-08-02

[Jared Rhine]

Below are the meeting notes from the Cosmo release meeting held 2007-08-02.


Decisions
- We only need probably 4 days after Cosmo 0.7 release before Hub is
   Preview ready (1 day after Cosmo 0.7 to update Hub, 3 days of
   watching 0.7 in production in case something breaks).

- The PTO-entry Hub blocking tickets are large blockers, but not
   enough to roll a pre-0.7 Hub update.

- The "ZBR" (Zero Bug Release) milestone tracked by the Chandler
   Desktop team is equivalent to our "code complete" milestone.

- Ted will track the "hub-admin" alias to provide customer support
   coverage for Jared.

- We'll do a bug council right after this meeting.


Discussion
- ted: we're about 5 days worth of bugs away from code complete, with
   matthew currently on critical path.  Ted will follow up to the list
   with details.

- aparna: we're finding 4-5 bugs a day.

- mikeal: we're not reopening many bugs

- aparna: our test coverage is pretty much complete; most everything's
   been tested at least once now.

- ted: we have about 20 new untargetted bugs, mostly in account
   browser and admin console areas.

- jared: migration testing can come back to the forefront.  what will
   be loaded into the migration user?

- mikeal: i'll send you the 3K ICS file that's been useful

- capps: how can we best track data migration tasks?  should we use a
   bugzilla keyword?

- jared, aparna: it's an easy to track task; no bugzilla currently

- jared: i'm schema migration test driver, and will followup with next
   steps and open issues

- aparna: let's reuse most of the 0.6.1 migration test plan:
   http://chandlerproject.org/Journal/CosmoZeroSixOneMigrationTestPlan

- aparna: would like to know the status of the hub pto entry service
   ticket (#10104, 10022) and feedback server (#9828)

- capps, jared: we all pretty adverse to hub-update cycle, so let's
   just postpone the hub pto entry problem.

- jared: i'll work with bear to get the feedback server back up

- bear: cool

- jared: let's do migration testing early next week

- jared: noticed recently that we've talked about hardware coverage,
   but "customer support" coverage hasn't been discussed.  There have
   been maybe 4 incidents this year requiring direct, extra support.
   We don't know how much support a Preview Launch will generate nor
   what form it will come in.  Ted's been added to the support alias.

- ted: i'm fine covering, though I'm not sure what there is to do.

- jared: we need to add bear to the eyes-only list for proper backend
   coverage too.

- jared: for preview scheduling, there's more slack in the proposed
   schedule.  i'm planning to update Hub to Cosmo 0.7 as soon as
   released, not after a delay.  after that, we need about 3 days to
   watch Cosmo 0.7 in the real world before launching Preview
   officially.