From 8bf1296992b6579acabcba62cc6cd0efe039c38a Mon Sep 17 00:00:00 2001 From: Robert Griesemer Date: Tue, 28 Jan 2020 08:40:20 -0800 Subject: content/go1.15-proposals.article: use relative links for other blog articles Change-Id: I5ee0c1e2688fe1d42bc03e5435eb7f9eb9944c65 Reviewed-on: https://go-review.googlesource.com/c/blog/+/216626 Reviewed-by: Dmitri Shuralyov --- content/go1.15-proposals.article | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/go1.15-proposals.article b/content/go1.15-proposals.article index 01bfe48..62a3034 100644 --- a/content/go1.15-proposals.article +++ b/content/go1.15-proposals.article @@ -9,7 +9,7 @@ gri@golang.org We are close to the Go 1.14 release, planned for February assuming all goes well, with an RC1 candidate almost ready. Per the process outlined in the -[[https://blog.golang.org/go2-here-we-come][Go 2, here we come!]] blog post, +[[/go2-here-we-come][Go 2, here we come!]] blog post, it is again the time in our development and release cycle to consider if and what language or library changes we might want to include for our next release, Go 1.15, scheduled for August of this year. @@ -81,7 +81,7 @@ always a chance that we missed something important. For that reason we plan to have the proposals implemented at the beginning of the Go 1.15 release cycle (at or shortly after the Go 1.14 release) so that there is plenty of time to gather experience and provide feedback. Per the -[[https://blog.golang.org/go2-here-we-come][proposal evaluation process]], +[[/go2-here-we-come][proposal evaluation process]], the final decision will be made at the end of the development cycle, at the beginning of May, 2020. -- cgit v1.2.3