Hands-On Software Engineering with Golang

Managing the source code for multiple package versions

One thing that may have you as odd about the previous section is the fact that while I keep going on about the publishing version x.y.z of the weather package, the section content itself is devoid of any information regarding the actual process involved in publishing a package.

At this point, you might also be asking yourself the question, if we have released multiple major versions of a package, how do we manage the source code for each released version? After all, as the package authors, we can opt to maintain and support several major or major/minor combinations of package versions in parallel and each version can potentially follow its own release cycle. For example, we can work on ...