On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
Back on track, will sign the pom, and will ask this list to verify it
before copying over. (BTW, is there a way to get m2 to sign?)
snap/
Done, I've added my signature to the
On 12/27/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
The md5 and sha1 checksums are fine. When I try to verify the signature,
though:
gpg --verify shale-master-2.pom.asc shale-master-2.pom
I get the Can't check signature: public
On 12/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
Done, I've added my signature to the master pom v2 in the staging
repo. My key is here [1] amongst other places (I intend to add a
generic UID before 1.0.4).
Please
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
Yep ... that worked. I got the good signature and untrusted messages.
snap/
OK, so we're good to go on the master pom. Thanks.
I should have mentioned also what Wendy said ... we should follow the best
practice of maintaining
Shale Master POM version 2 release vote passes with 4 binding +1s from:
Craig McClanahan
Greg Reddin
Wendy Smoak
Gary VanMatre
No other binding votes.
Following a 24 hour buffer for reporting any counting errors, artifact
will be in the m2 rsync repo.
Thanks to those who took time to review
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Following a 24 hour buffer for reporting any counting errors, artifact
will be in the m2 rsync repo.
Thanks to those who took time to review and participate.
While I'm thinking of it... I checked the pom, but not the signature
and
On 12/26/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Following a 24 hour buffer for reporting any counting errors, artifact
will be in the m2 rsync repo.
Thanks to those who took time to review and participate.
While I'm thinking of it... I
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
OK, I'll wait till pao is good again (and this is sorted out). I don't
remember signing the pom with my key (will do it once I get a chance).
I used 'mvn deploy' so m2 summed it for me.
Let me know if the missing sig is reason for a new vote.
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
Back on track, will sign the pom, and will ask this list to verify it
before copying over. (BTW, is there a way to get m2 to sign?)
snap/
Done, I've added my signature to the master pom v2 in the staging
repo. My key is here [1]
