Rev 6022: (vila) Move news entries from 2.4 to 2.5 for patches landed after 2.4 in file:///home/pqm/archives/thelove/bzr/%2Btrunk/

[vila]

>>>>> Martin Pool <mbp at canonical.com> writes:

    > I think the key thing here for last time is that as near to possible
    > as atomically we should:

That's the theory. 'Atomically' doesn't fly when a new pqm branch needs
to be created or when pqm spuriously fail to accept a valid submission,
that caused delays, aggravated by a week-end.

    >  * tag a revision
    >  * branch from that exact revision onto the release branch
    >  * make that the series branch (there should not previously be any
    > series branch)
    >  * announce this

    > There is no freeze on trunk; trunk can always take api-changing
    > patches for the next release.  Therefore, after the last beta,
    > there must be a separate release branch.

Indeed.

And without a proper way to lock the branches involved, that cannot be
done atomically, so everybody has to collaborate in case the atomicity
can not be enforced.

I left both lp:bzr/2.4 and lp:bzr in a state that allowed each branch to
be fixed properly[1] and I would have fixed them myself when time
permitted. I thought they will be fixed quicker by just mentioning the
issue.

        Vincent

[1]: The expedient alternative would have been to blindly land
everything on 2.4 and ask people to *remove* the undeeded stuff. A
longer alternative was to inspect the diff but I didn't have the time
for this one.