Versioned Imports and dependencies.tsv

[Nate Finch]

On Tue, Sep 23, 2014 at 9:52 AM, roger peppe <roger.peppe at canonical.com>
wrote:

>
> That's not quite how it works. For versioned import paths, the version
> is about the API, not the exact implementation. It's entirely
> OK to add new (backwardly compatible) features to a package that
> has a versioned import path (see "When to change the version" in
> http://gopkg.in for details on this).
>
> We use godeps to guarantee stable builds. That means that
> even in the presence of versioned import paths, we still want
> to pin the dependencies for testing purposes, so that we
> get reproducible tests and builds.
>
> Thus godeps and use of gopkg.in are orthogonal, and I think
> that the commits you mention look fine to me.
>

+1

We do need to be careful about not letting fixes fall through the cracks in
cases like this where there are commits to v3 after v4 has been created,
but that's true of any branching of code.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140923/bcbb9ee0/attachment-0001.html>