[MERGE] Split bzrlib/transport/smart.py into several smaller modules.
robert.collins at canonical.com
Wed Apr 11 03:11:51 BST 2007
On Tue, 2007-04-10 at 10:50 -0500, John Arbash Meinel wrote:
> I'm happy to see this refactoring land. Though whenever we do
> like this, I wonder about backwards compatibility. Is it okay to break
> compatibility for large cleanups like this? Is the 'official' api to
> access it in a different way (I don't think it is common for a plugin
> want to grab an existing smart server object, but it certainly might
> implement one.)
So perhaps we should add a NEWS item. In terms of compatability, bzr
0.15 does not offer extensability to the smart server on client or
server side. The only usable bits of it are:
- the server (via bzr serve or the library).
We're breaking the server with this move, but its trivial to recover
from (unlike other forms of api change).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070411/00e73638/attachment.pgp
More information about the bazaar