bzr 1.18rc1 source frozen

[Ben Finney]

Martin Pool <mbp at canonical.com> writes:

> 2009/8/11 John Arbash Meinel <john at arbash-meinel.com>:
> > My personal understanding is that in the new system:
> >
> > 1) We will have release candidates for 6-month stable releases
> > 2) We will *not* have release candidates for 1-month "beta" releases
[…]

> That's correct.
> 
> (I'll try sometime soon to update the document with the thread
> consensus and propose that to merge into bzr.dev developer docs.)

Would this be a good time to point out that a “release candidate” is
clearly naming something that comes *before* a release, and so “Bazaar
1.18rc3 released” is begging for confusion (is that “1.18 is actually
released now”, or “something that is actually released is still only a
candidate for release”, or something else?)

I think the terminology of discussing the workflow would make a whole
lot more sense if the objects which *lead up to* a release are not
themselves “released”. Otherwise it makes no sense to talk about a
“release candidate”.

Instead:

    1.17.1 released
    1.18.beta2 available
    1.18.rc4 available
    1.18 released
    1.18.1 released

Either that, or abandon the idea of communicating anything meaningful
with “release candidate” and just incremental numbers for everything.

-- 
 \         “Pleasure's a sin, and sometimes sin's a pleasure.” —“Lord” |
  `\                              George Gordon Noel Byron, _Don Juan_ |
_o__)                                                                  |
Ben Finney