x/build/cmd/gopherbot: pick next minor release milestone, not "latest" open one, in setMinorMilestones #57031
Labels
Builders
x/build issues (builders, bots, dashboards)
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
It's useful to be able to create a future Go version milestone ahead of time to hold an issue that is known not to need attention for some time, and we do this ocassionally (e.g., #41152, #56836, etc.).
gopherbot's setMinorMilestones task gets confused when this happens for minor release milestones, and starts to assign backport issues to the latest open minor milestone, rather than the upcoming one:
We should change it to pick the upcoming minor release by default. We have current Go version information available, making it easier to do this than in 2018 when this task was originally added. I'll send a CL.
CC @golang/release, @rsc.
The text was updated successfully, but these errors were encountered: