Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
x/build/cmd/tip: migrate beta.golang.org to tip GKE service #25978
beta.golang.org runs on a GCE VM in a somewhat ad-hoc config.
Now that tip.golang.org on GKE is stable (I think?), let's nuke the weird VM and just make tip.golang.org and beta.golang.org have the same IP and be served by the same place.
The difference between betas and tip is always tiny anyway, and there's basically never a case where we want beta.golang.org to serve something older than tip. If anything, it's been tedious logging into beta.golang.org regularly during the beta/rc cycle and running "git pull" and restarting systemd services when needed.
I have some comments/questions to understand this better. I'm not against this, you're in a better position to know if the work maintaining beta isn't justified.
If I understand this issue, once resolved, tip and beta will both always serve the exact same Go version, is that right?
My understanding of beta was that it's supposed to be the latest beta or RC release, whereas tip is latest
FWIW, there were a few times in the last few years when tip was broken (for a few hours) but I could fall back to beta in the meantime. It's certainly rare though.
If my understanding is right and the plan is to have tip and beta always serve the exact same version, why not just drop beta completely and leave only tip?
That's effectively what we're doing, but we're redirecting beta.golang.org URLs to tip.golang.org so we don't break any links.
… tip We're turning down the old (and neglected) beta.golang.org godoc VM. It's not different enough from tip.golang.org, which is more reliable than it used to be. Now beta.golang.org will just redirect to tip. Updates golang/go#25978 Fixes golang/go#21073 Change-Id: Iae7fe4c82c14cec7381e75a2e214210d38b6e623 Reviewed-on: https://go-review.googlesource.com/c/120056 Reviewed-by: Filippo Valsorda <email@example.com> Reviewed-by: Dmitri Shuralyov <firstname.lastname@example.org> Reviewed-by: Bryan C. Mills <email@example.com>