AFAIK I created v4 because of a breaking change to testing importing
gocheck from its new location, but we have to update the world before we
can land the dependencies.tsv changes.
John
=:-
On Sep 23, 2014 4:24 PM, Dimiter Naydenov dimiter.nayde...@canonical.com
wrote:
-BEGIN PGP SIGNED
On 23 September 2014 13:23, Dimiter Naydenov
dimiter.nayde...@canonical.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I noticed a recent change in juju/juju bumping the revision of a
sub-repo (in this case juju/charms), which should be fine if the
sub-repo wasn't
Disclaimer: one of the commits mentioned here is mine.
I think I agree with Roger on this - as long as the changes to a package
are backwards compatible, incrementing the version number seems a bit over
the top. To begin with, it would mean quickly incrementing versioned
package versions (would
There are packaging nuances to versioning
On Tue, Sep 23, 2014 at 9:57 AM, Nate Finch nate.fi...@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)
