Need updated lp:gwacl

[Julian Edwards]

On 23/07/13 11:50, John Meinel wrote:
> We have 2 options. We peg the dependecy versions the bot is using and
> update them manually on request. Or the bot grabs the latest on every
> build. (And the mythical but not yet implemented we actually track
> dependency versions.)
> 
> We are going with manual updating. Without it, as soon as Red squad
> would commit a possibly incompatible change to gwacl, we could no longer
> land *any* patches to juju-core itself until the patch that fixes
> compatibility with gwacl lands.
> 
> Trackings deps would mean that when the patch to maintain compatibility
> with an updated gwacl could also specify that we should depend on the
> new gwacl.
> 
> This lets sub teams iterate rapidly on their code and it doesnt break
> the rest of us until they say it is ready.

FWIW I agree wholeheartedly with this approach.

If you just pull tip of all dependencies every time you do a bot run,
you're quite frankly insane as you're going to get inconsistent runs
that are out of your control.  Remember that it's pulling in projects
that we don't own.

We take this approach with MAAS too - all dependencies are explicitly
versioned for maximum stability.

There is friction with Go projects, however, because there's no easy way
of setting dependency versions which means someone has to do a manual
bot update.

It might be worth having a separate file in the core codebase that lists
revision numbers for each dependency which would allow both developers
and users to re-create an environment to an exact specification, because
I can virtually guarantee at the moment that developers and the bot will
be working to different revnos of dependencies.