Is it ok now to delete the methods deprecated in 1.4?

[Robert Collins]

On Wed, 2008-04-16 at 12:46 +1000, Martin Pool wrote:
> 
> Our general policy is to keep deprecated methods around for a few
> releases, to avoid breaking external code that uses it.  If it takes
> extra work to keep supporting them then we can make an exception; if
> it's just that you'd like to shrink the code I'd suggest waiting for
> 1.6 at least.

It will take extra work; this is the part of the code that is being
pivoted from single-versioned files to tuple-key based broader
containers; all the methods that aren't deleted when we pivot need
adapting.

So, I propose:
 - a clear message to the list saying whats happening
 - remove the methods now, with 1.5 just opened

plugin authors/users that go from 1.3 to 1.4 will get deprecation
warnings.
Those that jump straight to 1.5 will get missing attribute errors and
the like.

Both cases will be documented in NEWS.

I'll put together a patch for this soon; if its not something that seems
appropriate it can be shelved till 1.6.

-Rob


-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080416/b3e7bbeb/attachment.pgp