You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by Tom Barber <to...@meteorite.bi> on 2018/02/02 03:14:21 UTC
Re: [VOTE] Apache OODT 1.2.1 release candidate #1
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>.
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.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>