-
Notifications
You must be signed in to change notification settings - Fork 76
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update README.md now that we have releases, and detail the release pr…
…ocess Reviewed By: strulovich Differential Revision: D20995039 fbshipit-source-id: d6442d9208b31864e4cf0f870baa2f0fca3485a3
- Loading branch information
1 parent
59239c6
commit 1e47813
Showing
2 changed files
with
44 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# Releasing a New `ktfmt` Version | ||
|
||
1. Land a diff bumping the version to a non-SNAPSHOT version (e.g., `0.11`). For example, https://github.com/facebookincubator/ktfmt/commit/a674918aa9fddffed5321da3828fa028a520a406. Note that there are _2_ places to update. | ||
2. Land another diff, bumping the version to the next SNAPSHOT version (e.g., `0.12-SNAPSHOT`). For example, https://github.com/facebookincubator/ktfmt/commit/ed2d3d0b363cc04d867f7c9fe84c5a28b1f5c62e | ||
3. git-clone and checkout the commit of the non-SNAPSHOT version. Don't forget a recursive clone to get google-java-format. | ||
3. Obtain the private key used to sign `ktfmt` releases, as well as its passphrase. | ||
4. Run `cd core && mvn -Prelease clean deploy` | ||
5. Enter the passphrase when requested. | ||
6. Create a new release at https://github.com/facebookincubator/ktfmt/releases . Use a previous release as a template. | ||
7. Upload release files by dragging them from `core/target/`. | ||
|
||
This is terribly manual. We'll hopefully soon improve this using GitHub Actions. |