[ANN] bzr 2.4b1 has gone gold

[Aaron Bentley]

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

On 11-03-19 12:13 PM, Gordon Tyler wrote:
> Using the same versions as bzr 2.3, bzr-pipeline and bzr-svn are failing
> to load with bzr 2.4b1.
> 
> pipeline (failed to load)
>   ** Unable to load plugin 'pipeline'. It requested API version (2, 3,
> 0) of module <module 'bzrlib' from
> '/Library/Python/2.6/site-packages/bzrlib/__init__.pyc'> but the minimum
> exported version is (2, 4, 0), and the maximum is (2, 4, 0)

I know it's too late, but I thought I'd try to fix this, only to realize
that I don't know what I should be doing about versioning these days.

With pipeline, I'm trying to play nice by using the official versioning
 functions instead ofapi instead of the homebrew approach used in
bzrtools.  The idea was supposed to be that bzr wouldn't update its
minimum API version very often, and so plugins could declare
compatibility with certain API versions and wouldn't have to update
until compatibility was actually broken.   But these days, we seem to
update the API version in sync with the bzr version, so declaring
compatibility with bzrlib 2.3 doesn't do any good for pipeline when
2.4b1 comes out.

But I don't want to declare that a release is compatible with bzrlib 2.4
until I've tested it with a final version of that API, i.e. bzr 2.4.0.
So I really shouldn't release bzr-pipeline 1.2 until bzr 2.4.0 goes gold.

In this situation, it seems like the homegrown versioning in bzrtools
works better, because it tolerates betas of the next release.

So maybe I should be releasing betas of pipeline?  Seems a bit crazy
when I've hardly changed anything.

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

iEYEARECAAYFAk2L6ccACgkQ0F+nu1YWqI3vTgCfZ6784o8a2ZDJzKWOJXhKTbRl
VjgAn1KQbXf7DPLk2l6Tkv6XUMgdk7JM
=H0KU
-----END PGP SIGNATURE-----