THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
All artifacts must be signed and checksummed. In order to sign a release you will need a PGP key. You should get your key signed by a few other people. You will also need to recv their keys from a public key server. See the Apache release signing page for more details.
1. Add your key to the KEYS file:
Code Block |
---|
(gpg --list-sigs <your-email> && gpg --armor --export <your-email>) >> KEYS |
...
Code Block |
---|
gpg --armor --output apache-flume-1X.2Y.0Z-bin.tar.gz.asc --detach-sig apache-flume-1X.2Y.0Z-bin.tar.gz gpg --armor --output apache-flume-1X.2Y.0Z.tar.gz.asc --detach-sig apache-flume-1X.2Y.0Z.tar.gz |
3. Checksum the artifacts:
Code Block |
---|
md5 -r apache-flume-1X.2Y.0Z-bin.tar.gz > apache-flume-1X.2Y.0Z-bin.tar.gz.md5 md5 -r apache-flume-1X.2Y.0Z.tar.gz > apache-flume-1X.2Y.0Z.tar.gz.md5 shasum apache-flume-1X.2Y.0Z-bin.tar.gz > apache-flume-1X.2Y.0Z-bin.tar.gz.sha1 shasum apache-flume-1X.2Y.0Z.tar.gz > apache-flume-1X.2Y.0Z.tar.gz.sha1 |
Note: the checksum files will not be mirrored; They should be downloaded from the main apache dist site.
...
No Format |
---|
To: dev@flume.apache.org Subject: [VOTE] Release Apache Flume version 1X.2Y.0Z rc0 This is the first release for Apache Flume as a top-level project, version 1.2.0. We are voting on release candidate rc0. *** Please cast your vote within the next 72 hours *** The list of fixed issues: <Link-to-CHANGELOG-in-the-tag> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5sum, *.sha1sum) for the source and binary artifacts can be found at: https://people.apache.org/~mpercy/flume/apache-flume-1X.2Y.0Z-rc0/ The tag to be voted on: https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=<commit-hash-of-the-tag> The KEYS file can be found here: https://svn.apache.org/repos/asf/flume/dist/KEYS |
...