diff options
| author | Agniva De Sarker <agnivade@yahoo.co.in> | 2018-04-14 00:23:09 +0530 |
|---|---|---|
| committer | Andrew Bonventre <andybons@golang.org> | 2018-04-13 19:50:50 +0000 |
| commit | 7edc962a942e4a9d5e06dde79299f7fc5605f000 (patch) | |
| tree | d05d3cbb132e60ace21a28184833cc4b31ef59c3 /content/go-becomes-more-stable.article | |
| parent | efc7460c787535c46feadda9f7c395f16a615306 (diff) | |
content: update all golang.org links to https
Ran sed -i 's/\[\[http:\/\/golang.org/\[\[https:\/\/golang.org/g' *.article
Change-Id: I88acc5104e1a3fc5e9a1cf11b600b657202d8997
Reviewed-on: https://go-review.googlesource.com/106955
Run-TryBot: Andrew Bonventre <andybons@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>
Diffstat (limited to 'content/go-becomes-more-stable.article')
| -rw-r--r-- | content/go-becomes-more-stable.article | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/go-becomes-more-stable.article b/content/go-becomes-more-stable.article index e33d2c5..17325e4 100644 --- a/content/go-becomes-more-stable.article +++ b/content/go-becomes-more-stable.article @@ -8,7 +8,7 @@ Andrew Gerrand The Go project is moving fast. As we learn more about Go we are compelled to change our tools, libraries, and occasionally even the language itself. We permit backward-incompatible changes so that we can learn from, rather than immortalize, our mistakes. We believe flexibility at this stage of Go’s development is essential to the project’s development and, ultimately, its longevity. -Since Go's launch we have been making releases approximately once a week. Accompanying each release are [[http://golang.org/doc/devel/release.html][notes describing what changed]], with any backwards-incompatible changes signposted. Questions I hear often are "Is Go stable? How can I be sure that I won’t have to update my Go code every week?" The answer to those questions are now "Yes," and "You won't." +Since Go's launch we have been making releases approximately once a week. Accompanying each release are [[https://golang.org/doc/devel/release.html][notes describing what changed]], with any backwards-incompatible changes signposted. Questions I hear often are "Is Go stable? How can I be sure that I won’t have to update my Go code every week?" The answer to those questions are now "Yes," and "You won't." With this week’s release we’re introducing a new release tagging scheme. We intend to continue with our weekly releases, but have renamed the existing tags from `release` to `weekly`. The `release` tag will now be applied to one hand-picked stable release each month or two. This more relaxed release schedule should make life easier for the average Go programmer. |