trouble with dependent repos

[Nate Finch]

Last week, I had trouble landing code in gopkg.in/juju/charm.v6-unstable,
and using that code from master of github.com/juju/juju.  I was hoping
someone could help me figure out a way to avoid problems I've encountered.

A couple times lately, commits that contain backward incompatible changes
have landed in one of the repos juju depends on.  No corresponding fixes
landed in juju, so the HEAD of master of juju can't compile against the
HEAD master of the dependent repo.  Luckily, godeps insulates juju from
these breaking changes, so the master of juju still builds using godeps.

However, the problem comes when I try to land my own changes in the
dependent repo (in this case in charm.v6), and update juju to use my
changes.  If I update dependencies.tsv to my commit in charm.v6, the repo
now includes the breaking changes... and juju won't compile.

Note that this is even true of code in a feature branch of juju, since the
feature branch would still have the same incompatibility with the dependent
repo.

Anyone have ideas on how can we prevent incompatible changes landing in a
dependent repo without the corresponding fixes landing in juju soon
thereafter?

-Nate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20151124/8c8ec1f2/attachment.html>