On Aug 9, 2012, at 8:10 AM, Greg Reddin wrote: > On Thu, Aug 9, 2012 at 1:16 AM, Alex Harui <aha...@adobe.com> wrote: >> Absolutely correct, but I don't want to hold off another release until we >> have a mustella test for every code path and boundary condition, so I am >> proposing using an "unstable" branch as the proving ground until we prove we >> don't need it. > > Similar to my previous post, but maybe we avoid argument by simply > flipping the model. > > Instead of stable trunk and unstable branch what about this? > > svn cp trunk branches/stable > > Trunk is now unstable and "branches/stable" is ready for a quick > release. The only complication there is how to "promote" code from > trunk to stable, but maybe we can do that on a case by case basis.
IMO the Release Vote is the main promotion process, but there might be other cases. FYI - Some projects like Tomcat and HTTPD maintain multiple branches that are stable (or not so stable) releases. Regards, Dave > > Greg
