Perhaps I am behind the times, but that doesn't match my expectation when I go 
check out a source repository for a project. If I want to try the bleeding edge 
of development code I always go checkout trunk. Having that not be the bleeding 
edge seems like another thing we would have to document and tell people about. 

Also, changes in structure will make the history in the repository harder to 
read later. There is already a v0_10_0 in tags perhaps we should just go with 
that? Trunk can just be 0.11.0 and we can go forward using committer specific 
branches as needed? Then when we move trunk to another version we can create a 
tag v0_11_0. 

I applaud the order you are attempting to add to the situation with those 
future version branches but I am not sure the management overhead makes sense 
with such a small team. 

Joseph Southwell
[email protected]
The past is history,
The future's a mystery,
The present's a gift.

On Jan 3, 2014, at 8:10 AM, Thorsten Schöning <[email protected]> wrote:

> Hello,
> 
> as we now have commit access to log4cxx, I would like to create a new
> directory structure to get new patches etc. applied and move towards
> our first incubation release which will be entirely based on the "old"
> codebase with all the patches since 0.10.0 which seemed to never ever
> make it into an official release.
> 
> I would like to create the branches 0.11.0, 0.11.1 and 0.12.0 base on
> the current history and would like to revert trunk back to the last
> official release 0.10.0. The only changes I would keep in trunk would
> be those from Christian regarding the website etc., but no changes to
> the log4cxx codebase itself. Development should take place in branches
> for each new release/version we would like to make, while trunk
> reflecting the last stable released version or something like that. Of
> course everyone should create committer specific branches as needed.
> 
> Any objections?
> 
> Mit freundlichen Grüßen,
> 
> Thorsten Schöning
> 
> -- 
> Thorsten Schöning       E-Mail:[email protected]
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
> 
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
> 
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to