Skip to content

Move PRs to newer milestone when doing RC-1#106

Merged
frouioui merged 1 commit into
mainfrom
move-milestones-item-during-code-freeze
Jun 21, 2024
Merged

Move PRs to newer milestone when doing RC-1#106
frouioui merged 1 commit into
mainfrom
move-milestones-item-during-code-freeze

Conversation

@frouioui

Copy link
Copy Markdown
Member

During RC-1's code freeze, we create the new release branch and a new milestone (i.e. v21.0.0), however we were not moving the PRs from the previous milestone (v20.0.0), into the new one (v21.0.0). Meaning that we had PRs on the main branch that were still assigned to the v20.0.0 milestone although these specific PRs were never going to make it to the v20.0.0 release (maybe they would have thanks to backport, but that does not matter).

Eventually during the release step of GA, we migrate all the opened PRs from the v20.0.0 milestone to the new v21.0.0 milestone, but that happens too late already.

This PR fixes this issue by migrating all opened PRs from the current to the next milestone during RC-1's code freeze.

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
@frouioui frouioui merged commit f3defd0 into main Jun 21, 2024
@frouioui frouioui deleted the move-milestones-item-during-code-freeze branch June 21, 2024 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants