[ANN] bzr 2.3b1 released ! (bzr-beta-ppa updated; some plugins uninstallable)
Martin Pool
mbp at canonical.com
Sat Sep 25 03:17:49 BST 2010
On 25 September 2010 01:48, Vincent Ladeuil <v.ladeuil+lp at free.fr> wrote:
>>>>>> John Arbash Meinel <john at arbash-meinel.com> writes:
> > Yes, it is a bit gratuitous, but I think it helps set
> > expectations. In the 2.2 cycle, we asked for API freeze on 2.2b4
> > specifically so that plugins could make sure they were all
> > up-to-date before the 2.2.0 release. I think that worked ok, and
> > the more regularly we do that, the smoother the process will
> > become.
>
> But we did set it to 2.2.0 in revno 5110, so roughly after 2.2b2 but
> before 2.2b3.
>
> If we decide to bump it, then the sooner the better and preferably far
> before a release so, very soon on trunk or just after 2.3b2.
Let's do it.
I think that for Python, and for bzr, there is little to be gained by
distinguishing the api supported versions from the code version. It
may work in C but not here. Let's just declare that "we're 2.3b2" and
then plugins can decide if they want to assume they work with any
bzrlib, they work with bzr >=2.2, they need a special workaround for
some versions, or whatever.
I'd be ok with a code change that just says "the api version = the
code version."
If plugin developers do find the api version stuff useful I'm happy to be wrong.
--
Martin
More information about the bazaar
mailing list