-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/website: make it safer to make changes to draft release notes #37072
Comments
Given that the release notes are largely HTML (with a minor template component) inside the |
I've searched through the release notes for many Go releases, and I'm seeing that most of them do not actually use the template functionality for anything, other than to escape I see that
But none of the other releases (1.1 through 1.14) do. |
Change https://golang.org/cl/218058 mentions this issue: |
#37047 is closely related, in that it would also (ideally) detect issues in generated HTML during TryBot runs. |
Change https://golang.org/cl/218217 mentions this issue: |
This just bit me on CL 217877, too — and it did have a TryBot +1. I think we really do need to test the rendered templates in some form. (Reopening.) |
I forgot to escape them in CL 217877, and the TryBots don't currently catch template errors in HTML docs. Updates golang/go#37042 Updates golang/go#37072 Change-Id: Ia7b82a9c9b85914f224c04050bfbe3747d5a3acc Reviewed-on: https://go-review.googlesource.com/c/website/+/218217 Run-TryBot: Bryan C. Mills <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]>
The scope of this issue was about the draft release notes, and that's been fixed. I'll revert the issue to reflect that. Opened #37090 to track testing improvements for catching problems on pages that still use template mode. |
Change https://golang.org/cl/229079 mentions this issue: |
There are no template features being used in either of these two files, so convert them to regular non-template HTML files. Having template be off has proven to be a safer default, and it uses less CPU. For golang/go#37070. For golang/go#37072. For golang/go#37090. Change-Id: Ib0de115e58c51a9660d648dbb8793fcaae9a7197 Reviewed-on: https://go-review.googlesource.com/c/website/+/229079 Reviewed-by: Alexander Rakoczy <[email protected]>
Right now we rely on https://tip.golang.org (served by the
golang.org/x/build/cmd/tip
command), the server that automatically deploys and serves the latest x/website and Go repository commits, for sharing draft release notes such as at https://tip.golang.org/doc/go1.14.Always showing the latest Go+x/website commits means that changes to the draft release notes are previewed very quickly, which is great for seeing the latest state and for spotting problems very quickly. However, release notes use template processing, and if there is an error in the template, an error is displayed. That makes editing the draft release notes a risky process, which can cause times where draft release notes can't be viewed (see #37070 recently).
We should find a way to make the process safer, but hopefully without negatively affecting the convenience of being able to see the latest commits without manual effort.
/cc @golang/osp-team
The text was updated successfully, but these errors were encountered: