You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some steps in this checklist could be entirely automated. It would be great if @coqbot could take care of them whenever we check a box. This would include creating the missing milestone, the backporting project, opening the PR bumping the version numbers, opening the PR consolidating the release notes, and even creating the next release issue from the release process doc.
Some actions like pushing tags should not be done when checking boxes (which can happen accidentally) but when merging PRs doing version number bumps instead. The release branch could also be created automatically upon merging the next alpha bump in master.
The text was updated successfully, but these errors were encountered:
The current release process includes creating a release issue (cf. coq/coq#8445, coq/coq#8446, coq/coq#10843, coq/coq#11157, coq/coq#12334). These issues were created by copy-pasting the content of
dev/doc/release-process.md
.Some steps in this checklist could be entirely automated. It would be great if @coqbot could take care of them whenever we check a box. This would include creating the missing milestone, the backporting project, opening the PR bumping the version numbers, opening the PR consolidating the release notes, and even creating the next release issue from the release process doc.
Some actions like pushing tags should not be done when checking boxes (which can happen accidentally) but when merging PRs doing version number bumps instead. The release branch could also be created automatically upon merging the next alpha bump in master.
The text was updated successfully, but these errors were encountered: