plugin api versioning (Re: [ANN] bzr 2.4b1 has gone gold)

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-03-24 09:34 PM, Martin Pool wrote:
> What I think we should move to is to have declarations of
> 
>   plugin $name $version_range works* with bzr $version
>   plugin $name $version_range does not work with bzr $version
> 
> which is a lot like what's done in Debian packages.
> 
> It should be possible to insert these on either side so if we know bzr
> 2.4.2 breaks bzr-foo 3.141 then we can say so in bzr rather than
> forcing a new bzr-foo release.

I like the sound of this.

> I would suggest then that plugins could normally just say ">= bzr 2.3"
> and assume they will probably work on later versions.

We could make optimistic declarations, but it's really easy to make
realistic declarations instead.  I think running the plugin test suite
is a sufficient compatibility test.  We could even automate it to test
all installed plugins and update the compatibility declarations.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2L/hUACgkQ0F+nu1YWqI09sACeLCmVoOOpVzcapisIJobBQJ1X
h7AAn1N+jTStN6Abg9evShWDJjrXlLLB
=11T/
-----END PGP SIGNATURE-----