[Buildbot-devel] How to have blamelist include all blamed checkins since last successful build?

Dustin J. Mitchell dustin at v.igoro.us
Mon Oct 15 12:40:32 UTC 2012

On Mon, Oct 15, 2012 at 7:37 AM, tom fogal <tfogal at sci.utah.edu> wrote:
> On 10/14/2012 07:09 PM, Dustin J. Mitchell wrote:
>> If my tyranny results in a plugin architecture growing up earlier
>> than that, that's great, with the caveat that per semver.org we won't
>> guarantee stable APIs until 1.0.0.
> Speaking of which, when is this coming?
> My projects are long past the point where I started relying on the existing
> API: changes to the API or DB are really painful for us.  To the point where
> we've basically stopped upgrading because it's too much work to keep on top
> of BBot, especially given I am not nearly as deep into this as I once was.
> So, for us, buildbot is stable, even if it isn't.  I would bet others are in
> the same boat.  It seems Chromium && mozilla are only keeping up by having
> people very dedicated to having feet in both camps.  I don't feel that's a
> good model; we can't afford that, for example.

This is exactly why we need a stable API.  That doesn't mean it's easy, though!

The current de-facto API is deeply flawed, so standardizing on that
would be no better than the approach you (and many others) have taken
- not upgrading.  The work on the nine branch is paying attention to
configuration compatibility and, as much as possible, API
compatibility - both forward and backward.  To the extent that we
perceive something as part of an API, we will be careful in changing
it and include information about the change in the release notes.  But
we will change things where it's necessary.

Looping back to earlier emails in the thread, this is one reason I
want to avoid merging partial features -- it often commits us to
supporting problematic APIs that are not forward-compatible, or
breaking those APIs later.

To answer your direct question, it will be ready when the few of us
working on it are finished.  Many hands would make lighter work :)


P.S. To clarify the point, Buildbot is not a Mozilla responsibility of
mine - I work on Buildbot in my spare time.

More information about the devel mailing list