Release readiness communication [was Re: bzr 2.1 timeline]

[Martin Pool]

2009/9/10 James Westby <jw+debian at jameswestby.net>:
> On Thu Sep 10 12:30:11 +0100 2009 Ian Clatworthy wrote:
>> Do bugs in LP support sub-tasks now? (Sorry for my ignorance). If so,
>> that's certainly an option.
>
> I was meaning a single bug with tasks on bzr and each of the plugins
> that is likely to be version dependent.
>
>    bzr               Fix Committed           ...
>    bzr-svn           In Progress             ...
>
> but given the information that you would like to capture:

Yes, we can do that, though I see you already made
<http://bazaar-vcs.org/Releases/2.0.0>

>> * plugin name
>> * version to ship
>> * released (Y/N)
>> * in PPA (Y/N)
>
> a bug isn't going to cut it, and has other drawbacks, so I think a wiki
> page is the better idea.
>
>> 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.

It seems like we could do something here as far as just checking that
everything in the PPA can be simultaneously installed.  Robert has a
script that detects unintentional conflicts in the main archive, so
perhaps we should just run that on our ppa.  This would be useful
beyond 2.0.0, and avoid needing manual checking.  It would also be a
nice feature for Soyuz to offer automatically, eventually.

-- 
Martin <http://launchpad.net/~mbp/>