From: Junio C Hamano <gitster@pobox.com>
To: Sebastien Douche <sdouche@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Let's make our cycles shorter
Date: Mon, 25 Apr 2011 10:03:35 -0700 [thread overview]
Message-ID: <7v1v0ql0uw.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <BANLkTinzXLK0dHYjBMpBgLqZ_7KNHeu3uA@mail.gmail.com> (Sebastien Douche's message of "Mon, 25 Apr 2011 02:34:58 +0200")
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).
next prev parent reply other threads:[~2011-04-25 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 22:26 What's cooking in git.git (Mar 2011, #06; Thu, 31) Junio C Hamano
2011-03-31 22:35 ` Let's make our cycles shorter Junio C Hamano
2011-04-25 0:34 ` Sebastien Douche
2011-04-25 17:03 ` Junio C Hamano [this message]
2011-06-13 0:45 ` Sebastien Douche
2011-04-01 13:31 ` [PATCH] git diff -D: omit the preimage of deletes Michael J Gruber
2011-04-01 19:26 ` Junio C Hamano
2011-04-03 6:23 ` Junio C Hamano
2011-04-03 6:38 ` Junio C Hamano
2011-04-03 12:51 ` Michael J Gruber
2011-04-01 15:26 ` What's cooking in git.git (Mar 2011, #06; Thu, 31) Jeff King
2011-04-01 17:01 ` Junio C Hamano
2011-04-01 17:06 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v1v0ql0uw.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sdouche@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).