[Trac-dev] Re: tentative 0.12.0 release schedule

Manuzhai wrote:
> On Sat, May 3, 2008 at 11:47 AM, Jeroen Ruigrok van der Werven
> <asmodai <at> in-nomine.org> wrote:
>>  My current suggestion:
>>
>>  beta 1 : 2008-10-01
>>  beta 2 : 2008-10-14
>>  rc1    : 2008-11-01
>>  rc2    : 2008-11-14 (as needed)
>>  release: 2008-12-01
> 
> I think the cycle could be much shorter for than that. Instead of
> aiming to fix everything bug in the tracker, get i18n and
> MultipleRepositorySupport (which are supposedly both already in a
> fairly usable state), merge them, fix things up (including lots of
> small bugfixes, of course), and release in three months.

While your timeline is really only about 6 months, which is reasonable 
for a release, I say let's cut the 0.12 features to i18n and 
MultipleRepositorySupport and release.  I think keeping releases to 2, 
maybe 3 "features"[1] each is a good thing to keep our release cycle down.

-John

[1] While I think focusing on two or three features should be the goal, 
if someone completes a feature that isn't on the the goals, it could be 
merged.  Just it wouldn't be a release blocker.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---