[asterisk-dev] merge policies, supported branches, API/ABI freeze (was Re: Asterisk 1.6 Release Management Proposal)

[Luigi Rizzo]

On Fri, Oct 19, 2007 at 12:39:42PM -0400, Simon Perreault wrote:
> On Friday 19 October 2007 12:27:51 Luigi Rizzo wrote:
> > Developer branches do have many purposes, but the testing-for-production
> > is not one of them.
> 
> No, that's the role of the 1.6.X branches.
> 
> Russel's plan makes total sense. Developer branches are a playground, where 
> you may break things at will. Trunk is "let's keep this working, but pretty 
> much everything goes". 1.6.X branches are "let's stabilize and release 
> trunk".

so what is in your definition the [most] "stable" version, trunk or 1.6.x ?
I don't mind either way, it's just a matter of naming, but in the end,
as a user i need to know what i want to use as a "99.9% safe-to-use
version" and a "may be occasionally broken but it has new interesting
features, plus i will help progress if i test this branch".

cheers
luigi