1.1.x backports (was Re: svn commit: r10604)

On Thu, 2004-08-12 at 15:34, Peter N. Lundblad wrote:

> > Well, I'm hoping it gets into 1.1. :-)
> >
> Why? Cleanups are good, but are they worth back-porting at this late
> stage? -0.

Remember that a 1.X release doesn't have the same backporting criteria
as a 1.X.Y release.

The latter is "critical bugfixes only!". The goal is to *not* have
1.X.Y releases at all.

But the 1.1.0-RC releases can have more than just crticial bugfixes:
they're about stabilization. They can have trivial bugfixes backported
to them, not just critical ones. And API cleanup, and code cleanup
too.

The 1.1.x branch requires votes for backport, sure, but it's not
"frozen" in the same sense that 1.0.x is. It's a "stabilization"
branch, open to any changes that make the release as clean and polished
as possible. Once 1.1.0 is released, then the 1.1.x branch goes into
"frozen" critical-bugfixes only. At least, that's my understanding.

Remember ghudson's new plan in HACKING: assuming we find no critical
bugs that require restarting the 'soak' period, we're going to release
an RC3 about a week before the final 1.1.0, just as a sanity check. So
feel free to nominate non-critical stuff that you feel should be in 1.1,
and it will be merged for RC3.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 12 22:50:28 2004