subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf <danie...@elego.de>
Subject Re: Proposal for reducing Subversion's lengthy (and unpredictable) release cycles.
Date Thu, 13 Jun 2013 13:43:28 GMT
C. Michael Pilato wrote on Thu, Jun 13, 2013 at 15:27:07 +0200:
> In the interest of serving our user base, we are proposing that each release
> live on the trunk for at most nine months.  The first six months of this
> period are open to new features.  In the first three months of the new
> feature period, large, destabilizing features will be accepted (under the
> provision that the feature itself is arguably “complete”, which seemingly
> implies that it was developed on a feature branch maintained with routine
> sync merges.

Or, where possible, developed on trunk within #ifdef THAT_FEATURE tags,
with -DTHAT_FEATURE being disabled by default.

> In the second three months, we will still accept smaller new
> features.  But at the end of the six months, the trunk is closed to new
> features and stabilization for the release begins.  We will allow up to
> three months for stabilization on the trunk, cutting the release
> stabilization branch at the end of the period (or beforehand, if we agree
> that the codebase is ready for RC).  The release branch is managed the same
> as it is today, with an RC at the earliest reasonable moment and the same
> soak requirements and such that we've always had.

Mime
View raw message