You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MAINTAINERSHIP.md
+1
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ If any maintainer thinks an issue is major, it is major.
30
30
31
31
#### Releasing, Publishing
32
32
33
+
* Releases adhere to [semver](https://semver.org/)
33
34
* To cut a release, an issue should be opened for it and reach the required approval based on the above `Categories of Work` section above
34
35
* When progress is possible, the issue may be closed and the proposer may publish to crates.io. This is controlled by those in the [crate publishers organization-level team](https://github.com/orgs/rust-rocksdb/teams/crate-publishers).
35
36
* Releases should have an associated tag pushed to this repo. I recommend doing this after the publish to crates.io succeeds to prevent any mishaps around pushing a tag for something that can't actually be published.
0 commit comments