[Buildbot-devel] Release schedule for 0.7.x

[Axel Hecht]

Hi Neil,

I smell a 0.7.x release not too far out, Dustin has been taking a good deal
of patches.

What I think we should get to before a release is done:

- make a call on what repo we release off. git or darcs, if git, which.
- reanimate http://buildbot.buildbot.net/waterfall, moving that over to
github.
-- we might have to create and deprecate a few builders there. Twisted up to
8.2.0 should go up, not sure which should go down. Python 2.6, not sure
about 3 (anyone tested that?)

- get a list of pre-release teams. For 0.7.8 or .9, I ran the buildbot tip
against my local install and found a flock of issues not covered by tests.
I'd volunteer to do that again. I also asked joduinn to think about doing
that with the staging environment at Mozilla, they would need some lead time
to plan that, at least. How about others? Don't wanna see "test test test
test ...."? Run your setup upfront, then ;-)

-  Looking at the existing builders on bbn, getting better coverage on VCs
would be good.

- Something that I have seen at the Mercurial wiki was a wiki page with the
upcoming release notes. Creating that or a changelog of some other form is
probably the biggest chunk of work right now :-/ Docs suck.


Personally, I still have another set of bugs that I'd love to get into the
next release, in particular, build log compression (and, unfiled, a separate
build log directory)


My 2 cts.

Axel

2009/1/6 Neil Hemingway <neil.hemingway at greyhavens.org.uk>

> 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
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090106/fce2a4af/attachment.html>