Skip to content
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.

Sign up for GitHub

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

Update release process #2078

Merged
merged 1 commit into from
Dec 17, 2023
Merged

Update release process #2078

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/Contributing/release.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,10 @@ These are the general steps to prepare and finalize a release:
post to the ``#releases-project`` channel in the ``LT.DEV`` section on the Longturn Discord server. The
main purpose of the post is to alert the developers of a pending cadence threshold and to gauge if we
need to delay in any way or if we are good to proceed as normal.
#. A release manager or another regular contributor will update the ``vcpkgGitCommitId`` value in the CI/CD
build file (:file:`.github/workflows/build.yaml`). Grab the Commit ID of the most recent release from
https://github.com/microsoft/vcpkg/releases. Commit and push a PR. Ensure all of the CI/CD Action runners
complete successfully.
lmoureaux marked this conversation as resolved.
Show resolved Hide resolved
#. When it is time, the release manager will finalize the release notes and ask for an editorial review in the
``#releases-project`` channel. Updates are made as per review.
#. If the release will be the :strong:`first release candidate` towards a stable release, the release manager
Expand Down Expand Up @@ -56,7 +60,7 @@ These are the general steps to prepare and finalize a release:
#. The release manager will open an issue titled ``Review workarounds after <version> release`` with the following text:

We should review the workarounds in the source code and check that they are still needed. Some
workarounds are documented here: :doc:`Workarounds`.
workarounds are documented here: :doc:`workarounds`.

#. When all the CI actions are complete, the release manager will make a post in the ``#news-channel`` on the
Longturn.net Discord server.
Expand Down
Loading