I use following steps to release. 1) Prepare the release:
$ mvn release:prepare 2) Digitally sign the distribution hama-X.X.X.tar.gz: $ md5sum hama-x.x.x.tar.gz > hama-x.x.x.tar.gz.md5 $ sha1sum hama-x.x.x.tar.gz > hama-x.x.x.tar.gz.sha1 3) Uploading and Voting - http://people.apache.org/~edwardyoon/dist/0.6.2-RC1/ 4) Release artifacts $ mvn release:perform 5) Commit artifacts to https://dist.apache.org/repos/dist/release/hama/ On Thu, Sep 5, 2013 at 8:14 AM, Leonidas Fegaras <[email protected]> wrote: > Thanks Edward, > I will need your help for this. It's a lot of info to digest. > It would be faster if you just tell us how you did this for Hama. > I have created a KEY file at http://www.apache.org/dist/incubator/mrql/KEYS > that contains my public key. I have already distributed my public key. > Please enter yours in this KEY too. > How do you tell maven to use this KEY for signing when you do 'mvn deploy'? > Do you need to add something in the POM or in the ~/.m2/settings.xml? > Any help will really be appreciated. > Thanks > Leonidas > > > > On 09/04/2013 04:55 PM, Edward J. Yoon wrote: >> >> See also http://www.apache.org/dev/release-publishing >> >> We have to create our KEYS file - >> http://www.apache.org/dev/release-signing.html#keys-policy - and >> upload it somewhere. Maybe http://www.apache.org/dist/incubator/mrql/ >> >> All release candidate artifacts should be signed by author using PGP, >> SHA1, and MD5 signatures. >> >> Here's incubator project release vote example - >> http://markmail.org/message/cxyydek2vq3ioroh >> >> On Thu, Sep 5, 2013 at 4:57 AM, Karthik Kambatla <[email protected]> >> wrote: >>> >>> On Wed, Sep 4, 2013 at 12:37 PM, Leonidas Fegaras >>> <[email protected]>wrote: >>> >>>> We now have group accounts at the Nexus repository to release MRQL >>>> artifacts >>>> (see >>>> https://issues.apache.org/**jira/browse/INFRA-6703<https://issues.apache.org/jira/browse/INFRA-6703>) >>>> >>>> I have already stored the first MRQL snapshot. The current source >>>> tarball >>>> is at: >>>> https://repository.apache.org/**content/repositories/** >>>> >>>> snapshots/org/apache/mrql/**mrql-src-dist/<https://repository.apache.org/content/repositories/snapshots/org/apache/mrql/mrql-src-dist/> >>>> >>>> The binary tarball is at: >>>> https://repository.apache.org/**content/repositories/** >>>> >>>> snapshots/org/apache/mrql/**mrql-bin-dist/<https://repository.apache.org/content/repositories/snapshots/org/apache/mrql/mrql-bin-dist/> >>>> >>>> I think we are now ready to initiate the process for releasing our first >>>> release (MRQL 0.9.0). >>>> I would need somebody to do some sanity checks first. >>>> >>>> 1) I am using the maven rat plugin to find any missing licenses. But I >>>> skipped test queries and data. I cannot put license info on data. Do you >>>> think I should put license info on every query in tests/queries? >>>> >>> AFAIK, all the tests/queries also should have the license info. >>> >>>> 2) Please check the NOTICE file for completeness/correctness. >>>> >>>> 3) Spark has become an ASF incubating project very recently. So I assume >>>> that I don't have to include any license for Spark. Is this OK? >>>> >>>> 4) I have included javadocs in the src tarball only. Do you think I >>>> should >>>> include them in the bin tarball too? >>>> >>> Users typically use binary tarballs. I think it is a good idea to include >>> javadocs in the binary as well. >>> >>> >>>> After this, >>>> >>>> 1) I will stage the tarballs on Nexus for voting >>>> >>>> 2) I will start two threads in [email protected]: one for PPMC vote and one >>>> for discussion >>>> >>>> 3) if the PPMC accepts this release, I will send email to >>>> [email protected] ask for discussion, feedback, and vote for approval. >>>> >>>> Is there anything that I have missed? >>>> Thanks for your help. >>>> Leonidas >>>> >>>> >> >> > -- Best Regards, Edward J. Yoon @eddieyoon
