>>> 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.
+1. > We would only have some overhead for the first releases, 0.11.0 and > 0.11.1 would get merged back to trunk during their release and deleted > as branches, only keeping the "active development branches" we would > want, 0.12.0 in the beginning. I like the 0.11.0, 0.11.1, and 0.12.0 plan that Thorsten set out with the implication that "trunk" means the last, public, stable release. That makes the public APIs and website reflect stable in a straightforward manner as he described. Maybe post-0.12.0 we can call something "develop" or "next" or "unstable" or something which should make it clear to anyone browsing SVN what the bleeding edge happens to be...? - Rhys
