From: Wincent Colaiuta <win@wincent.com>
Date: Sun, 20 Jan 2008 10:18:23 GMT
Subject: Re: Time to flush developer accumulated patches?
Message-ID: <0B23B7DB-8AB2-4D8D-BE50-917651238353@wincent.com>
In-Reply-To: <e5bfff550801200210y212d0921x214773596810be52@mail.gmail.com>

El 20/1/2008, a las 11:10, Marco Costalba escribió:

> Reading mailing list threads it is becoming common these days to hear
> about contributors with patches ready to be sent as soon as 1.5.4 is
> out.
>
> Would be a good idea to open a new branch new_stuff as a target for
> this pending stuff?
>
> I understand that you want people focused on fixing bugs, but I also
> understand that people don't ;-)
>
> Opening a new_stuff branch could have the following benefits:
>
> - Give more time to fix bugs before 1.5.4 is out without stopping
> people from having fun and reduce the pressure to release.
>
> - Reduce the merging impact when master reopens because patches are
> already merged in new_stuff and developers have already taken care of
> conflicts
>
> - Do not slow down the wheel: I can develop some patches and keep them
> myself, but until are not discussed in the list and eventually got in
> master has little meaning to continue develop additional stuff.
>
> - Perhaps it's lack of reviewing time on your side that worries you
> (as is normal because we are on bug fixes mode in master) but upgrade
> from new_stuff to master would be not automatic nor guaranteed but at
> least people have an idea at what's going on and can keep contributing
> in code and ideas.

We already have two such branches: next and pu.

Here's an old version of a mail from Junio describing the different  
branches; I know he's sent out newer ones but this it he one that I  
could lay my hands on:

http://article.gmane.org/gmane.comp.version-control.git/39954

Cheers,
Wincent