Skip to content

Commit b7994a6

Browse files
authored
update versioning instructions (#275)
1 parent ddf6370 commit b7994a6

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

RELEASE.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,12 @@ Follow these instructions for creating a Release Version.
1717

1818
### Pre-Release Tasks
1919

20+
#### Determine the correct version to be released
21+
Go to the [SQL releases page](https://jira.mongodb.org/projects/SQL?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased), and check the content of the tickets that are included in the current release. The fix version by default is a patch version. If there is a backwards incompatible API change in the tickets that are set to be released, we should instead update the major version; if there are new features added in the tickets set to be released, we should instead update the minor version. To do so, update the version on the [SQL releases page](https://jira.mongodb.org/projects/SQL?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased) under "Actions". This will update the fix version on all of the tickets as well.
22+
2023
#### Start Release Ticket
2124
Move the JIRA ticket for the release to the "In Progress" state.
22-
Ensure that its fixVersion matches the version being released.
25+
Ensure that its fixVersion matches the version being released, and update it if it changed in the previous step.
2326

2427
#### Ensure Evergreen Passing
2528
Ensure that the build you are releasing is passing the tests on the evergreen waterfall.

0 commit comments

Comments
 (0)