For the record, we can easily send branches against charms that matter
to us for this particular case (as we will for few other
landscape-owned branches waiting for review [1] [2] [3], hint hint :)
).
But this seems like a problem in need of a more general (and scalable) solution.
- Chris (tribaa
This sounds a lot like the static build problem: once a piece of shared
code is fixed/updated, how to make sure everything using it gets rebuilt?
charm-helpers is such a case. It's shared code used by a growing number of
charms.
Case in point: https://bugs.launchpad.net/charm-helpers/+bug/1317980
