Re: Let's make our cycles shorter

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 25, 2011, 17:03 UTC
Message-ID: <7v1v0ql0uw.fsf@alter.siamese.dyndns.org>
In-Reply-To: <BANLkTinzXLK0dHYjBMpBgLqZ_7KNHeu3uA@mail.gmail.com>

Sebastien Douche <sdouche@gmail.com> writes:

> On Fri, Apr 1, 2011 at 00:35, Junio C Hamano <gitster@pobox.com> wrote:
> ...
> I was surprised to not read response, it's having sensitive impact on
> the project.

Hmm, what sensitive impact on which project do you have in mind?

> Junio, it's effective now?

The structure of clean-up, development, freeze and then release has always been in effect in this project, but historically the duration of the development stretch varied a lot from cycle to cycle.

I just spelled the structure out for the next cycle, and tried to give some predictable bounds to that elastic development stretch, in order to force myself to stick to a schedule in which we can make measurable progress in reasonable amount of time.

It does not mean that we won't be tackling issues that will take more than N weeks to perfect. Either a topic gets polished enough in a single cycle to graduate to 'master' before -rc0, or it keeps cooking in 'next' during the feature freeze, and will attempt to be in the release after that.

I've tentatively set the following dates on my calendar, based on 9-week cycle:

 - Today is the beginning of week #1 for this cycle.

 - The entire month of May 2011 will be the development stretch (lasting
   up to Week #5 that ends May 29th).

 - Aim to tag 1.7.6-rc0 on June 1st, 2011, -rc1 on 8th, -rc2 on 15th.

 - Either tag 1.7.6 final on 19th or have -rc3 on 22nd and final on 26th
   of June.

If you happen to use Google Calendar, you can paste:

    jfgbl2mrlipp4pb6ieih0qr3so@group.calendar.google.com

in the "Other calendars" box (where a gray "Add a friend's calendar" appears), but you won't be missing much even if you don't (I only have week numbers and the target tagging dates, nothing more interesting than that).