On 7/15/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> On 7/15/06, Max Bowsher <maxb1@ukf.net> wrote:
> > This isn't anyone's deliberate fault, but collectively as a team, I
> > think we've failed to explicitly define a compatibility policy for the
> > Ruby bindings. This has led to the current situation in which some
> > portion of the committers expect the bindings to follow the same
> > compatibility rules as the rest of the project, whilst those committers
> > most closely focused on the Ruby bindings seem to have been assuming
> > it's OK to incompatibly change interfaces in a minor release.
>
> I thought we had decided for the Python bindings, at least, that the
> versioning rules don't apply. I know we've talked about this in the
> past, but I can't seem to find the thread just now. -- justin
I'm not sure if that's the case... I know for example that we've gone
out of our way to avoid breaking compatiblity in the python bindings
at least as far as making sure mailer.py and viewvc continue to work
properly...
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 16 23:33:27 2006