Preview countdown meeting, 6 August 2007

Agenda

Quick status

• Desktop status
• Server status
• Hub status
• QA

Milestone/Countdown Review

• Both ZBRs planned for this week (Aug 6 - 10)
• Releases planned for next week (Aug 13 - 17)
• KKIE test session planned for next week (Aug 13 - 17) -- screencast and guide drafts should be ready

Non-code deliverables Review

• Deadline for final draft of all docs not tied to the release: Next week
• Deadline for final draft of all docs tied to the release? How do we align release dates with release notes being completed, etc.?
• Jared: what should deadlines be for Hub related non-code deliverables?
• Announcements? what announcements should we do at time of server and desktop releases? (before Hub ready for launch)

Post Preview Planning

• 0.7.1 desktop release -- Sept 24 is strawman date. What planning do we need to do now (or soon)?
• weekly server releases -- next actions for working this plan through?

Launch Plan Review

• blog posts
• blog traffic
  • peak @152 views a day, both general and announce are much more heavily subscribed.
  • osaf-rss feed broken for a month
  • anecdotal: more traffic after blog than mailing list (chandler users)
  • actions to consider?
    • Jared: any planets we should be on?
    • reannounce blog to all of the mailing lists: basic first step: Ted (closer to the launch)
    • blog mentioned on planet python: Ted
    • Ted to link from his blog

Notes

Status

• Desktop
  • Assessment today @4
  • Philippe on vacation next week
• Server
  • 27 bugs (8 admin bugs)
  • Jared just closed a few unhelpful tracking bugs
  • 9th date depends on incoming bugs -- doable but not guaranteed
  • Ted will be load-balancing throughout the week
• Hub
  • Jared is tired but happy -- lots of closed bugs
  • Almost have final plan for TOS links
  • Hub moving servers on Friday (pending Randy and Bear ok)
  • Rev Run Book one more time
  • Run Book first draft is out, round of comments, getting to "acceptable" stage
  • TOS/Privacy -- meet with lawyer this week -- should be in second round of non-deliverables, finalized around the 20th
  • Cosmo release notes -- if not done by end of week an issue
  • Hub wiki presence? Less of a preview must have.
  • Hub/Server content in Getting Started Guide -- review on the 13th
  • Feedback server up and running -- Jared taking back from Bear
  • Public repo submit -- Bear -- does this need some intro, public page? troubleshooting section?
• QA
  • Bug verification mode: 70 bugs to verify
  • Continue daily sessions, might do 2 on Wednesday
  • Specs updated when running into new issues/scenarios
  • On track for this week

• Why verify bugs?
  • Focused scenarios in areas where the app was recently broken, get to verify recently fixed bugs and discover new related bugs

• Server Performance?
  • Aparna says: not blocking

• Content item must have: update wiki with release info -- bug
• Announcements:
  • Server -- Jared: freshmeat, blog, list
  • Hub -- Jared: blog, list
  • Desktop -- Philippe: freshmeat, cheeseshop for plugins (Heikki, Bear have privs), Linux weekly news
  • Preview -- Katie: blog, announce, mailing lists
• Contingency: Jared's vacation: have them written and/or have backup to pick up the ball (Ted)
• Other URLs that purchased
• Troubleshooting page
• New mailing list archive before Preview: lists.osafoundation.org/archives
• Ted to drive list policy: reply to list? should we change?

• Adding tests
  • regression tests, make this a policy
• Avoiding regressions:

• A release a week?
  • Server: doable -- validation and avoidance of regressions is the issue
  • Hub: creation of an automated sanity test for Hub
  • Jared and Aparna meet and discuss this, get faster turnaround on bug fixes
    • checklist of everything that needs to be done, need a format to follow
  • Ted: Reorient thinking away from big blocks of features. Thinking of critical bug fixes. Not opening tree for all developer work, new feature work in weekly releases. For critical problems that need to be fixed (e.g. support for Safari?). Be disciplined about fixes we take in.
  • Jared: review before commit?
  • Ted: special case first 4 weeks. Be able to deliver changes into production. Not weekly schedule forever.
  • Jared: success when we have control over what fixes go in.
  • Ted: coordination about fixes we take in.
  • Lack of standing release manager during those weeks.
  • Conversation next week: Jared, Ted, Aparna.

• Bear: wants to review plans, interested in implementation details.

Action Items

• Cosmo release notes to be done by end of week or flag
• Hub/Server content in Getting Started Guide
• Public repo submit -- hang a date on that
• Troubleshooting page
• Get developer seat for Leopard: Philippe
• Mimi to file tickets for blog
• Jared, Ted, Aparna to meet (next week) about release