kfogel@collab.net writes:
> I think we really need to get that STATUS file under version control
> right now, so we can start to compile a complete list of the proposed
> changes. I'm finding it hard to evaluate this one without the others
> around it.
>
> I'll ask Jostein if he minds us starting it in the 0.35 branch, since
> that leads directly to the 1.0 line.
Jostein, do you mind if I start a STATUS file on the 0.35 branch,
since, unlike trunk, that leads to the 1.0-stabilization line?
The STATUS file is described in HACKING, see the section "Stabilizing
a release branch". It's basically a place to record votes about
whether something will or will not get merged into 1.0. (I've been
assuming that once developers agree on a particular change being
merged, you're okay with any full committer actually doing the merge.
"Release manager" doesn't have to mean "merge slave" :-) ).
Anyway, it would be nice to start that STATUS file now so we can start
getting an overview of all the issues out there. There are a lot of
them; I think when we see the sheer number, that will automatically
make us a bit more conservative about choosing them.
Whatever state the STATUS file is in at the 0.35 release is fine, it's
really about 1.0, not 0.35. I'd port r8005 over to 0.35 too, that's
the new HACKING section about the STATUS file.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 15 23:02:05 2003