Ready in bzr/proposed: qbzr, bzr-builddeb, bzr-stats

[Vincent Ladeuil]

>>>>> Max Bowsher <maxb at f2s.com> writes:

    > Ready in bzr/proposed:
    >  * qbzr 0.19.2
    >  * bzr-builddeb 2.6
    >  * bzr-stats 0.0.1~bzr41-1

Thanks !

It seems to me there is an interesting pattern showing up here: some
plugins release stable version corresponding to the bzr ones even if a
bit later (we document that they should have a stable branch to do that,
I'm not sure how many plugins really do that so far though).

We are buffering them into proposed before copying them to the stable
ppa.

*When* should this copy occur ?

- only when we do a stable release (they will accumulate until the 2.2.2
  release),

- after they have been tested (who is using the proposed ppa instead of
  the stable one ?)

If people are using it I suspect they have read this mail or at least
noticed the update, can you shime in here if you're one of these
people ?

Otherwise, are there people out there using the stable ppa that are
ready to take a slight risk of switching to it ? 

Since this is the last step before entering the stable ppa, the risk is
really slight, not null, but certainly the second less risky scenario
(after just using stable). One should also keep in mind that subscribing
to both allow you to easily revert to the stable version via
synaptic. I.e. even if some breakage is introduced in the proposed ppa
you can quickly revert the update waiting for a fix which is supposed to
occur as fast as we get feedback ;)

         Vincent