dependency branches for 1.21

[roger peppe]

In general, let's please move toward using gopkg.in to maintain stable APIs.
Then we should be able to use the latest version of all dependencies
without thinking too much, and there will always be a branch available
for backported changes.


On 5 February 2015 at 20:38, Horacio Duran <horacio.duran at canonical.com> wrote:
> Hey, I have been backporting licencing fixes into utils, syslog and testing
> for 1.21 release. While doing this I noticed that the revs testing and utils
> used in 1.21 are quite far from what we use in master so, in order to
> prevent bringing unwanted changes to 1.21 by bumping the deps to HEAD I
> branched utils and testing at the version they where in 1.21.
> Both repos now have a 1.21 branch where all backported changes should go, if
> any.
> I presume I will be doing the same for 1.22 If I find the case to be the
> same.
> Cheers.
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>