From: Sebastien Douche <sdouche@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Let's make our cycles shorter
Date: Mon, 13 Jun 2011 02:45:36 +0200 [thread overview]
Message-ID: <BANLkTim4STXM-r0aujsmu4YeJ9WLt+Y_VEvZ_rG5PEqLnAAq6Q@mail.gmail.com> (raw)
In-Reply-To: <7v1v0ql0uw.fsf@alter.siamese.dyndns.org>
On Mon, Apr 25, 2011 at 19:03, 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?
Short cycle means less time to write code for the next release, the
"frame" to add feature is reduced. I'm surely wrong, Git is a stable
project and well managed (with 4 branches: unstable, integration, next
stable & stable).
> 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.
Cool :).
--
Sebastien Douche <sdouche@gmail.com>
Twitter : @sdouche
next prev parent reply other threads:[~2011-06-13 0:46 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
2011-06-13 0:45 ` Sebastien Douche [this message]
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=BANLkTim4STXM-r0aujsmu4YeJ9WLt+Y_VEvZ_rG5PEqLnAAq6Q@mail.gmail.com \
--to=sdouche@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).