aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKatie Hockman <katie@golang.org>2020-02-04 12:48:20 -0500
committerKatie Hockman <katie@golang.org>2020-02-04 19:45:51 +0000
commita744be42f9427a3b20e7e179e4b9831dbcf27f4c (patch)
tree18bc8775807966ebb9f02afd42e17ae583ea481d
parente6ebbe0d20fe877b111cf4ccf8349cba129d6d3a (diff)
downloadgo-a744be42f9427a3b20e7e179e4b9831dbcf27f4c.tar.gz
go-a744be42f9427a3b20e7e179e4b9831dbcf27f4c.zip
doc: remove paragraph break for upgrading to modules
Previously, the release notes broke up the sentences that modules is now ready for production use and where to file issues for migration problems into separate paragraphs. This made it look like the migration paragraph was about upgrading to 1.14, not to modules, and made the reading a bit confusing. Now the entire idea is in one paragraph. Change-Id: I10bddfb8aba5f5909ac6842f25e3e97d505835e6 Reviewed-on: https://go-review.googlesource.com/c/go/+/217720 Run-TryBot: Katie Hockman <katie@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
-rw-r--r--doc/go1.14.html3
1 files changed, 0 insertions, 3 deletions
diff --git a/doc/go1.14.html b/doc/go1.14.html
index d3199cb0e9..186899e680 100644
--- a/doc/go1.14.html
+++ b/doc/go1.14.html
@@ -27,9 +27,6 @@ Do not send CLs removing the interior tags from such phrases.
<p>
Module support in the <code>go</code> command is now ready for production use,
and we encourage all users to migrate to Go modules for dependency management.
-</p>
-
-<p>
If you are unable to migrate due to a problem in the Go toolchain,
please ensure that the problem has an
<a href="https://golang.org/issue?q=is%3Aissue+is%3Aopen+label%3Amodules">open issue</a>