-
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
**This PR:** - Adds release signing information to `README.md` - Updates instructions in `RELEASING.md` - Updates gemspec: - Adds new authors - Fixes warnings - ...and more
- Loading branch information
1 parent
1c5c8ba
commit 1c40eb7
Showing
3 changed files
with
31 additions
and
20 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -78,6 +78,11 @@ Or install it yourself as: | |
For instructions on how to integrate Yuri-ita with your Rails application, | ||
[view the Getting Started documentation](docs/getting_started.md). | ||
|
||
## Releases | ||
|
||
Releases are signed by [email protected]. | ||
The fingerprint is `7B3B 5C4E C777 3530 7E65 EF2B D728 8DAC CCC8 0A03`. | ||
|
||
## Contributing | ||
|
||
See the [CONTRIBUTING] document. Thank you, [contributors]! | ||
|
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 |
---|---|---|
@@ -1,23 +1,28 @@ | ||
# Releasing | ||
|
||
1. Update version file accordingly. | ||
## Prepare | ||
1. Update the version number in `lib/yuriita/version.rb`. | ||
1. Update `NEWS.md` to reflect the changes since last release. | ||
1. Commit changes. | ||
There shouldn't be code changes, | ||
and thus CI doesn't need to run, | ||
you can then add "[ci skip]" to the commit message. | ||
1. Tag the release: `git tag -s vVERSION` | ||
- We recommend the [_quick guide on how to sign a release_] from git ready. | ||
1. Push changes: `git push --tags` | ||
1. Open and merge a PR with the changes. | ||
|
||
## Tag | ||
1. Tag and sign the release: `git tag -s vVERSION` | ||
[notes on signing] | ||
1. Verify the signed tag: `git tag -v vVERSION` | ||
1. Push changes: `git push --tags` | ||
|
||
## Publish | ||
1. Build and publish: | ||
```bash | ||
gem build yuri-ita.gemspec | ||
gem push yuri-ita-*.gem | ||
``` | ||
|
||
## Announce | ||
1. Add a new GitHub release using the recent `NEWS.md` as the content. Sample | ||
URL: https://github.com/thoughtbot/yuri-ita/releases/new?tag=vVERSION | ||
1. Announce the new release, | ||
making sure to say "thank you" to the contributors | ||
who helped shape this version! | ||
|
||
[_quick guide on how to sign a release_]: http://gitready.com/advanced/2014/11/02/gpg-sign-releases.html | ||
[notes on signing]: http://gitready.com/advanced/2014/11/02/gpg-sign-releases.html |
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