diff options
| author | d-tsuji <dram.dt.shonan@gmail.com> | 2020-09-05 20:20:57 +0900 |
|---|---|---|
| committer | Emmanuel Odeke <emm.odeke@gmail.com> | 2020-09-05 21:52:30 +0000 |
| commit | d241bfce965a553d85e6d650ce17acc6ac425276 (patch) | |
| tree | 0e1269e5d369dc6784a132cb0a76e0abf53f693a /content/toward-go2.article | |
| parent | 3841cf6a3ea0effaf63edb48a2cc0973c56ce756 (diff) | |
content: fix link to "Go version 1 is released"
Change-Id: Iac52d9fc7044fa5cecf19e6580688a1ab49cb156
Reviewed-on: https://go-review.googlesource.com/c/blog/+/253099
Run-TryBot: Emmanuel Odeke <emm.odeke@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Emmanuel Odeke <emm.odeke@gmail.com>
Diffstat (limited to 'content/toward-go2.article')
| -rw-r--r-- | content/toward-go2.article | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/content/toward-go2.article b/content/toward-go2.article index 0c506af..ae7f6df 100644 --- a/content/toward-go2.article +++ b/content/toward-go2.article @@ -37,7 +37,7 @@ and leading to the [plan for Go 1](https://blog.golang.org/preview-of-go-version </div> With more help from the Go community, we revised and implemented that -plan, eventually [releasing Go 1](https://blog.golang.org/go-version-1-is-released) on March 28, 2012. +plan, eventually [releasing Go 1](https://blog.golang.org/go1) on March 28, 2012. <div style="margin-left: 2em;"> .image toward-go2/go1-release.png _ 556 @@ -52,7 +52,7 @@ In the years leading to Go 1, we changed Go and broke everyone's Go programs nearly every week. We understood that this was keeping Go from use in production settings, where programs could not be rewritten weekly to keep up with language changes. -As the [blog post announcing Go 1](https://blog.golang.org/go-version-1-is-released) says, the driving motivation was to provide a stable foundation +As the [blog post announcing Go 1](https://blog.golang.org/go1) says, the driving motivation was to provide a stable foundation for creating reliable products, projects, and publications (blogs, tutorials, conference talks, and books), to make users confident that their programs would continue to compile and run without change for |