A great deal has been written about Go’s package versioning situation (by@nathany in particular). However, at this time, there is no community standardfor managing package versions. Therefore, it is left up to the end developer toensure their software builds safely and reproducibly.

If you use Revel for a production application, it is your responsibility toavoid breakages due to incompatible changes. Your build process should notinvolve “go get”ing the master branch of Revel.

The simplest way to handle this is to check the code for Revel and alldependencies into your repository. If you use git, they can be embeddedefficiently as sub-repos.

Alternatively, try one of the package managers described in the linked article.

• Go package versioning

原文: https://revel.github.io/manual/versions.html