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

Give attribution to new contributors at release #2438

Merged
merged 1 commit into from
Nov 7, 2024
Merged

Give attribution to new contributors at release #2438

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
2 changes: 2 additions & 0 deletions docs/Contributing/release.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ These are the general steps to prepare and finalize a release:
time. This prevents an accidental release.
#. A release manager will update the draft as PR's are committed to the repository to help keep track of
the release cadence progress. As PR's are added to sections the ``* Nothing for this release`` is removed.
#. As PR's are added to the draft release notes, pay attention to the contributor. If a new contributor has
opened a PR, call it out --- "With this release we welcome @[GithubID] as a new contributor (#[PR])"
#. Multiple PR's can be combined on a single bullet line. Documentation updates are often done this way.
#. When we are getting close to crossing one of the release candidate thresholds, the release manager will
post to the ``#releases-project`` channel in the ``LT.DEV`` section on the Longturn Discord server. The
Expand Down
Loading