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 RELEASING.md #1677

Merged
merged 1 commit into from
Apr 24, 2024
Merged

Update RELEASING.md #1677

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: 1 addition & 1 deletion RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ A draft PR can be created, but before releasing consider the following:

* Are there any pending pull requests which should be included in the next release?
* Are they blockers?
* Are there any unresolved issues which should be resolved before the next release?
* Are there any unresolved issues which should be resolved before the next release? Check the release [blockers milestone](https://github.com/open-telemetry/opentelemetry-rust/milestones) for every release
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could have been merged with the above about PRs.

* Bring it up at a SIG meeting, this can usually get some of these questions answered sooner than later. It will also
help establish a person to perform the release. Ideally this can be someone different each time to ensure that the
process is documented.
Expand Down
Loading