Skip to content

CXX-3002 update release notes to account for new branch protection rules #1385

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

Merged
merged 5 commits into from
Apr 18, 2025
Merged

CXX-3002 update release notes to account for new branch protection rules #1385

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
1a728fc
CXX-3002 update release notes to account for new branch protection rules
eramongodb Apr 18, 2025
bb1ea5f
Add instructions to "lock" the prior stable release branch
eramongodb Apr 18, 2025
0aa3736
The repo admin must lock the branch, not the releaser
eramongodb Apr 18, 2025
a8f73d4
Tweak instructions to reference MANA for team membership management
eramongodb Apr 18, 2025
01be109
Use hyperlinks for references to team and MANA
eramongodb Apr 18, 2025
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
12 changes: 12 additions & 0 deletions etc/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,12 @@ Verify there are no unexpected errors or issues.

## Release Steps

### Branch Protection Rules

The release process may require creating new branches, new tags, and directly pushing to development branches. These operations are normally restricted by branch protection rules.

When assigned the responsibility of performing a release, submit a request to a repository administrator to be temporarily added to the [dbx-c-cxx-releases](https://github.com/orgs/mongodb/teams/dbx-c-cxx-releases/) team for the duration of the release process. The team member must be added via [MANA](https://mana.corp.mongodb.com/resources/68029673d39aa9f7de6399f9) (the GitHub team is usually empty; no member has the maintainer role).

### Update CHANGELOG...

This step depends on the release type.
Expand Down Expand Up @@ -848,6 +854,12 @@ The C++ Driver Team

Add an entry to the [C/C++ Release Info](https://docs.google.com/spreadsheets/d/1yHfGmDnbA5-Qt8FX4tKWC5xk9AhzYZx1SKF4AD36ecY) spreadsheet documenting the date, release version, author (of the release), and additional comments.

### Update Branch Protection Rules

Notify a repository administrator that the previous stable release branch (which will no longer recieve any further updates) may now be "locked" by adding it to the list of branches in the "Restrict Branch Updates" ruleset.

Once the release process is complete, use [MANA](https://mana.corp.mongodb.com/resources/68029673d39aa9f7de6399f9) to remove yourself from the [dbx-c-cxx-releases](https://github.com/orgs/mongodb/teams/dbx-c-cxx-releases/) team or request a repository administrator to remove you instead.

## Packaging

### vcpkg
Expand Down