-
Notifications
You must be signed in to change notification settings - Fork 123
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2cfa94d
commit c9414bf
Showing
1 changed file
with
2 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,9 +12,6 @@ Prerequisites | |
* The web-site for the new version has been published to https://logging.staged.apache.org/log4cxx (using [this procedure](staging.md) ) | ||
* An e-mail has been sent to [email protected] announcing the intention to release | ||
* Your e-mail client can send mail from your `@apache.org` address. (Refer: https://eventmesh.apache.org/community/how-to-use-email/) | ||
* You have generated a RSA key of length 2048 or more (Refer: https://infra.apache.org/release-signing.html) | ||
* You have practiced signing files for weeks or months (to ensure you remember your passphrase) | ||
* Your public key is available in [Apache Logging KEYS file](https://dist.apache.org/repos/dist/release/logging/KEYS) | ||
|
||
Steps | ||
----- | ||
|
@@ -42,12 +39,9 @@ Steps | |
- Click the `>` to the left of `Run action/upload-artifact` | ||
- The numbered steps will display | ||
- Click the link next to `Artifact download URL:` | ||
- The browser will download the file `Upload release files.zip` onto your system | ||
- The browser will download the file `release_files.zip` onto your system | ||
1. Unpack the release files using these commands (with `apache-dist-logging-dev/log4cxx/1.3.1` as the working directory) | ||
- `unzip "$HOME/Downloads/Upload release files.zip"` | ||
1. Sign release artifacts (with `apache-dist-logging-dev/log4cxx/1.3.1` as the working directory) | ||
- `gpg --armor --output apache-log4cxx-1.3.1.zip.asc --detach-sig apache-log4cxx-1.3.1.zip` | ||
- `gpg --armor --output apache-log4cxx-1.3.1.tar.gz.asc --detach-sig apache-log4cxx-1.3.1.tar.gz` | ||
- `unzip "$HOME/Downloads/release_files.zip"` | ||
1. Send the new artifacts to svn (with `apache-dist-logging-dev/log4cxx/1.3.1` as the working directory) | ||
- `svn add *` | ||
- `svn commit -m 'log4cxx 1.3.1'` | ||
|
@@ -64,9 +58,6 @@ Steps | |
- `git checkout v1.3.1-RC1` | ||
- `git tag rel/v1.3.1` | ||
- `git push origin tag rel/v1.3.1` | ||
1. Set your details in `src/site/CMakeLists.txt` | ||
- Set your name in the LOG4CXX_RELEASE_MANAGER variable | ||
- Set your GnuPG key in the LOG4CXX_RELEASE_MANAGER_KEY variable | ||
1. Enter the release date in `src/site/markdown/change-report-gh.md` | ||
- Commit the change | ||
- Update the staged web site using [the update procedure](staging.md) | ||
|