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

[Simon Perreault]

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".

Take a look at the KDE development model. It's *exactly* the same. And it's 
worked wonders for them over many years.