[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: stabilize means STABILIZE (was: svn commit: rev 7961 - trunk/subversion/libsvn_wc)

From: Sander Striker <striker_at_apache.org>
Date: 2003-12-11 18:17:24 CET

On Thu, 2003-12-11 at 15:55, kfogel@collab.net wrote:
> I hate straddling the middle ground, because it seems so wishy-washy,
> but I think Greg Stein's got a point, just not as strong a point as he
> would have it.
> We don't need to completely shut down all non-0.35 commits on trunk.
> But we do need to get somewhat stricter than we have been.
> Can we agree that until we branch, it's fine to commit riskless things
> like error message fixes, comment fixes, and null checks (where the
> thing *definitely* shouldn't be null)... but that larger changes such
> as the recent wc access baton thing, or Tobias's SSL auth work, should
> only be done if they bring a large benefit, and even then need three
> +1's from full committers to go in?

If that is the deal, branch today and backport on 3 +1s.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 11 18:18:03 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.