git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Instituting feature and infrastructure enhancement proposal window?

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 25, 2008, 00:52 UTC
Message-ID
<20080225005254.GJ8410@spearce.org>
In-Reply-To
<alpine.LFD.1.00.0802241226340.21332@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
Show 16 quoted lines
> 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.
Previous: Linus TorvaldsNext: Junio C Hamano
Message 3 of 5 in “Instituting feature and infrastructure enhancement proposal window?”
  1. Junio C HamanoFeb 24, 2008
  2. Linus TorvaldsFeb 24, 2008
  3. Shawn O. PearceFeb 25, 2008
  4. Junio C HamanoFeb 25, 2008
  5. Daniel BarkalowFeb 25, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.