Code complete date and current reality (Sheila) - 5 min
Launch plan (Ted) - 10 min
Plan for updating QASharing (Katie) - 10 min
OSCON (Katie) - 10 min
Review of wiki URL issues (Mimi) - 10 min
Notes
Cosmo
Around 50 P1 and P2 bugs
Code complete date and where we are now
Are we going to promote any P3s higher to P1 and P2
Bug fix rate has been pretty good
QA - how do we feel about code coverage? Round trip sharing and updating dashboard items has not started.
Make another schedule assessment next Monday
Jared - planning on going onto final release steps for 0.6.1 today - some impact on QA resources
Cosmo QA sessions planned for Wed and Friday
Desktop
Today is the localization freeze date
Philippe added i18n keywords to all the applicable bugs
Four bugs outstanding right now but we are very close * bkirsch - 2 bugs * heikki * mimi - tooltip bugs * welcome note - all done
We can declare this milestone done - Philippe will send email out about this
Bug count - need to do a big bug scrub - only 36 P1 and P2s
Need to identify any P3s that we want to promote
Integration between desktop and cosmo is still a concern
Bug find rate is still a concern
Code complete date and
Next actions
Triage all the P3s and identify important bugs
Lots of QA this week to
Launch plan
Wanted to get people's thoughts on the launch plan
Katie: We could think of OSCON as a first step in the launch plan. We need to think of what wiki stuff needs to be ready. First event that is happening to get people engaged.
Mimi: Launch card - has heard back from most people about tagline. Last call going out today so please respond.
Jared: Put some more attention to the web presence post preview.
Sheila: Talk about everyone engaging on the users list - not just PPD.
Jared: Some questions about what the launch posts look like. We should come up with a first draft early. To make sure we get the right tone.
Bear: Doing some wiki stuff after launch shows continual progress
Philippe: Contacting some of the blogger and demo'ing the product. Should we approach these people? We would need to make sure our content and message is clear first.
Mimi: Will we get our point across better from talking to people or blogging. Probably we need to do both. We can take the first step and write about this.
Need a gentle ramp up on the message.
Important for everyone to respond on users list and IRC (and other mailing lists).
Next actions
Make the plan a bit more concrete - Ted
What are the minimums we need to have as far as the wiki is concerned - launch page and blog? Explicit about artifacts that we absolutely need and when.
Plan for updating QA sharing
We had some conversations about the Cosmo release meeting about plan for QA sharing and QA Cosmo and how they get updated
Katie will do an OSCON presentation - running locally on her machine
In support of this we will move QASharing to some release candidate - proposal is 2 weeks from now (one week before OSCON)
Aparna not sure how we will be doing by then. We need to have done more integration tests.
Need to add this to the Preview countdown - upgrade QA sharing to 0.7 (some RC)
Bug number 9833 - add this to the Preview countdown page.
OSCON
Identified that we need to have the launch page up.
Need to clarify all the other wiki requirements.
OSCON goals need to be added to Preview countdown page.
Wiki/URL stuff
Landing page
Download page - conversation to happen on list. Iron out issues that Bear brought up.
Get involved vs developer vs community
Product FAQ - logged a bug for Ted to write up directions for publishing to Cosmo server.
Cosmo help
Cosmo has already had release specific help and PPD was planning to just have a consolidated FAQ.
There would be documentation specific to a particular release.
We can have a separate conversation about this in the release meeting on
Mimi doesn't understand how the landing page url will be different from the wiki home page URL
If the landing page is chandlerproject.org - we will have a static page in the works (mimi). There is a separate wiki home page.
Need an email to the list that explains these 2 pages, what they are and where they are referenced and the current implementation.
Rationalizing the wiki content across project
Delete the Cosmo home page. Is there content that needs to be migrated. Ted can move content from Cosmo home to the right places.
Mimi will log a bug with next actions
Mimi will send out this summary to the list.
Other
Jared planned a vacation for the end of August
Others will need to shadow Jared and learn how to update the Hub