[Buildbot-devel] Release schedule for 0.7.x

[Neil Hemingway]

Brian,

I know you were intending to release buildbot 0.7.10 and the fact that you
haven't suggests that something ($work|$life)? has got in the way.  Someone
on IRC thought that the 0.7.x line was essentially now dead, and no further
releases will be made until 1.0 is ready.  Of course (as with all FLOSS),
this depends entirely on developers' time, so could well be months away.  So
I think it would be sensible to continue with the 0.7.x line until 1.0 has
matured enough to become a viable alternative for real work.

This raises the question of how buildbot get released.  ISTR that you
weren't happy about being the bottleneck for buildbot releases.  What would
need to happen to enable more than one person to be able to build and ship a
release?

I've put together a short list of what I came up with:
* A set of criteria that dictates when a new release is built (perhaps every
six months, maybe when sufficient tickets have been resolved)
* A set of criteria that a release must meet before it is eligible for a
release (all tests pass on all "supported" platforms, etc)
* Access to the downloads area to ship the new release package
* Access to the location where the online docs are held
* Access to the wiki to change the links to the latest version

I've almost certainly missed stuff.

Regards,
Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090106/4e626fca/attachment.html>