Russ Cox
Also: > RELNOTE= comments are obsolete in the current design; authors should instead add a doc/next/*.md file, possibly with a TODO. The relnote todo command would print these out. It's...
I also sent CL https://go-review.googlesource.com/c/build/+/584303 to restore the cutoff date calculation.
I haven't written release notes yet for the synctimer proposal. I'd like to see relnote catch that before I do.
I found https://go-review.googlesource.com/c/build/+/582097 which says: > The cutoff date must now be provided manually on the command line, avoiding errors in calculating it automatically. This seems completely backward to me....
Apologies for the issue comment storm. I seem to have jumped into the middle of work on relnote and it took me a few messages to get up to speed....
Thanks. That info is in x/website/internal/history, but you can't import it. You can do the https fetch to go.dev though. It's template-generated so any simple regexp you use is likely...
Or you could look in master for the git commit that tags the release and use that date. But I thought the problem was that the dev cycle might have...
This is something we can just fix once at the start of each cycle by manually overriding the few false positivies. The cutoff date is also something we can hard-code...
// +build comments need a blank line, because otherwise a package doc comment talking about the +build feature might accidentally turn into a semantically important comment after an unfortunate line...
Are we missing RemoveIn?