From: Bryan C. Mills Date: Fri, 24 Jan 2020 15:26:24 +0000 (-0500) Subject: doc/go1.14: note that module support is ready for production use X-Git-Tag: go1.14rc1~57 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=4615b39514d1463c1cfed624ff3629ab1580a915;p=gostls13.git doc/go1.14: note that module support is ready for production use The public proxy and checksum database launched with Go 1.13 have been running smoothly, pkg.go.dev is serving module-aware documentation, and in 1.14 we have improved the vendoring workflow and finished Subversion support to reach parity with GOPATH mode for users of those features, updated documentation (including the “How to Write Go Code” intro document) and published blog posts describing common modes of usage, and improved the migration path for existing v2+ modules by making version resolution less aggressive about "+incompatible" major versions. We (always) have more fit-and-finish work to do, but at this point we believe that module mode will provide a better user experience than GOPATH mode for most users, including in production use. Change-Id: I897e0a43e3aebe4c90553c414337a46bfc9c2bef Reviewed-on: https://go-review.googlesource.com/c/go/+/216317 Reviewed-by: Jay Conrod Reviewed-by: Katie Hockman Reviewed-by: Russ Cox --- diff --git a/doc/go1.14.html b/doc/go1.14.html index 99d2550680..245b068ce8 100644 --- a/doc/go1.14.html +++ b/doc/go1.14.html @@ -24,6 +24,20 @@ Do not send CLs removing the interior tags from such phrases.

+

+Module support in the go command is now ready for production use, +and we encourage all users to migrate to Go modules for dependency management. +

+ +

+If you are unable to migrate due to a problem in the Go toolchain, +please ensure that the problem has an +open issue +filed. (If the issue is not on the Go1.15 milestone, please let us +know why it prevents you from migrating so that we can prioritize it +appropriately.) +

+

Changes to the language