Milestone 4

• Not a lot of visible features, unfortunately -- most visible features will be part of M5
  • we did have sidebar, toolbar, minical and detail
  • Yet to see: timezones, recurrence, more minical stuff (busybar, snap, preview)
• Integration work on Item Collection is now in progress -- much tearing apart and putting back together.

Version #s, again

• Original: 0.3 release was 0.3.01, 0.3.02, then 0.3. People would get confused thinking 0.3.01 was "greater than" 0.3 therefore later and more recent.
• Today: 0.6 release is 0.5.01, 0.5.02... then 0.6. We have some confusion saying "Oh five" to mean the milestone as well as "Oh five" the dot five release.

• What Cosmo does: 0.2-1, 0.2-2... then release 0.2 (and patches would be 0.2.1)
• Note that RPM numbering system doesn't support any variation other than pure digits divided by periods. Is there a possibility we haven't figured out how to use RPM very well?

• Our plan: starting from beginning of developing 0.7, we will have 0.7m1, 0.7m2... 0.7 release. Then if we ever need to patch a release we will be able to call the patches 0.7.1, 0.7.2, even 0.7.1.1 if necessary. All of these will be considered part of 0.7 so the major version field in bugzilla would be 0.7 for all of these.

Next milestone

• Tinderbox changes discussed
• Remember to be clear about when the checkins close vs. when the build is dropped -- often these are on successive days. Which is the day of the milestone? Arbitrary, we just need to be clear
• need to be clear (make decision) about supporting tiger

0.7 thinking

Goals

• We'd like to have a shorter release than 0.6
• We'd like to have clear tenets again

Conclusions

• These are two reasons to split what we previously envisioned as 0.7 into two (naturally called 0.7 and 0.8)
• As we now understand the list of tasks, both 0.7 and 0.8 should be shorter than 0.6
• 0.7 would clearly be mostly focused on calendar again: view freebusy, doing invitations
• One way to characterize 0.7 is group calendaring rather than only personal calendaring
• We're not yet sure how to characterize 0.8 -- it departs from focus on calendaring to really concern with more general PIM features and email specific features, but it won't be a complete 0.8
• This is mostly thinking about the Application team and their tasks -- Apps will continue to be the critical path for 0.7 and probably 0.8 so we are designing the releases around the constraints of Apps

0.6 one more milestone?

• Sheila and Philippe own making this decision very shortly
• Services, Dev Platform developers won't add completely new features to take advantage of an extra milestone. However they might extend scope of some things and hopefully will dig into bugs in their own areas and those of other more constrained devs.