[bt-devel] Your changes in CVS

[k486]

* Raoul Snyman <raoul.snyman at saturnlaboratories.co.za> wrote on [2009/11/17 03:18]:
> On Tue, 17 Nov 2009 11:08:03 +0200 (EET), Eeli Kaikkonen wrote:
> > BTW, if the long time waiting for final realease is a problem, maybe we
> > could create a new 2.x branch before beta or rc? Then the head would be
> > open to larger changes.
> 
> I'd recommend that beta release becomes a code freeze, we branch then, and
> only bug fixes happen in that branch. Once final is released, we can merge
> those bug fixes back into trunk. This branching technique will allow
> greater freedom in trunk, and less problems. Of course our tagging of
> releases happens in conjunction with this.

Hi all!

I'm slightly confused about the roles of the trunk and branches.  Is it 
not the norm for trunk or the mainline to remain as stable as possible 
and for major code changes and new features to be tracked in development 
branches?  Then after everyone has tested and reviewed the development 
code, it is merged back to the trunk.

I'm new so I don't want to make any assumptions or presumptions for that 
matter.  

Kang

PS - Thomas, thanks for the warm welcome!