[Cosmo-dev] Cosmo.next version numbering

[Katie Capps Parlante]

Putting on my cosmo-pm-pinch-hitter hat, I have a follow up proposal:

- Move Safari related bugs to 0.7.1: Bugs 9747, 9888, 9889, 9890

- Other bugs to treat similarly (or outright move to Future):
   + Bug 8130 (Detail view display when you switch collections)
   + Bug 9818 (Users should be allowed to leave Title field blank)
   + Bug 9899 (to/fr fields not displayed in the Updated By column)
   + Bug 9939 (Ubuntu logo)
   + Bug 9887 (small screen browser button layout)

I know these cuts are getting painful; the spirit of the proposal is to 
get something up on production and fix these bugs in quick release 
cycles. I'm not 100% sure a Safari punt is the right thing to do, but 
thought I'd throw it out there.

Cheers,
Katie

Ted Leung wrote:
> Hi folks,
> 
> We've been saying that the next "feature" release of Cosmo was going to 
> focus on interop of various kinds, and that the external forcing 
> function for that release would be Apple's release of OS X Leopard 
> sometime in October.   Currently we've been assigning the interop bugs 
> to a 0.7.1 milestone, but in conversations with various folks, it seems 
> like it would be better to create a Cosmo 0.8 milestone, and put all the 
> bugs currently assigned to 0.7.1 there and leave the 0.7.x release 
> numbers for an inevitable series of Cosmo 0.7 bug fix releases.