Release readiness communication [was Re: bzr 2.1 timeline]

[Ian Clatworthy]

James Westby wrote:
> On Thu Sep 10 07:32:05 +0100 2009 Ian Clatworthy wrote:

>> * getting plugins compatible with 2.0 tested, packaged and announced
> 
> Do we have a point of co-ordination for this? It would be silly for
> each of us that rely on this information to track it individually.
> 
> Do we need some way of tracking this at every release? (Say a bug
> with a task open on each plugin and use the statuses to track
> what is ready?)

Do bugs in LP support sub-tasks now? (Sorry for my ignorance). If so,
that's certainly an option.

Another option is a Wiki page with columns something like ...

* plugin name
* version to ship
* released (Y/N)
* in PPA (Y/N)

Then each of us building a package, meta-package or installer knows what
versions to grab and whether they're ready or not.

I guess we could use the same page for tracking whether packages are
built yet for the various OSes, so the release manager knows whether the
public announcement can go out yet or not.

Anyhow, we certainly need some way of tracking it. If possible, I'd like
one place where plugin maintainers, platform packagers and the release
manager can communicate release readiness information with each other.

Ian C.