Hi Aaron, I can take this up. Please give me a signal when you feel that How-To-Release wiki page is up to date. I have already started going through this page. As I am doing Apache release first time so might need help from your side :)
On Fri, Mar 14, 2014 at 7:20 AM, Aaron McCurry <[EMAIL PROTECTED]> wrote:
Ok. I have reviewed and edited the http://wiki.apache.org/blur/HowToRelease instructions. There are a couple of sections that still need to be written down. However those are after a successful vote, so we have a few days.
Let us know if you need help or have questions. Thanks!
Aaron On Fri, Mar 14, 2014 at 7:01 PM, Aaron McCurry <[EMAIL PROTECTED]> wrote:
basically though it's 1) call the vote on dev list, min 72hours, if that passes 2) call the vote on incubator general, if that passes (wait another 72hrs, min 3 IPMC +1's, regular rules re release vote (the vote needs to pass)) then you're ready to roll.
However I think that I need to setup (or have setup) something in https://repository.apache.org/ so that we can stage and push our artifacts. Do you know what the process is here or can point me to a doc? I have done a quick look in JIRA for other requests and did not find any. I will continue to look for more information.
On Sun, Mar 16, 2014 at 2:50 AM, Gagan Juneja <[EMAIL PROTECTED]>wrote: I can try, Tim helped me get through this process when I went though it. Maybe he can jump in here.
Where are you in the process? Assuming that you are at the beginning you will need to download and install a PGP tool. I'm on OSX so I used https://gpgtools.org/. Make sure you follow these instructions:
Hey Gagan, The page Aaron linked to has tons of details but you need to publish your keys to a keyserver (e.g. mit) - something like '--send-key' if you're using gpg. Do you live near any other committers who can sign your key?
Hi Tim, I tried to connect with some committer near by. But got reply that this is possible only after personal meeting. He recommended to get it signed is some upcoming cloud stack. Is it required for release as I have uploaded public key to MIT server. I will sign jars with the private key I am having and anybody can use this with public key I have uploaded.
On Sun, Mar 16, 2014 at 9:41 PM, Gagan Juneja <[EMAIL PROTECTED]> wrote:
On Tue, Mar 18, 2014 at 10:35 AM, Gagan Juneja <[EMAIL PROTECTED]> wrote:
Hi Gagan, That's why I suggested you find a local committer:) Is anyone in range that you could meetup for a beer or coffee? Most folks (myself included) will want to see some in-person identification before signing a key. Technically, maybe there's no requirement to be linked into the WoT but it's surely the best thing for the project to have trusted releases. I'm not sure what to say, I hate to turn down an eager Release Manager - hopefully you can find some spare time to meetup with someone? :)
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext