"Erik Huelsmann" <e.huelsmann@gmx.net> writes:
> I better get those changes for my issue 897 checked in fast! :-)
>
> [ snip the part which explains the process; I agree ]
In general, that's a very dangerous attitude :-). We don't want
people thinking "Oh, a release is coming up, better squeeze all my
changes in before it goes out!" unless they have issues specifically
planned to be completed for that release. It's much better not to
have stuff rushed in like that.
As issue #897 is about making error messages clearer and more
consistent, this particular issue is not very dangerous, so you can do
as much of it as you want before 1.0. Just note that the release will
not be held up for this issue.
> > Exactly which
> > changes get merged and which don't will be decided by the release
> > manager (Jostein), in consultation with the developers, but the
> > general goal is to avoid destabilizing the branch.
>
> This (potentially) puts a lot more work on the hands of the release manager.
> Maybe we should consult Jostein if he has this amount of time available
> after we agree that this is how it is going to work.
>
> [ snip the open issues part ]
I don't think it's that much more work, because realistically, he'll
have to delegate a lot of that decision-making to the full committers.
And he can make some of that delegation explicit, e.g., he can say
"Ben is allowed to merge changes to the 1.0-stabilization branch
according to his judgement", so that Jostein doesn't have to do
everything.
IOW, if it's too much work, Jostein can find additional workers.
> And here you did not say that there will be no releases for 1.0 while
> releasing from the trunk. Did you?
The purpose of a maintenance line is to release bugfixed versions of
the stable software, without including new features. So after 1.0
comes out, then yes, there would be releases from both lines, though
the 1.0.X releases would be much less frequent than the 1.1.X
releases, because they'd only be done as needed.
> I think this is very clear. One question though: From the 1.0.X and 1.1.X
> part I conclude that we will be releasing fixes for 1.0 and fixes
> and features for 1.1 in equal pace? i.e the X in 1.0.X was
> intentionally the same X as the one in 1.1.X?
Actually, no. The development line (1.1.X) releases much more frequently.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 4 19:29:23 2003