On Fri, Oct 03, 2003 at 10:48:20AM -0500, kfogel@collab.net wrote:
> 2. Stabilize trunk, and just don't do new feature development until
> 1.0 is out.
>
> (2) has a bigger impact on developers who might want to work on new
> features. It effectively asks them to forgo that work, and either sit
> tight or help fix bugs instead.
>
> > So, I'm -0 on using the trunk as the release branch, but only because
> > it might blur the changes made on other branches and merged in later.
> > If we can agree to focus only on bugfixes, then I'm +1 on using the
> > trunk; that way there's no merging at all.
>
> Exactly, me too.
>
> Would any developers be very uncomfortable with (2)? It would be
> great if we all felt pretty much the same way about the relative
> priority of 1.0 versus new feature dev at this time... But I don't
> want to presume.
My point was that if they can't help but work on some non-1.0 feature,
they can always do the work on a branch. Then there's no presumption
required; individuals will need to weigh their desire to work on something
new against the extra hassle of the merge required later.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 3 18:44:39 2003