aboutsummaryrefslogtreecommitdiff
path: root/vendor/adler/RELEASE_PROCESS.md
diff options
context:
space:
mode:
authorValentin Popov <valentin@popov.link>2024-07-19 15:37:58 +0300
committerValentin Popov <valentin@popov.link>2024-07-19 15:37:58 +0300
commita990de90fe41456a23e58bd087d2f107d321f3a1 (patch)
tree15afc392522a9e85dc3332235e311b7d39352ea9 /vendor/adler/RELEASE_PROCESS.md
parent3d48cd3f81164bbfc1a755dc1d4a9a02f98c8ddd (diff)
downloadfparkan-a990de90fe41456a23e58bd087d2f107d321f3a1.tar.xz
fparkan-a990de90fe41456a23e58bd087d2f107d321f3a1.zip
Deleted vendor folder
Diffstat (limited to 'vendor/adler/RELEASE_PROCESS.md')
-rw-r--r--vendor/adler/RELEASE_PROCESS.md13
1 files changed, 0 insertions, 13 deletions
diff --git a/vendor/adler/RELEASE_PROCESS.md b/vendor/adler/RELEASE_PROCESS.md
deleted file mode 100644
index 71a3673..0000000
--- a/vendor/adler/RELEASE_PROCESS.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# What to do to publish a new release
-
-1. Ensure all notable changes are in the changelog under "Unreleased".
-
-2. Execute `cargo release <level>` to bump version(s), tag and publish
- everything. External subcommand, must be installed with `cargo install
- cargo-release`.
-
- `<level>` can be one of `major|minor|patch`. If this is the first release
- (`0.1.0`), use `minor`, since the version starts out as `0.0.0`.
-
-3. Go to the GitHub releases, edit the just-pushed tag. Copy the release notes
- from the changelog.