[asterisk-dev] Tension between trunk and release branches

[Steven Critchfield]

On Thu, 2007-05-31 at 16:28 +0000, Tony Mountifield wrote:
> d) How can the above points be addressed? It seems we need a mechanism
> to add non-invasive extra features to a production-quality branch after
> they have been sufficiently tested. By "non-invasive", I mean features
> that are effectively just clean additions without making architectural
> changes to Asterisk as a whole. All the dangerous
> completely-break-it-then-fix-it changes would still be done in the
> "experimental" trunk. (Yes, I know that team branches are used nowadays
> for many initial developments before they are ready for trunk).

Isn't this what the add-ons would be great for? Maybe a third portion
that isn't add-ons from a licensing standpoint but rather just a feature
set. This way it still takes a extra step to get it, but it isn't left
completely out of the maintenance cycle when features are considered or
upgraded.
-- 
Steven Critchfield <critch at basesys.com>