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

Re: Merge policies regarding bindings

From: <kfogel_at_collab.net>
Date: 2003-12-22 19:30:47 CET

Eric Gillespie <epg@pretzelnet.org> writes:
> We don't need to hold up a release waiting on the bindings. The
> point is, the bindings that ship with 1.0 will NOT be 1.0
> quality. If that is the case, it would be best to ship with the
> latest and greatest.
> We should be *encouraging* the use of the bindings. Shipping
> with bindings that aren't the best we have is no way to do that.
> Furthermore, it's insulting to those who are working hard to make
> them better.

Well, obviously no insult is intended here... :-)

My point is that one can't say for sure that a change touches only
bindings and affects nothing else, without inspecting it. That's why
bindings changes need to go through the same inspection process as
other 1.0 changes. (For example, some bindings changes tweak the
build system -- if there's a mistake, they could affect aspects of the
build that have nothing to do with bindings.)

Shipping with the latest bindings is fine, just not by skimping on


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 22 20:21:13 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.