"Greg Stein" <gstein_at_gmail.com> writes:
> The big question is whether this goes into 1.6 or not. On the roadmap,
> I see there is a hope to release 1.6 at the end of the year. I'm
> hoping to be done in time for that. But that's pretty aggressive. So
> the next question becomes: hold 1.6, or just include some dead code in
> 1.6? At some point, there will be a "no turning back" commit that puts
> the WC onto its new track. We'll have to discuss/judge at that point.
> *That* commit may start a branch so that it can route around a 1.6
> release.
After the 1.5 delay, we pretty much decided not to hold releases for
particular features. Let's stick to that. Maybe if it were a smallish
feature, and really close to being done, and we could all see the scope
clearly, we'd delay a release by a week or something... But a wc
rewrite? If it doesn't make the 1.6 train, then the 1.7 will be along
any day now :-).
> I'm actually thinking that making all active developers deal
> with it (tho I'll try to minimize, of course) may be the right
> approach.
+1
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-18 15:08:29 CEST