Dependencies in the PPA for Jaunty

[Gary van der Merwe]

On Mon, Jun 15, 2009 at 7:24 PM, Aaron Bentley<aaron at aaronbentley.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Maritza Mendez wrote:
>> Is there a document which states which plugins are so important that a
>> bzr build must pass compatibility testing against them before bzr can be
>> released as a stable release?
>
> No, we consider the dependency to be the other way around-- bzrtools
> must pass compatibility testing against the current bzr RC before
> bzrtools can be released.
>
> Forcing bzr to retain compatibility with bzrtools would retard bzr
> enhancements, whereas forcing bzrtools to stay up-to-date with bzr is
> rarely more than a few minutes' work.
>
> Aaron

I agree with that, but there needs to be some process to get key
plugins released at the same time.  Maybe we only need to do this for
final releases, and not for rc releases. Then we can tell users, if
you install a rc, you are probably going to have broken plugins, so if
you don't want that, wait until the final comes out.

When we do a final release, I feel we should have the following done
before any public targeted release announcements go out:

* Have compatible versions of plugins out.
* Have key installers done, eg debs in the ppa, Windows installers out, etc..

This leaves the risk of delaying the releases, so if it is know that
there is going to be a delay with one of the above, the RM can decide
to send out the announcement, with a note that x is currently not
available, but this needs to be avoided.