API breakages - file bugs / update HACKING.txt ?

[Jelmer Vernooij]

In order to make life easier for myself as bzr-svn maintainer and for
its various packagers, I would like to get rid of the (currently very
strict) coupling of bzr-svn and Bazaar releases.

bzr-svn only uses public Bazaar APIs but the ones it uses are not used
by many other plugins and at least one breakage (without deprecation)
happens each Bazaar release (Bazaar 1.2 being the only exception),
despite HACKING.txt saying there is a commitment to 6 months API
stability. Is this still the intention for all public APIs? 

I realize that there is overhead in deprecating rather than directly
removing APIs and so it makes not to deprecate when the API is not used
by any plugins. I could file bugs (before bzr releases) whenever bzr-svn
uses an API that wasn't properly deprecated so it can be fixed before
the release. 

If HACKING.txt is outdated, what is the current policy wrt API breakage?

Cheers,

Jelmer
-- 
Jelmer Vernooij <jelmer at samba.org> - http://samba.org/~jelmer/
Jabber: jelmer at jabber.fsfe.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080512/67213cf1/attachment.pgp