Need updated lp:gwacl

[John Meinel]

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.

John
=:->
On Jul 22, 2013 5:46 PM, "David Cheney" <david.cheney at canonical.com> wrote:

> Why does the bot need this ?
>
> The bot should checkout the revision it has been asked, the getting
> all the deps is as simple as
>
> go get launchpad.net/juju-core/...
>
> Yes, none of those dependencies are version, but that doesn't appear
> to be any different from what we have at the moment.
>
> On Tue, Jul 23, 2013 at 1:52 AM, Raphaël Badin
> <raphael.badin at canonical.com> wrote:
> > The latest trunk requires some changes from lp:gwacl, so please update
> your
> > working tree.
> >
> > Note that the most recent version of gwacl embeds a forked crypto/tls
> > package which supports TLS renegociation.  go-curl is not needed any
> more.
> >
> > Cheers,
> >
> > R.
> >
> > --
> > Juju-dev mailing list
> > Juju-dev at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130723/7130f5ba/attachment-0001.html>