Thanks Bob! I'll start the vote for ClickIDE 2.1.0.0 soon.
2010/2/12 Bob Schellink <[email protected]>: > Great work Naoki. I verified the release signature from the public mit > server, so everything looks good. > > I think we can start the vote. > > kind regards > > bob > > > On 12/02/2010 11:33 PM, Naoki Takezoe wrote: >> >> Hi Bob, >> >> I revoked old key and re-signed with new RSA 4096 bit key. >> And I also added my new key to<svn trunk>/click/KEYS. >> >> Could you check<svn trunk>/click/KEYS and release files? >> http://people.apache.org/~takezoe/click/clickide/2.1.0.0/ >> >> 2010/2/12 Bob Schellink<[email protected]>: >>> >>> Hi Naoki, >>> >>> Before voting you'll need at least a RSA 4096 bit KEY and upload it to a >>> public key server such as pgp.mit.edu. >>> >>> See the first paragraph here: >>> >>> http://www.apache.org/dev/release-signing.html >>> >>> So I suggest you create a new RSA 4096 bit key and use that for signing >>> releases. That key also needs to be uploaded to a public key server such >>> as >>> 'pgp.mit.edu'. >>> >>> Here are the steps outlining how to create and sign the release: >>> >>> 1. Grab the latest version of GPG here: http://www.gnupg.org/ (you'll >>> need >>> at least version 2.0.12) >>> >>> 2. Change your config to avoid SHA-1: >>> http://www.apache.org/dev/openpgp.html#key-prefs >>> >>> 3. Generate a RSA 4096 key, and a revocation certificate -> >>> http://www.apache.org/dev/openpgp.html#key-gen-generate-key >>> >>> 4. Upload the key to a public server: gpg --keyserver pgp.mit.edu >>> --send-keys<YOUR-KEY> >>> >>> 5. Create and add an ascii armored key to the KEYS file in Click SVN[1]: >>> >>> generate an ascii armored key and add to the KEYS file: >>> http://www.apache.org/dev/openpgp.html#export-option-output >>> >>> Currently the Click KEYS file only contain one key. See the Velocity KEYS >>> file for an example of having multiple keys in the KEYS file: >>> >>> http://www.apache.org/dist/velocity/KEYS >>> >>> >>> Setting up the keys is a bit of pain the first time, so let me know if >>> you >>> need help with these steps. >>> >>> kind regards >>> >>> bob >>> >>> [1]: >>> >>> http://svn.apache.org/viewvc/click/trunk/click/KEYS?revision=907362&view=markup >>> >>> >>> On 12/02/2010 03:35 PM, Naoki Takezoe wrote: >>>> >>>> Hi Bob, >>>> >>>> I completed preparing the release of the ClickIDE 2.1.0.0. >>>> Release files are below: >>>> http://people.apache.org/~takezoe/click/clickide/2.1.0.0/ >>>> >>>> Can we start the vote to release ClickIDE 2.1.0.0? >>>> >>>> 2010/2/11 Bob Schellink<[email protected]>: >>>>> >>>>> Sorry Naoki, it is indeed 2.1.0.0. >>>>> >>>>> Let me know when the release is feature complete and I'll build and >>>>> publish >>>>> the zip and start the vote. >>>>> >>>>> kind regards >>>>> >>>>> bob >>>>> >>>>> >>>>> On 12/02/2010 12:24 AM, Naoki Takezoe wrote: >>>>>> >>>>>> Hi Bob, >>>>>> >>>>>> Thanks for your help. >>>>>> >>>>>> I'm readying ClickIDE 2.1.0.0 which supports Apache Click 2.1.0. >>>>>> Should I release it as ClickIDE 2.0.0.0 ? >>>>>> >>>>>> 2010/2/11 Bob Schellink<[email protected]>: >>>>>>> >>>>>>> Hi Naoki, >>>>>>> >>>>>>> Since we haven't had a release of ClickIDE since joining the ASF, >>>>>>> I'll >>>>>>> volunteer to be the release manager for ClickIDE 2.0.0.0. The release >>>>>>> procedure is a bit complex and I'd like to capture all the necessary >>>>>>> steps >>>>>>> in this document: >>>>>>> >>>>>>> >>>>>>> >>>>>>> http://click.apache.org/docs/developer-guide/releasing-subprojects.html >>>>>>> >>>>>>> Let me know when you think we can push out this release. >>>>>>> >>>>>>> kind regards >>>>>>> >>>>>>> bob >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> >> > > -- Naoki Takezoe
