launchpad-dev team mailing list archive

[Robert Collins <robertc@xxxxxxxxxxxxxxxxx>]

On Fri, Jul 2, 2010 at 8:25 PM, Deryck Hodge <deryck.hodge@xxxxxxxxxxxxx> wrote:
> What do you mean by "broken?"  If you mean "test failure," buildbot
> catches those.  If you mean, "something does not now work on Launchpad
> as it should," then I'm not sure I agree that entirely avoiding that
> condition should be a prerequisite for continuous deployment.  That
> seems a separate issue, regardless of deployment method.  But maybe
> you're thinking something else entirely?

So it will depend on what we mean by trunk - and what the slides that
prompted this thread meant.

If we mean 'stable' or 'db-stable' then by broken I mean 'things that
we find in QA on edge'. If we mean 'devel' or 'db-devel' then I also
mean test failures.

Perhaps we'll just accept the risk - I don't think thats unreasonable,
particularly if we also have rollback mechanisms that are more
effective than we have today; but I don't think we could do it without
considering the risks either.

@Julian If we only rollout one branch, and we develop on the same
branch,and we have a DB change, where does it go, how does it get
controlled, how do we make it work? Not necessarily a hard problem,
but not solved just by having one branch.

-Rob