[Cosmo-dev] Cosmo release frequency

[Mikeal Rogers]

I agree with bcm.

With the features we've been talking about 2 week releases would end  
up meaning that features that had been worked on for 3 weeks or more  
in branches would just get merged in whenever they were finished and  
fell on a release week. We can really only have these short QA cycles  
when the set of changes are minimal, if 4 weeks of a developer's time  
are spent on a few features then we can expect a QA cycle like we  
would for a 4 week release every 2 weeks.

4 week releases sound a bit more reasonable.

-Mikeal

On Oct 8, 2007, at 10:51 AM, Brian Moseley wrote:

> On 10/8/07, Ted Leung <twl at osafoundation.org> wrote:
>
>> For Cosmo 0.7.x, we were on a 1 week release cycle, and for Cosmo
>> 0.8, we stretched a little bit in order to get the CalDAV interop
>> work in.   I'd like to go back to a time based release schedule, but
>> I'd like to have people's opinions as to how frequently we ought to
>> release.   My personal preference would be every 2 weeks, but I 'd
>> like to hear what other people think.
>
> i think two weeks is a little too ambitious. releases would lose any
> sort of coherence and would just be dumping grounds for random
> assortments of independent features. i think a month might allow us to
> declare a theme for a release and therefore rally around it a little
> more. it would also keep stress levels a little more evened out.
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev