couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Kocoloski <>
Subject Re: 1.0 Code Management
Date Wed, 07 Apr 2010 00:32:30 GMT
On Apr 5, 2010, at 6:16 PM, Tim Smith wrote:

> On Sat, Apr 3, 2010 at 11:53 AM, Jan Lehnardt <> wrote:
>> A conservative view would mandate that we use the 0.11.x branch to add
>> bug fixes until it is shaped into a form that we want to call 1.0.0 and then
>> branch that into the 1.0.x branch that we keep for maintenance.
>> This would allow us to keep using trunk for new features as usual. This
>> also means, we have to maintain two to three branches (0.11.x, trunk and
>> eventually 1.0.x). This is a lot of bookkeeping.
> I think it's best to keep trunk == where development happens.
> Bookkeeping is inevitable, and I think it doesn't serve anyone to
> create a new development branch named something other than 'trunk' and
> then use it like we should be using trunk.
> I'd be happy to help with the bookkeeping, if that would be useful.
> Tim
> -- 
> If you're not part of the solution, you're part of the precipitate

I'd also like to cut 1.0 from the 0.11 branch and not have any restrictions on what lands
in trunk.  Best,


View raw message