You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by Chris Mattmann <ma...@apache.org> on 2017/12/20 02:50:55 UTC
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Ping (
Can I get 2 more VOTEs here so I can push this release out? It’s kind of needed for DRAT.
We can release a 1.2.2 with Tom’s patch later, but would really love to release this. Thanks.
Cheers,
Chris
On 11/12/17, 9:53 AM, "Chris Mattmann" <ma...@apache.org> wrote:
Hi Folks,
I have posted a 1st release candidate for the Apache OODT 1.2.1 release. The
source code is at:
https://dist.apache.org/repos/dist/dev/oodt/
For more detailed information, see the included CHANGES.txt file for details on
release contents and latest changes. The release was made using the OODT
release process, documented on the Wiki here:
https://cwiki.apache.org/confluence/display/OODT/Release+Process
The release was made from the OODT 1.2 tag at:
https://github.com/apache/oodt/tree/1.2.1/
A staged Maven repository is available at:
https://repository.apache.org/content/repositories/orgapacheoodt-1015/
Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
open for at least the next 72 hours.
Only votes from OODT PMC are binding, but folks are welcome to check the
release candidate and voice their approval or disapproval. The vote passes
if at least three binding +1 votes are cast.
[ ] +1 Release the packages as Apache OODT 1.2.1
[ ] -1 Do not release the packages because...
Thanks!
Chris
P.S. Here is my +1.
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by BW <bw...@mysoftcloud.com>.
https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/
On Wed, Dec 20, 2017 at 9:15 AM Chris Mattmann <ma...@apache.org> wrote:
> Thanks Sean, appreciate it. Do you know the magic command to do that
> revocation? (
>
>
>
> On 12/20/17, 9:14 AM, "Sean Kelly" <ke...@apache.org> wrote:
>
> Chris:
>
> This time I get:
>
> gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
>
> So I am now +1 to release!
>
> Thanks Chris!
> --k
>
> PS: You might want to revoke your two older keys and make FD01FEDB the
> go-to.
>
>
> Chris Mattmann wrote:
> > Can you try now – I updated with the KEYS file from Master that has
> my new KEY. For whatever
> > reason it didn’t make it into the tag, which I think is fine, since
> master always has the latest
> > and greatest.
> >
> >
> >
> > On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
> >
> > Thanks Chris!
> >
> > I imported the KEYS but I still get
> >
> > gpg: Can't check signature: No public key
> >
> > Is it possible you signed this with a newly generated key
> that's not in
> > the KEYS file?
> >
> > --k
> >
> > Chris Mattmann wrote:
> > > KEYS file added! ( do I have your +1? (
> > >
> > >
> > >
> > > On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org>
> wrote:
> > >
> > > Strangely this (and the release announcement) ended up
> in my spam folder.
> > >
> > > Here goes:
> > >
> > > MD5: ✓
> > > SHA1: ✓
> > > Python tests: ✓
> > > Java tests: ✓
> > > Signature: gpg: Can't check signature: No public key
> > >
> > > Don't we also put a convenience copy of the KEYS file
> in the release dir?
> > >
> > > Take care
> > > --k
> > > > Chris Mattmann<ma...@apache.org>
> > > > 2017-12-19 at 8.50 p
> > > > Ping (
> > > >
> > > > Can I get 2 more VOTEs here so I can push this
> release out? It’s kind
> > > > of needed for DRAT.
> > > > We can release a 1.2.2 with Tom’s patch later, but
> would really love
> > > > to release this. Thanks.
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > > >
> > > >
> > > >
> > > > On 11/12/17, 9:53 AM, "Chris Mattmann"<
> mattmann@apache.org> wrote:
> > > >
> > > > Hi Folks,
> > > >
> > > >
> > > >
> > > > I have posted a 1st release candidate for the
> Apache OODT 1.2.1
> > > > release. The
> > > >
> > > > source code is at:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/oodt/
> > > >
> > > >
> > > >
> > > > For more detailed information, see the included
> CHANGES.txt file for
> > > > details on
> > > >
> > > > release contents and latest changes. The release
> was made using the OODT
> > > >
> > > > release process, documented on the Wiki here:
> > > >
> > > >
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
> > > >
> > > >
> > > >
> > > > The release was made from the OODT 1.2 tag at:
> > > >
> > > > https://github.com/apache/oodt/tree/1.2.1/
> > > >
> > > >
> > > >
> > > > A staged Maven repository is available at:
> > > >
> > > >
> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> > > >
> > > >
> > > >
> > > > Please vote on releasing these packages as Apache
> OODT 1.2.1. The vote is
> > > >
> > > > open for at least the next 72 hours.
> > > >
> > > >
> > > >
> > > > Only votes from OODT PMC are binding, but folks are
> welcome to check the
> > > >
> > > > release candidate and voice their approval or
> disapproval. The vote passes
> > > >
> > > > if at least three binding +1 votes are cast.
> > > >
> > > >
> > > >
> > > > [ ] +1 Release the packages as Apache OODT 1.2.1
> > > >
> > > >
> > > >
> > > > [ ] -1 Do not release the packages because...
> > > >
> > > >
> > > >
> > > > Thanks!
> > > >
> > > >
> > > >
> > > > Chris
> > > >
> > > >
> > > >
> > > > P.S. Here is my +1.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Chris Mattmann <ma...@apache.org>.
Thanks Sean, appreciate it. Do you know the magic command to do that
revocation? (
On 12/20/17, 9:14 AM, "Sean Kelly" <ke...@apache.org> wrote:
Chris:
This time I get:
gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
So I am now +1 to release!
Thanks Chris!
--k
PS: You might want to revoke your two older keys and make FD01FEDB the
go-to.
Chris Mattmann wrote:
> Can you try now – I updated with the KEYS file from Master that has my new KEY. For whatever
> reason it didn’t make it into the tag, which I think is fine, since master always has the latest
> and greatest.
>
>
>
> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
>
> Thanks Chris!
>
> I imported the KEYS but I still get
>
> gpg: Can't check signature: No public key
>
> Is it possible you signed this with a newly generated key that's not in
> the KEYS file?
>
> --k
>
> Chris Mattmann wrote:
> > KEYS file added! ( do I have your +1? (
> >
> >
> >
> > On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
> >
> > Strangely this (and the release announcement) ended up in my spam folder.
> >
> > Here goes:
> >
> > MD5: ✓
> > SHA1: ✓
> > Python tests: ✓
> > Java tests: ✓
> > Signature: gpg: Can't check signature: No public key
> >
> > Don't we also put a convenience copy of the KEYS file in the release dir?
> >
> > Take care
> > --k
> > > Chris Mattmann<ma...@apache.org>
> > > 2017-12-19 at 8.50 p
> > > Ping (
> > >
> > > Can I get 2 more VOTEs here so I can push this release out? It’s kind
> > > of needed for DRAT.
> > > We can release a 1.2.2 with Tom’s patch later, but would really love
> > > to release this. Thanks.
> > >
> > > Cheers,
> > > Chris
> > >
> > >
> > >
> > >
> > > On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org> wrote:
> > >
> > > Hi Folks,
> > >
> > >
> > >
> > > I have posted a 1st release candidate for the Apache OODT 1.2.1
> > > release. The
> > >
> > > source code is at:
> > >
> > > https://dist.apache.org/repos/dist/dev/oodt/
> > >
> > >
> > >
> > > For more detailed information, see the included CHANGES.txt file for
> > > details on
> > >
> > > release contents and latest changes. The release was made using the OODT
> > >
> > > release process, documented on the Wiki here:
> > >
> > > https://cwiki.apache.org/confluence/display/OODT/Release+Process
> > >
> > >
> > >
> > > The release was made from the OODT 1.2 tag at:
> > >
> > > https://github.com/apache/oodt/tree/1.2.1/
> > >
> > >
> > >
> > > A staged Maven repository is available at:
> > >
> > > https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> > >
> > >
> > >
> > > Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
> > >
> > > open for at least the next 72 hours.
> > >
> > >
> > >
> > > Only votes from OODT PMC are binding, but folks are welcome to check the
> > >
> > > release candidate and voice their approval or disapproval. The vote passes
> > >
> > > if at least three binding +1 votes are cast.
> > >
> > >
> > >
> > > [ ] +1 Release the packages as Apache OODT 1.2.1
> > >
> > >
> > >
> > > [ ] -1 Do not release the packages because...
> > >
> > >
> > >
> > > Thanks!
> > >
> > >
> > >
> > > Chris
> > >
> > >
> > >
> > > P.S. Here is my +1.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Tom Barber <to...@meteorite.bi>.
Fair enough, I figured it had just stalled into the ether :)
+1 ship it and we'll roll another off the back of it.
On 02/02/18 03:32, Mattmann, Chris A (1761) wrote:
> The vote kinda already passed let’s just roll a new 1.2.2 give me 24hr to finish please
>
> Sent from my iPhone
>
>> On Feb 1, 2018, at 7:14 PM, Tom Barber <to...@meteorite.bi> wrote:
>>
>> Okay, I'm digging this one back up.
>>
>> I'm changing my vote to -1 because of OODT-968 which causes data loss.
>>
>> I fixed it a few weeks ago, so what I propose is that we can this vote, and I'll roll a 1.2.1 RC2 tomorrow or Saturday and reopen the vote with that included.
>>
>> Tom
>>
>>> On 21/12/17 18:12, lewis john mcgibbney wrote:
>>> +1 current state of RC is good.
>>> Usual checks carried out.
>>> Thanks for pushing Chris
>>>
>>>> On Thu, Dec 21, 2017 at 01:04 BW <we...@apache.org> wrote:
>>>>
>>>> Trying to make up for my missed vote. ;)
>>>>
>>>>> On Wed, Dec 20, 2017 at 9:38 AM Sean Kelly <ke...@apache.org> wrote:
>>>>>
>>>>> BW is too fast for me! ^_^
>>>>>
>>>>> Take care
>>>>> --k
>>>>>
>>>>> Sean Kelly wrote:
>>>>>> Chris:
>>>>>>
>>>>>> This time I get:
>>>>>>
>>>>>> gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
>>>>>>
>>>>>> So I am now +1 to release!
>>>>>>
>>>>>> Thanks Chris!
>>>>>> --k
>>>>>>
>>>>>> PS: You might want to revoke your two older keys and make FD01FEDB the
>>>>>> go-to.
>>>>>>
>>>>>>
>>>>>> Chris Mattmann wrote:
>>>>>>> Can you try now – I updated with the KEYS file from Master that has my
>>>>>>> new KEY. For whatever
>>>>>>> reason it didn’t make it into the tag, which I think is fine, since
>>>>>>> master always has the latest
>>>>>>> and greatest.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
>>>>>>>
>>>>>>> Thanks Chris!
>>>>>>>
>>>>>>> I imported the KEYS but I still get
>>>>>>>
>>>>>>> gpg: Can't check signature: No public key
>>>>>>>
>>>>>>> Is it possible you signed this with a newly generated key that's not
>>>> in
>>>>>>> the KEYS file?
>>>>>>>
>>>>>>> --k
>>>>>>>
>>>>>>> Chris Mattmann wrote:
>>>>>>>> KEYS file added! ( do I have your +1? (
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
>>>>>>>>
>>>>>>>> Strangely this (and the release announcement) ended up in my spam
>>>>>>> folder.
>>>>>>>> Here goes:
>>>>>>>>
>>>>>>>> MD5: ✓
>>>>>>>> SHA1: ✓
>>>>>>>> Python tests: ✓
>>>>>>>> Java tests: ✓
>>>>>>>> Signature: gpg: Can't check signature: No public key
>>>>>>>>
>>>>>>>> Don't we also put a convenience copy of the KEYS file in the release
>>>>>>> dir?
>>>>>>>> Take care
>>>>>>>> --k
>>>>>>>>> Chris Mattmann<ma...@apache.org>
>>>>>>>>> 2017-12-19 at 8.50 p
>>>>>>>>> Ping (
>>>>>>>>>
>>>>>>>>> Can I get 2 more VOTEs here so I can push this release out? It’s
>>>>> kind
>>>>>>>>> of needed for DRAT.
>>>>>>>>> We can release a 1.2.2 with Tom’s patch later, but would really
>>>> love
>>>>>>>>> to release this. Thanks.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Chris
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org>
>>>> wrote:
>>>>>>>>> Hi Folks,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I have posted a 1st release candidate for the Apache OODT 1.2.1
>>>>>>>>> release. The
>>>>>>>>>
>>>>>>>>> source code is at:
>>>>>>>>>
>>>>>>>>> https://dist.apache.org/repos/dist/dev/oodt/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> For more detailed information, see the included CHANGES.txt file
>>>> for
>>>>>>>>> details on
>>>>>>>>>
>>>>>>>>> release contents and latest changes. The release was made using
>>>>>>> the OODT
>>>>>>>>> release process, documented on the Wiki here:
>>>>>>>>>
>>>>>>>>> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The release was made from the OODT 1.2 tag at:
>>>>>>>>>
>>>>>>>>> https://github.com/apache/oodt/tree/1.2.1/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> A staged Maven repository is available at:
>>>>>>>>>
>>>>>>>>>
>>>> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
>>>>>>>>>
>>>>>>>>> Please vote on releasing these packages as Apache OODT 1.2.1. The
>>>>>>> vote is
>>>>>>>>> open for at least the next 72 hours.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Only votes from OODT PMC are binding, but folks are welcome to
>>>>>>> check the
>>>>>>>>> release candidate and voice their approval or disapproval. The
>>>>>>> vote passes
>>>>>>>>> if at least three binding +1 votes are cast.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [ ] +1 Release the packages as Apache OODT 1.2.1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [ ] -1 Do not release the packages because...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Chris
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> P.S. Here is my +1.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by "Mattmann, Chris A (1761)" <ch...@jpl.nasa.gov>.
The vote kinda already passed let’s just roll a new 1.2.2 give me 24hr to finish please
Sent from my iPhone
> On Feb 1, 2018, at 7:14 PM, Tom Barber <to...@meteorite.bi> wrote:
>
> Okay, I'm digging this one back up.
>
> I'm changing my vote to -1 because of OODT-968 which causes data loss.
>
> I fixed it a few weeks ago, so what I propose is that we can this vote, and I'll roll a 1.2.1 RC2 tomorrow or Saturday and reopen the vote with that included.
>
> Tom
>
>> On 21/12/17 18:12, lewis john mcgibbney wrote:
>> +1 current state of RC is good.
>> Usual checks carried out.
>> Thanks for pushing Chris
>>
>>> On Thu, Dec 21, 2017 at 01:04 BW <we...@apache.org> wrote:
>>>
>>> Trying to make up for my missed vote. ;)
>>>
>>>> On Wed, Dec 20, 2017 at 9:38 AM Sean Kelly <ke...@apache.org> wrote:
>>>>
>>>> BW is too fast for me! ^_^
>>>>
>>>> Take care
>>>> --k
>>>>
>>>> Sean Kelly wrote:
>>>>> Chris:
>>>>>
>>>>> This time I get:
>>>>>
>>>>> gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
>>>>>
>>>>> So I am now +1 to release!
>>>>>
>>>>> Thanks Chris!
>>>>> --k
>>>>>
>>>>> PS: You might want to revoke your two older keys and make FD01FEDB the
>>>>> go-to.
>>>>>
>>>>>
>>>>> Chris Mattmann wrote:
>>>>>> Can you try now – I updated with the KEYS file from Master that has my
>>>>>> new KEY. For whatever
>>>>>> reason it didn’t make it into the tag, which I think is fine, since
>>>>>> master always has the latest
>>>>>> and greatest.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
>>>>>>
>>>>>> Thanks Chris!
>>>>>>
>>>>>> I imported the KEYS but I still get
>>>>>>
>>>>>> gpg: Can't check signature: No public key
>>>>>>
>>>>>> Is it possible you signed this with a newly generated key that's not
>>> in
>>>>>> the KEYS file?
>>>>>>
>>>>>> --k
>>>>>>
>>>>>> Chris Mattmann wrote:
>>>>>>> KEYS file added! ( do I have your +1? (
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
>>>>>>>
>>>>>>> Strangely this (and the release announcement) ended up in my spam
>>>>>> folder.
>>>>>>> Here goes:
>>>>>>>
>>>>>>> MD5: ✓
>>>>>>> SHA1: ✓
>>>>>>> Python tests: ✓
>>>>>>> Java tests: ✓
>>>>>>> Signature: gpg: Can't check signature: No public key
>>>>>>>
>>>>>>> Don't we also put a convenience copy of the KEYS file in the release
>>>>>> dir?
>>>>>>> Take care
>>>>>>> --k
>>>>>>>> Chris Mattmann<ma...@apache.org>
>>>>>>>> 2017-12-19 at 8.50 p
>>>>>>>> Ping (
>>>>>>>>
>>>>>>>> Can I get 2 more VOTEs here so I can push this release out? It’s
>>>> kind
>>>>>>>> of needed for DRAT.
>>>>>>>> We can release a 1.2.2 with Tom’s patch later, but would really
>>> love
>>>>>>>> to release this. Thanks.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Chris
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org>
>>> wrote:
>>>>>>>> Hi Folks,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I have posted a 1st release candidate for the Apache OODT 1.2.1
>>>>>>>> release. The
>>>>>>>>
>>>>>>>> source code is at:
>>>>>>>>
>>>>>>>> https://dist.apache.org/repos/dist/dev/oodt/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> For more detailed information, see the included CHANGES.txt file
>>> for
>>>>>>>> details on
>>>>>>>>
>>>>>>>> release contents and latest changes. The release was made using
>>>>>> the OODT
>>>>>>>> release process, documented on the Wiki here:
>>>>>>>>
>>>>>>>> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The release was made from the OODT 1.2 tag at:
>>>>>>>>
>>>>>>>> https://github.com/apache/oodt/tree/1.2.1/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> A staged Maven repository is available at:
>>>>>>>>
>>>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
>>>>>>>>
>>>>>>>>
>>>>>>>> Please vote on releasing these packages as Apache OODT 1.2.1. The
>>>>>> vote is
>>>>>>>> open for at least the next 72 hours.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Only votes from OODT PMC are binding, but folks are welcome to
>>>>>> check the
>>>>>>>> release candidate and voice their approval or disapproval. The
>>>>>> vote passes
>>>>>>>> if at least three binding +1 votes are cast.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [ ] +1 Release the packages as Apache OODT 1.2.1
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [ ] -1 Do not release the packages because...
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Chris
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> P.S. Here is my +1.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Tom Barber <to...@meteorite.bi>.
Okay, I'm digging this one back up.
I'm changing my vote to -1 because of OODT-968 which causes data loss.
I fixed it a few weeks ago, so what I propose is that we can this vote,
and I'll roll a 1.2.1 RC2 tomorrow or Saturday and reopen the vote with
that included.
Tom
On 21/12/17 18:12, lewis john mcgibbney wrote:
> +1 current state of RC is good.
> Usual checks carried out.
> Thanks for pushing Chris
>
> On Thu, Dec 21, 2017 at 01:04 BW <we...@apache.org> wrote:
>
>> Trying to make up for my missed vote. ;)
>>
>> On Wed, Dec 20, 2017 at 9:38 AM Sean Kelly <ke...@apache.org> wrote:
>>
>>> BW is too fast for me! ^_^
>>>
>>> Take care
>>> --k
>>>
>>> Sean Kelly wrote:
>>>> Chris:
>>>>
>>>> This time I get:
>>>>
>>>> gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
>>>>
>>>> So I am now +1 to release!
>>>>
>>>> Thanks Chris!
>>>> --k
>>>>
>>>> PS: You might want to revoke your two older keys and make FD01FEDB the
>>>> go-to.
>>>>
>>>>
>>>> Chris Mattmann wrote:
>>>>> Can you try now – I updated with the KEYS file from Master that has my
>>>>> new KEY. For whatever
>>>>> reason it didn’t make it into the tag, which I think is fine, since
>>>>> master always has the latest
>>>>> and greatest.
>>>>>
>>>>>
>>>>>
>>>>> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
>>>>>
>>>>> Thanks Chris!
>>>>>
>>>>> I imported the KEYS but I still get
>>>>>
>>>>> gpg: Can't check signature: No public key
>>>>>
>>>>> Is it possible you signed this with a newly generated key that's not
>> in
>>>>> the KEYS file?
>>>>>
>>>>> --k
>>>>>
>>>>> Chris Mattmann wrote:
>>>>>> KEYS file added! ( do I have your +1? (
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
>>>>>>
>>>>>> Strangely this (and the release announcement) ended up in my spam
>>>>> folder.
>>>>>> Here goes:
>>>>>>
>>>>>> MD5: ✓
>>>>>> SHA1: ✓
>>>>>> Python tests: ✓
>>>>>> Java tests: ✓
>>>>>> Signature: gpg: Can't check signature: No public key
>>>>>>
>>>>>> Don't we also put a convenience copy of the KEYS file in the release
>>>>> dir?
>>>>>> Take care
>>>>>> --k
>>>>>>> Chris Mattmann<ma...@apache.org>
>>>>>>> 2017-12-19 at 8.50 p
>>>>>>> Ping (
>>>>>>>
>>>>>>> Can I get 2 more VOTEs here so I can push this release out? It’s
>>> kind
>>>>>>> of needed for DRAT.
>>>>>>> We can release a 1.2.2 with Tom’s patch later, but would really
>> love
>>>>>>> to release this. Thanks.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chris
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org>
>> wrote:
>>>>>>> Hi Folks,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I have posted a 1st release candidate for the Apache OODT 1.2.1
>>>>>>> release. The
>>>>>>>
>>>>>>> source code is at:
>>>>>>>
>>>>>>> https://dist.apache.org/repos/dist/dev/oodt/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> For more detailed information, see the included CHANGES.txt file
>> for
>>>>>>> details on
>>>>>>>
>>>>>>> release contents and latest changes. The release was made using
>>>>> the OODT
>>>>>>> release process, documented on the Wiki here:
>>>>>>>
>>>>>>> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The release was made from the OODT 1.2 tag at:
>>>>>>>
>>>>>>> https://github.com/apache/oodt/tree/1.2.1/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> A staged Maven repository is available at:
>>>>>>>
>>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
>>>>>>>
>>>>>>>
>>>>>>> Please vote on releasing these packages as Apache OODT 1.2.1. The
>>>>> vote is
>>>>>>> open for at least the next 72 hours.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Only votes from OODT PMC are binding, but folks are welcome to
>>>>> check the
>>>>>>> release candidate and voice their approval or disapproval. The
>>>>> vote passes
>>>>>>> if at least three binding +1 votes are cast.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [ ] +1 Release the packages as Apache OODT 1.2.1
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [ ] -1 Do not release the packages because...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Chris
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> P.S. Here is my +1.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by lewis john mcgibbney <le...@apache.org>.
+1 current state of RC is good.
Usual checks carried out.
Thanks for pushing Chris
On Thu, Dec 21, 2017 at 01:04 BW <we...@apache.org> wrote:
> Trying to make up for my missed vote. ;)
>
> On Wed, Dec 20, 2017 at 9:38 AM Sean Kelly <ke...@apache.org> wrote:
>
> > BW is too fast for me! ^_^
> >
> > Take care
> > --k
> >
> > Sean Kelly wrote:
> > > Chris:
> > >
> > > This time I get:
> > >
> > > gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
> > >
> > > So I am now +1 to release!
> > >
> > > Thanks Chris!
> > > --k
> > >
> > > PS: You might want to revoke your two older keys and make FD01FEDB the
> > > go-to.
> > >
> > >
> > > Chris Mattmann wrote:
> > >> Can you try now – I updated with the KEYS file from Master that has my
> > >> new KEY. For whatever
> > >> reason it didn’t make it into the tag, which I think is fine, since
> > >> master always has the latest
> > >> and greatest.
> > >>
> > >>
> > >>
> > >> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
> > >>
> > >> Thanks Chris!
> > >>
> > >> I imported the KEYS but I still get
> > >>
> > >> gpg: Can't check signature: No public key
> > >>
> > >> Is it possible you signed this with a newly generated key that's not
> in
> > >> the KEYS file?
> > >>
> > >> --k
> > >>
> > >> Chris Mattmann wrote:
> > >> > KEYS file added! ( do I have your +1? (
> > >> >
> > >> >
> > >> >
> > >> > On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
> > >> >
> > >> > Strangely this (and the release announcement) ended up in my spam
> > >> folder.
> > >> >
> > >> > Here goes:
> > >> >
> > >> > MD5: ✓
> > >> > SHA1: ✓
> > >> > Python tests: ✓
> > >> > Java tests: ✓
> > >> > Signature: gpg: Can't check signature: No public key
> > >> >
> > >> > Don't we also put a convenience copy of the KEYS file in the release
> > >> dir?
> > >> >
> > >> > Take care
> > >> > --k
> > >> > > Chris Mattmann<ma...@apache.org>
> > >> > > 2017-12-19 at 8.50 p
> > >> > > Ping (
> > >> > >
> > >> > > Can I get 2 more VOTEs here so I can push this release out? It’s
> > kind
> > >> > > of needed for DRAT.
> > >> > > We can release a 1.2.2 with Tom’s patch later, but would really
> love
> > >> > > to release this. Thanks.
> > >> > >
> > >> > > Cheers,
> > >> > > Chris
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org>
> wrote:
> > >> > >
> > >> > > Hi Folks,
> > >> > >
> > >> > >
> > >> > >
> > >> > > I have posted a 1st release candidate for the Apache OODT 1.2.1
> > >> > > release. The
> > >> > >
> > >> > > source code is at:
> > >> > >
> > >> > > https://dist.apache.org/repos/dist/dev/oodt/
> > >> > >
> > >> > >
> > >> > >
> > >> > > For more detailed information, see the included CHANGES.txt file
> for
> > >> > > details on
> > >> > >
> > >> > > release contents and latest changes. The release was made using
> > >> the OODT
> > >> > >
> > >> > > release process, documented on the Wiki here:
> > >> > >
> > >> > > https://cwiki.apache.org/confluence/display/OODT/Release+Process
> > >> > >
> > >> > >
> > >> > >
> > >> > > The release was made from the OODT 1.2 tag at:
> > >> > >
> > >> > > https://github.com/apache/oodt/tree/1.2.1/
> > >> > >
> > >> > >
> > >> > >
> > >> > > A staged Maven repository is available at:
> > >> > >
> > >> > >
> > >>
> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> > >> > >
> > >> > >
> > >> > >
> > >> > > Please vote on releasing these packages as Apache OODT 1.2.1. The
> > >> vote is
> > >> > >
> > >> > > open for at least the next 72 hours.
> > >> > >
> > >> > >
> > >> > >
> > >> > > Only votes from OODT PMC are binding, but folks are welcome to
> > >> check the
> > >> > >
> > >> > > release candidate and voice their approval or disapproval. The
> > >> vote passes
> > >> > >
> > >> > > if at least three binding +1 votes are cast.
> > >> > >
> > >> > >
> > >> > >
> > >> > > [ ] +1 Release the packages as Apache OODT 1.2.1
> > >> > >
> > >> > >
> > >> > >
> > >> > > [ ] -1 Do not release the packages because...
> > >> > >
> > >> > >
> > >> > >
> > >> > > Thanks!
> > >> > >
> > >> > >
> > >> > >
> > >> > > Chris
> > >> > >
> > >> > >
> > >> > >
> > >> > > P.S. Here is my +1.
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >> >
> > >>
> > >>
> > >>
> >
>
--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by BW <we...@apache.org>.
Trying to make up for my missed vote. ;)
On Wed, Dec 20, 2017 at 9:38 AM Sean Kelly <ke...@apache.org> wrote:
> BW is too fast for me! ^_^
>
> Take care
> --k
>
> Sean Kelly wrote:
> > Chris:
> >
> > This time I get:
> >
> > gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
> >
> > So I am now +1 to release!
> >
> > Thanks Chris!
> > --k
> >
> > PS: You might want to revoke your two older keys and make FD01FEDB the
> > go-to.
> >
> >
> > Chris Mattmann wrote:
> >> Can you try now – I updated with the KEYS file from Master that has my
> >> new KEY. For whatever
> >> reason it didn’t make it into the tag, which I think is fine, since
> >> master always has the latest
> >> and greatest.
> >>
> >>
> >>
> >> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
> >>
> >> Thanks Chris!
> >>
> >> I imported the KEYS but I still get
> >>
> >> gpg: Can't check signature: No public key
> >>
> >> Is it possible you signed this with a newly generated key that's not in
> >> the KEYS file?
> >>
> >> --k
> >>
> >> Chris Mattmann wrote:
> >> > KEYS file added! ( do I have your +1? (
> >> >
> >> >
> >> >
> >> > On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
> >> >
> >> > Strangely this (and the release announcement) ended up in my spam
> >> folder.
> >> >
> >> > Here goes:
> >> >
> >> > MD5: ✓
> >> > SHA1: ✓
> >> > Python tests: ✓
> >> > Java tests: ✓
> >> > Signature: gpg: Can't check signature: No public key
> >> >
> >> > Don't we also put a convenience copy of the KEYS file in the release
> >> dir?
> >> >
> >> > Take care
> >> > --k
> >> > > Chris Mattmann<ma...@apache.org>
> >> > > 2017-12-19 at 8.50 p
> >> > > Ping (
> >> > >
> >> > > Can I get 2 more VOTEs here so I can push this release out? It’s
> kind
> >> > > of needed for DRAT.
> >> > > We can release a 1.2.2 with Tom’s patch later, but would really love
> >> > > to release this. Thanks.
> >> > >
> >> > > Cheers,
> >> > > Chris
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org> wrote:
> >> > >
> >> > > Hi Folks,
> >> > >
> >> > >
> >> > >
> >> > > I have posted a 1st release candidate for the Apache OODT 1.2.1
> >> > > release. The
> >> > >
> >> > > source code is at:
> >> > >
> >> > > https://dist.apache.org/repos/dist/dev/oodt/
> >> > >
> >> > >
> >> > >
> >> > > For more detailed information, see the included CHANGES.txt file for
> >> > > details on
> >> > >
> >> > > release contents and latest changes. The release was made using
> >> the OODT
> >> > >
> >> > > release process, documented on the Wiki here:
> >> > >
> >> > > https://cwiki.apache.org/confluence/display/OODT/Release+Process
> >> > >
> >> > >
> >> > >
> >> > > The release was made from the OODT 1.2 tag at:
> >> > >
> >> > > https://github.com/apache/oodt/tree/1.2.1/
> >> > >
> >> > >
> >> > >
> >> > > A staged Maven repository is available at:
> >> > >
> >> > >
> >> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> >> > >
> >> > >
> >> > >
> >> > > Please vote on releasing these packages as Apache OODT 1.2.1. The
> >> vote is
> >> > >
> >> > > open for at least the next 72 hours.
> >> > >
> >> > >
> >> > >
> >> > > Only votes from OODT PMC are binding, but folks are welcome to
> >> check the
> >> > >
> >> > > release candidate and voice their approval or disapproval. The
> >> vote passes
> >> > >
> >> > > if at least three binding +1 votes are cast.
> >> > >
> >> > >
> >> > >
> >> > > [ ] +1 Release the packages as Apache OODT 1.2.1
> >> > >
> >> > >
> >> > >
> >> > > [ ] -1 Do not release the packages because...
> >> > >
> >> > >
> >> > >
> >> > > Thanks!
> >> > >
> >> > >
> >> > >
> >> > > Chris
> >> > >
> >> > >
> >> > >
> >> > > P.S. Here is my +1.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >> >
> >> >
> >>
> >>
> >>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Sean Kelly <ke...@apache.org>.
BW is too fast for me! ^_^
Take care
--k
Sean Kelly wrote:
> Chris:
>
> This time I get:
>
> gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
>
> So I am now +1 to release!
>
> Thanks Chris!
> --k
>
> PS: You might want to revoke your two older keys and make FD01FEDB the
> go-to.
>
>
> Chris Mattmann wrote:
>> Can you try now – I updated with the KEYS file from Master that has my
>> new KEY. For whatever
>> reason it didn’t make it into the tag, which I think is fine, since
>> master always has the latest
>> and greatest.
>>
>>
>>
>> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
>>
>> Thanks Chris!
>>
>> I imported the KEYS but I still get
>>
>> gpg: Can't check signature: No public key
>>
>> Is it possible you signed this with a newly generated key that's not in
>> the KEYS file?
>>
>> --k
>>
>> Chris Mattmann wrote:
>> > KEYS file added! ( do I have your +1? (
>> >
>> >
>> >
>> > On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
>> >
>> > Strangely this (and the release announcement) ended up in my spam
>> folder.
>> >
>> > Here goes:
>> >
>> > MD5: ✓
>> > SHA1: ✓
>> > Python tests: ✓
>> > Java tests: ✓
>> > Signature: gpg: Can't check signature: No public key
>> >
>> > Don't we also put a convenience copy of the KEYS file in the release
>> dir?
>> >
>> > Take care
>> > --k
>> > > Chris Mattmann<ma...@apache.org>
>> > > 2017-12-19 at 8.50 p
>> > > Ping (
>> > >
>> > > Can I get 2 more VOTEs here so I can push this release out? It’s kind
>> > > of needed for DRAT.
>> > > We can release a 1.2.2 with Tom’s patch later, but would really love
>> > > to release this. Thanks.
>> > >
>> > > Cheers,
>> > > Chris
>> > >
>> > >
>> > >
>> > >
>> > > On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org> wrote:
>> > >
>> > > Hi Folks,
>> > >
>> > >
>> > >
>> > > I have posted a 1st release candidate for the Apache OODT 1.2.1
>> > > release. The
>> > >
>> > > source code is at:
>> > >
>> > > https://dist.apache.org/repos/dist/dev/oodt/
>> > >
>> > >
>> > >
>> > > For more detailed information, see the included CHANGES.txt file for
>> > > details on
>> > >
>> > > release contents and latest changes. The release was made using
>> the OODT
>> > >
>> > > release process, documented on the Wiki here:
>> > >
>> > > https://cwiki.apache.org/confluence/display/OODT/Release+Process
>> > >
>> > >
>> > >
>> > > The release was made from the OODT 1.2 tag at:
>> > >
>> > > https://github.com/apache/oodt/tree/1.2.1/
>> > >
>> > >
>> > >
>> > > A staged Maven repository is available at:
>> > >
>> > >
>> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
>> > >
>> > >
>> > >
>> > > Please vote on releasing these packages as Apache OODT 1.2.1. The
>> vote is
>> > >
>> > > open for at least the next 72 hours.
>> > >
>> > >
>> > >
>> > > Only votes from OODT PMC are binding, but folks are welcome to
>> check the
>> > >
>> > > release candidate and voice their approval or disapproval. The
>> vote passes
>> > >
>> > > if at least three binding +1 votes are cast.
>> > >
>> > >
>> > >
>> > > [ ] +1 Release the packages as Apache OODT 1.2.1
>> > >
>> > >
>> > >
>> > > [ ] -1 Do not release the packages because...
>> > >
>> > >
>> > >
>> > > Thanks!
>> > >
>> > >
>> > >
>> > > Chris
>> > >
>> > >
>> > >
>> > > P.S. Here is my +1.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>> >
>>
>>
>>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Sean Kelly <ke...@apache.org>.
Chris:
This time I get:
gpg: Good signature from "Chris Mattmann <ma...@apache.org>"
So I am now +1 to release!
Thanks Chris!
--k
PS: You might want to revoke your two older keys and make FD01FEDB the
go-to.
Chris Mattmann wrote:
> Can you try now – I updated with the KEYS file from Master that has my new KEY. For whatever
> reason it didn’t make it into the tag, which I think is fine, since master always has the latest
> and greatest.
>
>
>
> On 12/20/17, 8:58 AM, "Sean Kelly"<ke...@apache.org> wrote:
>
> Thanks Chris!
>
> I imported the KEYS but I still get
>
> gpg: Can't check signature: No public key
>
> Is it possible you signed this with a newly generated key that's not in
> the KEYS file?
>
> --k
>
> Chris Mattmann wrote:
> > KEYS file added! ( do I have your +1? (
> >
> >
> >
> > On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
> >
> > Strangely this (and the release announcement) ended up in my spam folder.
> >
> > Here goes:
> >
> > MD5: ✓
> > SHA1: ✓
> > Python tests: ✓
> > Java tests: ✓
> > Signature: gpg: Can't check signature: No public key
> >
> > Don't we also put a convenience copy of the KEYS file in the release dir?
> >
> > Take care
> > --k
> > > Chris Mattmann<ma...@apache.org>
> > > 2017-12-19 at 8.50 p
> > > Ping (
> > >
> > > Can I get 2 more VOTEs here so I can push this release out? It’s kind
> > > of needed for DRAT.
> > > We can release a 1.2.2 with Tom’s patch later, but would really love
> > > to release this. Thanks.
> > >
> > > Cheers,
> > > Chris
> > >
> > >
> > >
> > >
> > > On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org> wrote:
> > >
> > > Hi Folks,
> > >
> > >
> > >
> > > I have posted a 1st release candidate for the Apache OODT 1.2.1
> > > release. The
> > >
> > > source code is at:
> > >
> > > https://dist.apache.org/repos/dist/dev/oodt/
> > >
> > >
> > >
> > > For more detailed information, see the included CHANGES.txt file for
> > > details on
> > >
> > > release contents and latest changes. The release was made using the OODT
> > >
> > > release process, documented on the Wiki here:
> > >
> > > https://cwiki.apache.org/confluence/display/OODT/Release+Process
> > >
> > >
> > >
> > > The release was made from the OODT 1.2 tag at:
> > >
> > > https://github.com/apache/oodt/tree/1.2.1/
> > >
> > >
> > >
> > > A staged Maven repository is available at:
> > >
> > > https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> > >
> > >
> > >
> > > Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
> > >
> > > open for at least the next 72 hours.
> > >
> > >
> > >
> > > Only votes from OODT PMC are binding, but folks are welcome to check the
> > >
> > > release candidate and voice their approval or disapproval. The vote passes
> > >
> > > if at least three binding +1 votes are cast.
> > >
> > >
> > >
> > > [ ] +1 Release the packages as Apache OODT 1.2.1
> > >
> > >
> > >
> > > [ ] -1 Do not release the packages because...
> > >
> > >
> > >
> > > Thanks!
> > >
> > >
> > >
> > > Chris
> > >
> > >
> > >
> > > P.S. Here is my +1.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Chris Mattmann <ma...@apache.org>.
Can you try now – I updated with the KEYS file from Master that has my new KEY. For whatever
reason it didn’t make it into the tag, which I think is fine, since master always has the latest
and greatest.
On 12/20/17, 8:58 AM, "Sean Kelly" <ke...@apache.org> wrote:
Thanks Chris!
I imported the KEYS but I still get
gpg: Can't check signature: No public key
Is it possible you signed this with a newly generated key that's not in
the KEYS file?
--k
Chris Mattmann wrote:
> KEYS file added! ( do I have your +1? (
>
>
>
> On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
>
> Strangely this (and the release announcement) ended up in my spam folder.
>
> Here goes:
>
> MD5: ✓
> SHA1: ✓
> Python tests: ✓
> Java tests: ✓
> Signature: gpg: Can't check signature: No public key
>
> Don't we also put a convenience copy of the KEYS file in the release dir?
>
> Take care
> --k
> > Chris Mattmann<ma...@apache.org>
> > 2017-12-19 at 8.50 p
> > Ping (
> >
> > Can I get 2 more VOTEs here so I can push this release out? It’s kind
> > of needed for DRAT.
> > We can release a 1.2.2 with Tom’s patch later, but would really love
> > to release this. Thanks.
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org> wrote:
> >
> > Hi Folks,
> >
> >
> >
> > I have posted a 1st release candidate for the Apache OODT 1.2.1
> > release. The
> >
> > source code is at:
> >
> > https://dist.apache.org/repos/dist/dev/oodt/
> >
> >
> >
> > For more detailed information, see the included CHANGES.txt file for
> > details on
> >
> > release contents and latest changes. The release was made using the OODT
> >
> > release process, documented on the Wiki here:
> >
> > https://cwiki.apache.org/confluence/display/OODT/Release+Process
> >
> >
> >
> > The release was made from the OODT 1.2 tag at:
> >
> > https://github.com/apache/oodt/tree/1.2.1/
> >
> >
> >
> > A staged Maven repository is available at:
> >
> > https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> >
> >
> >
> > Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
> >
> > open for at least the next 72 hours.
> >
> >
> >
> > Only votes from OODT PMC are binding, but folks are welcome to check the
> >
> > release candidate and voice their approval or disapproval. The vote passes
> >
> > if at least three binding +1 votes are cast.
> >
> >
> >
> > [ ] +1 Release the packages as Apache OODT 1.2.1
> >
> >
> >
> > [ ] -1 Do not release the packages because...
> >
> >
> >
> > Thanks!
> >
> >
> >
> > Chris
> >
> >
> >
> > P.S. Here is my +1.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Sean Kelly <ke...@apache.org>.
Thanks Chris!
I imported the KEYS but I still get
gpg: Can't check signature: No public key
Is it possible you signed this with a newly generated key that's not in
the KEYS file?
--k
Chris Mattmann wrote:
> KEYS file added! ( do I have your +1? (
>
>
>
> On 12/20/17, 8:38 AM, "Sean Kelly"<ke...@apache.org> wrote:
>
> Strangely this (and the release announcement) ended up in my spam folder.
>
> Here goes:
>
> MD5: ✓
> SHA1: ✓
> Python tests: ✓
> Java tests: ✓
> Signature: gpg: Can't check signature: No public key
>
> Don't we also put a convenience copy of the KEYS file in the release dir?
>
> Take care
> --k
> > Chris Mattmann<ma...@apache.org>
> > 2017-12-19 at 8.50 p
> > Ping (
> >
> > Can I get 2 more VOTEs here so I can push this release out? It’s kind
> > of needed for DRAT.
> > We can release a 1.2.2 with Tom’s patch later, but would really love
> > to release this. Thanks.
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > On 11/12/17, 9:53 AM, "Chris Mattmann"<ma...@apache.org> wrote:
> >
> > Hi Folks,
> >
> >
> >
> > I have posted a 1st release candidate for the Apache OODT 1.2.1
> > release. The
> >
> > source code is at:
> >
> > https://dist.apache.org/repos/dist/dev/oodt/
> >
> >
> >
> > For more detailed information, see the included CHANGES.txt file for
> > details on
> >
> > release contents and latest changes. The release was made using the OODT
> >
> > release process, documented on the Wiki here:
> >
> > https://cwiki.apache.org/confluence/display/OODT/Release+Process
> >
> >
> >
> > The release was made from the OODT 1.2 tag at:
> >
> > https://github.com/apache/oodt/tree/1.2.1/
> >
> >
> >
> > A staged Maven repository is available at:
> >
> > https://repository.apache.org/content/repositories/orgapacheoodt-1015/
> >
> >
> >
> > Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
> >
> > open for at least the next 72 hours.
> >
> >
> >
> > Only votes from OODT PMC are binding, but folks are welcome to check the
> >
> > release candidate and voice their approval or disapproval. The vote passes
> >
> > if at least three binding +1 votes are cast.
> >
> >
> >
> > [ ] +1 Release the packages as Apache OODT 1.2.1
> >
> >
> >
> > [ ] -1 Do not release the packages because...
> >
> >
> >
> > Thanks!
> >
> >
> >
> > Chris
> >
> >
> >
> > P.S. Here is my +1.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Chris Mattmann <ma...@apache.org>.
KEYS file added! ( do I have your +1? (
On 12/20/17, 8:38 AM, "Sean Kelly" <ke...@apache.org> wrote:
Strangely this (and the release announcement) ended up in my spam folder.
Here goes:
MD5: ✓
SHA1: ✓
Python tests: ✓
Java tests: ✓
Signature: gpg: Can't check signature: No public key
Don't we also put a convenience copy of the KEYS file in the release dir?
Take care
--k
> Chris Mattmann <ma...@apache.org>
> 2017-12-19 at 8.50 p
> Ping (
>
> Can I get 2 more VOTEs here so I can push this release out? It’s kind
> of needed for DRAT.
> We can release a 1.2.2 with Tom’s patch later, but would really love
> to release this. Thanks.
>
> Cheers,
> Chris
>
>
>
>
> On 11/12/17, 9:53 AM, "Chris Mattmann" <ma...@apache.org> wrote:
>
> Hi Folks,
>
>
>
> I have posted a 1st release candidate for the Apache OODT 1.2.1
> release. The
>
> source code is at:
>
> https://dist.apache.org/repos/dist/dev/oodt/
>
>
>
> For more detailed information, see the included CHANGES.txt file for
> details on
>
> release contents and latest changes. The release was made using the OODT
>
> release process, documented on the Wiki here:
>
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
>
>
> The release was made from the OODT 1.2 tag at:
>
> https://github.com/apache/oodt/tree/1.2.1/
>
>
>
> A staged Maven repository is available at:
>
> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
>
>
>
> Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
>
> open for at least the next 72 hours.
>
>
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
>
> release candidate and voice their approval or disapproval. The vote passes
>
> if at least three binding +1 votes are cast.
>
>
>
> [ ] +1 Release the packages as Apache OODT 1.2.1
>
>
>
> [ ] -1 Do not release the packages because...
>
>
>
> Thanks!
>
>
>
> Chris
>
>
>
> P.S. Here is my +1.
>
>
>
>
>
>
>
>
>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Sean Kelly <ke...@apache.org>.
Strangely this (and the release announcement) ended up in my spam folder.
Here goes:
MD5: ✓
SHA1: ✓
Python tests: ✓
Java tests: ✓
Signature: gpg: Can't check signature: No public key
Don't we also put a convenience copy of the KEYS file in the release dir?
Take care
--k
> Chris Mattmann <ma...@apache.org>
> 2017-12-19 at 8.50 p
> Ping (
>
> Can I get 2 more VOTEs here so I can push this release out? It’s kind
> of needed for DRAT.
> We can release a 1.2.2 with Tom’s patch later, but would really love
> to release this. Thanks.
>
> Cheers,
> Chris
>
>
>
>
> On 11/12/17, 9:53 AM, "Chris Mattmann" <ma...@apache.org> wrote:
>
> Hi Folks,
>
>
>
> I have posted a 1st release candidate for the Apache OODT 1.2.1
> release. The
>
> source code is at:
>
> https://dist.apache.org/repos/dist/dev/oodt/
>
>
>
> For more detailed information, see the included CHANGES.txt file for
> details on
>
> release contents and latest changes. The release was made using the OODT
>
> release process, documented on the Wiki here:
>
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
>
>
> The release was made from the OODT 1.2 tag at:
>
> https://github.com/apache/oodt/tree/1.2.1/
>
>
>
> A staged Maven repository is available at:
>
> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
>
>
>
> Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
>
> open for at least the next 72 hours.
>
>
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
>
> release candidate and voice their approval or disapproval. The vote passes
>
> if at least three binding +1 votes are cast.
>
>
>
> [ ] +1 Release the packages as Apache OODT 1.2.1
>
>
>
> [ ] -1 Do not release the packages because...
>
>
>
> Thanks!
>
>
>
> Chris
>
>
>
> P.S. Here is my +1.
>
>
>
>
>
>
>
>
>
>
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by Tom Barber <to...@spicule.co.uk>.
Checked it out and ran it through its paces looks GTG from my end
+1
On 20/12/17 14:47, Ramirez, Paul M (398N) wrote:
> +1
>
> Thanks,
> Paul
>
>
> ======================================================================
> Paul Ramirez
> Group Supervisor - Science Data System Operations Engineering (398N)
> Acting Group Supervisor - Computer Science for Data Intensive Applications (398M)
> NASA - Jet Propulsion Laboratory
> 4800 Oak Grove Dr.
> Pasadena, CA 91109 USA
> Mailstop: 158-242
> Office: 818-354-1015
> Cell: 818-395-8194
> ======================================================================
>
> On 12/19/17, 6:50 PM, "Chris Mattmann" <ma...@apache.org> wrote:
>
> Ping (
>
> Can I get 2 more VOTEs here so I can push this release out? It’s kind of needed for DRAT.
> We can release a 1.2.2 with Tom’s patch later, but would really love to release this. Thanks.
>
> Cheers,
> Chris
>
>
>
>
> On 11/12/17, 9:53 AM, "Chris Mattmann" <ma...@apache.org> wrote:
>
> Hi Folks,
>
>
>
> I have posted a 1st release candidate for the Apache OODT 1.2.1 release. The
>
> source code is at:
>
> https://dist.apache.org/repos/dist/dev/oodt/
>
>
>
> For more detailed information, see the included CHANGES.txt file for details on
>
> release contents and latest changes. The release was made using the OODT
>
> release process, documented on the Wiki here:
>
> https://cwiki.apache.org/confluence/display/OODT/Release+Process
>
>
>
> The release was made from the OODT 1.2 tag at:
>
> https://github.com/apache/oodt/tree/1.2.1/
>
>
>
> A staged Maven repository is available at:
>
> https://repository.apache.org/content/repositories/orgapacheoodt-1015/
>
>
>
> Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
>
> open for at least the next 72 hours.
>
>
>
> Only votes from OODT PMC are binding, but folks are welcome to check the
>
> release candidate and voice their approval or disapproval. The vote passes
>
> if at least three binding +1 votes are cast.
>
>
>
> [ ] +1 Release the packages as Apache OODT 1.2.1
>
>
>
> [ ] -1 Do not release the packages because...
>
>
>
> Thanks!
>
>
>
> Chris
>
>
>
> P.S. Here is my +1.
>
>
>
>
>
>
>
>
>
>
>
>
--
Spicule Limited is registered in England & Wales. Company Number: 09954122.
Registered office: First Floor, Telecom House, 125-135 Preston Road,
Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to whom
it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or copying.
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Spicule Limited. The
company accepts no liability for any damage caused by any virus transmitted
by this email. If you have received this message in error, please notify us
immediately by reply email before deleting it from your system. Service of
legal notice cannot be effected on Spicule Limited by email.
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
Posted by "Ramirez, Paul M (398N)" <pa...@jpl.nasa.gov>.
+1
Thanks,
Paul
======================================================================
Paul Ramirez
Group Supervisor - Science Data System Operations Engineering (398N)
Acting Group Supervisor - Computer Science for Data Intensive Applications (398M)
NASA - Jet Propulsion Laboratory
4800 Oak Grove Dr.
Pasadena, CA 91109 USA
Mailstop: 158-242
Office: 818-354-1015
Cell: 818-395-8194
======================================================================
On 12/19/17, 6:50 PM, "Chris Mattmann" <ma...@apache.org> wrote:
Ping (
Can I get 2 more VOTEs here so I can push this release out? It’s kind of needed for DRAT.
We can release a 1.2.2 with Tom’s patch later, but would really love to release this. Thanks.
Cheers,
Chris
On 11/12/17, 9:53 AM, "Chris Mattmann" <ma...@apache.org> wrote:
Hi Folks,
I have posted a 1st release candidate for the Apache OODT 1.2.1 release. The
source code is at:
https://dist.apache.org/repos/dist/dev/oodt/
For more detailed information, see the included CHANGES.txt file for details on
release contents and latest changes. The release was made using the OODT
release process, documented on the Wiki here:
https://cwiki.apache.org/confluence/display/OODT/Release+Process
The release was made from the OODT 1.2 tag at:
https://github.com/apache/oodt/tree/1.2.1/
A staged Maven repository is available at:
https://repository.apache.org/content/repositories/orgapacheoodt-1015/
Please vote on releasing these packages as Apache OODT 1.2.1. The vote is
open for at least the next 72 hours.
Only votes from OODT PMC are binding, but folks are welcome to check the
release candidate and voice their approval or disapproval. The vote passes
if at least three binding +1 votes are cast.
[ ] +1 Release the packages as Apache OODT 1.2.1
[ ] -1 Do not release the packages because...
Thanks!
Chris
P.S. Here is my +1.