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

Re: What's cooking in git.git (Mar 2009, #01; Tue, 03)

From
Jeff King <peff@peff.net>
Date
Mar 3, 2009, 09:15 UTC
Message-ID
<20090303091504.GG3627@coredump.intra.peff.net>
In-Reply-To
<7vprgzdlom.fsf@gitster.siamese.dyndns.org>
On Tue, Mar 03, 2009 at 01:01:45AM -0800, Junio C Hamano wrote:
Show 5 quoted lines
> As an experiment, 'next' and 'pu' stayed open during this release freeze;
> new topics have been accepted.  I have to say that the experiment was a
> moderate success, and many topics in 'next' seem to be of fairly high
> quality already, which would mean that we will have a shorter cycle before
> 1.6.3.

I was going to stay quiet on this issue until after 1.6.3 released, but now you have opened the topic. :)

I think seeing the quality of topics in 'next' is only half of "success". You have to also consider how much attention was given to the about-to-be-released version (and its impact on quality). And I think we won't know about that until we see how quickly we need 1.6.3.1. :)

Personally, I know that I have spent much less time focusing on 'master'. Like everyone else, I have limited git bandwidth, and topics in 'next' are simply more interesting. I think it's easier to put them aside for a few weeks if everybody agrees to do so (rather than having interesting discussion proceeding without you if you choose to focus on 'master').

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 7 in “What's cooking in git.git (Mar 2009, #01; Tue, 03)”
  1. Junio C HamanoMar 3, 2009
  2. Jeff KingMar 3, 2009
  3. Junio C HamanoMar 16, 2009
  4. Jeff KingMar 17, 2009
  5. Jakub NarebskiMar 3, 2009
  6. Johannes SchindelinMar 3, 2009
  7. Christian CouderMar 5, 2009

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.