Git development
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Instituting feature and infrastructure enhancement proposal window?
Date: Sun, 24 Feb 2008 19:52:54 -0500	[thread overview]
Message-ID: <20080225005254.GJ8410@spearce.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0802241226340.21332@woody.linux-foundation.org>

Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, 24 Feb 2008, Junio C Hamano wrote:
> >
> > The important dates in the above would be (in parentheses are my
> > straw-mans):
> 
> So I would basically cut you target timeframes into half (except for the 
> first -rc release - there's no point in making that less than a week). 
> Three months is just going to make people who miss the release window 
> antsy. It's what the kernel has in practice, and I would *not* advocate it 
> as ideal - I actually aim for 2 months and we then invariably slip a bit..
> 
> So I'd suggest:
>  - first -rc in 1 week
>  - window closes in 3 weeks
>  - next release in 6 weeks
>  - rinse and repeat

Yea, I agree with Linus suggestion of cutting the time windows
down to closer to 2 months per release.  1.5.4 took a long time.
It doesn't really affect me as I usually run the bleeding edge
'next', but I think most of our users feel warm and fuzzy about
running a released version.  As a community we need to help Junio
get stable releases out more often, so users can benefit from the
improvements we've made.

-- 
Shawn.

  reply	other threads:[~2008-02-25  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 19:33 Instituting feature and infrastructure enhancement proposal window? Junio C Hamano
2008-02-24 20:42 ` Linus Torvalds
2008-02-25  0:52   ` Shawn O. Pearce [this message]
2008-02-25  1:37   ` Junio C Hamano
2008-02-25  3:25 ` Daniel Barkalow

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080225005254.GJ8410@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=torvalds@linux-foundation.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox