aboutsummaryrefslogtreecommitdiff
path: root/vendor/flate2/MAINTENANCE.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/flate2/MAINTENANCE.md
parent3d48cd3f81164bbfc1a755dc1d4a9a02f98c8ddd (diff)
downloadfparkan-a990de90fe41456a23e58bd087d2f107d321f3a1.tar.xz
fparkan-a990de90fe41456a23e58bd087d2f107d321f3a1.zip
Deleted vendor folder
Diffstat (limited to 'vendor/flate2/MAINTENANCE.md')
-rw-r--r--vendor/flate2/MAINTENANCE.md21
1 files changed, 0 insertions, 21 deletions
diff --git a/vendor/flate2/MAINTENANCE.md b/vendor/flate2/MAINTENANCE.md
deleted file mode 100644
index c032c25..0000000
--- a/vendor/flate2/MAINTENANCE.md
+++ /dev/null
@@ -1,21 +0,0 @@
-This document explains how to perform the project's maintenance tasks.
-
-### Creating a new release
-
-#### Artifacts
-
-* a tag of the version number
-* a new [crate version](https://crates.io/crates/flate2/versions)
-
-#### Process
-
-To generate all the artifacts above, one proceeds as follows:
-
-1. `git checkout -b release-<next-version>` - move to a branch to prepare making changes to the repository. *Changes cannot be made to `main` as it is protected.*
-2. Edit `Cargo.toml` to the next package version.
-3. `gh pr create` to create a new PR for the current branch and **get it merged**.
-4. `cargo publish` to create a new release on `crates.io`.
-5. `git tag <next-version>` to remember the commit.
-6. `git push --tags` to push the new tag.
-7. Go to the newly created release page on GitHub and edit it by pressing the "Generate Release Notes" and the `@` button. Save the release.
-