Changes on gonuts.org (now gopkg.in)

Thanks to the good feedback provided both publicly and privately, a
number of changes were done to make the versioning github.com
redirector match people's expectations better:

1) Multiple people complained about the domain name; it's now
"gopkg.in", inspired by Simon Menke's fork of the redirection concept.

2) There were also multiple complaints about the go- prefix in
repositories; this is gone.

3) Some people prefer the use of tags and branches for versioning,
instead of the repository name. This works now, using the approach
described by Simon Menke (filtering of refs plus redirect on object
fetch). As a side effect of this feature, repositories that use tags
or branches to mark the version will git clone from gopkg.in, so the
original approach of using a versioned repository name still works for
those that prefer it. No configuration is necessary for either.. just
use your preferred approach and gopkg.in will figure it.

As a consequence of these changes, the package

gonuts.org/v1/yaml => github.com/go-yaml/go-yaml-v1

can now be

gonuts.org/v1/yaml => github.com/go-yaml/yaml

and contains a branch "v1".

The documentation at https://gopkg.in was updated to reflect those
changes, although there isn't much more to it than what's above.

According to the logs, by now all of the packages that were using
gonuts.org since the announcement were migrated and are working
properly on gopkg.in.

There are more improvements to come, but a couple of these were
disruptive, so it's good to have them in place before more people
start using it.


gustavo @ http://niemeyer.net

This should be gopkg.in/v1/yaml, of course.


gustavo @ http://niemeyer.net

Just what the doctor ordered!

Big thanks!

Another batch of improvements has landed with the following changes.
These are all covered in the documentation at https://gopkg.in as
well.

4) Much better error reporting

The service now says what it is trying to do that is not working. For example:

https://gopkg.in/v1/bad-docs
https://gopkg.in/v2/docs
https://gopkg.in/bad-user/v1/docs

The error pages are not visually pleasing yet, but that's a secondary
issue that will be solved in due time.


5) Full version support

The version numbers used in the URL and in the GitHub repository must
look like "v1", "v1.2" or "v1.2.3", where the numbers match the
semantic versioning scheme of vMAJOR[.MINOR[.PATCH]].

When using branches or tags, gopkg.in also understands that a version
such as "v1" may be satisfied by a tag or branch "v1.2" or "v1.2.1" in
the repository, and will select the best match satisfying the
requested version.


6) Default version zero

Version zero (v0) is reserved for packages that are so immature that
offering any kind of API stability guarantees would be unreasonable.
This is equivalent to labeling the package as alpha or beta quality.

It also makes sense to say that every Go package in GitHub that is not
being versioned is in fact unstable, so gopkg.in will now consider
repositories that have no tags or branches matching the version
pattern as having its master branch as v0.

This implies that every Go package in GitHub is now addressable by
gopkg.in. For example:

gopkg.in/niemeyer/v0/qml

This is just an easy way to get started, though, and to avoid problems
should only be used once the maintainers encourage the use of
gopkg.in.


Please let me know if you have any comments or find any problems.


gustavo @ http://niemeyer.net

Yeah, the error reporting was pretty bad. It should be much better
now. Please let me know if you find issues again.


gustavo @ http://niemeyer.net

Cool project!

I found one typo on http://godoc.org/gopkg.in/v1/docs, "verioning".
I'm assuming you meant versioning.

brian

It must be doable. I'll check with Gary what we might do to have this working.


gustavo @ http://niemeyer.net

Thanks. That's fixed.
--

gustavo @ http://niemeyer.net

Indeed. There's a fine line there, but it's definitely wrong to report
these as reliable. I'll drop these from the description.

Thanks for the feedback,


gustavo @ http://niemeyer.net

There are now two instances of the service running, on New York and
San Francisco, with automatic failover setup so that the service
should remain up even if some bad things happen.

In a moment I'll take one of them down to ensure it's all working
properly, so you may see a short hiccup before the secondary takes
place.

All went well. The service can now survive traditional crashes and
network outages without me being around.

Hi Gustavo,
Any chances this gets extended to working with Mercurial repo's (on
Github), and with Bitbucket (git + hg)?

________________________________________________________________________
"Perfection seems to be achieved, not when there is nothing more to add,
but when there is nothing left to take away." - A. de Saint-Exupéry

There's a good chance we'll add other services. Let's consider that
after we gather some more experience.


gustavo @ http://niemeyer.net

Ah, sorry about that. I'm happy to fix it. What's the actual repository name?
> For more options, visit https://groups.google.com/d/optout.

If you have a project you're willing to use it with, I can do
something about it sooner rather than later.

Hey Alex,
We do have failover in place, in the sense that multiple machines have
to die for the service to fall down, but having the same URL pointing
to multiple code sources seems problematic, as they could easily go
out of sync and give different results. It's also hard to avoid a DDoS
in an effective way.. the system may look offline, even if neither
github or gopkg.in are offline, simply because the network path is
overloaded.
Thanks for the offer. DNS failover is already in place, but I'll
certainly get in touch if further help is necessary.


gustavo @ http://niemeyer.net