[VOTE] Release Apache Commons Pool2 2.6.1

classic Classic list List threaded Threaded
48 messages Options
123
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release Apache Commons Pool2 2.6.1

Mark Struberg-2
Hi folks!

I'm currently preparing the release for commons-pool2-2.6.1

So far I did

* fix the missing parts in changes.xml
* generate + copy the RELEASE_NOTES
* run the maven release (after fixing the setup...)

The ASF staging repository is at
https://repository.apache.org/content/repositories/orgapachecommons-1396/

The source zip is at
https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388

I added my KEY (struberg at apache.org) to our dist KEYS file
https://dist.apache.org/repos/dist/release/commons/KEYS

I will now continue with the follow up steps and then call an official VOTE.

Please let me know if something went wrong so far!

LieGrue,
strub


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

Mark Struberg-2
PS: I've created the release in a GIT manner and pushed the according changes to my ASF-linked github repo

https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
the sha1 of the commit is
https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019

the tag is
https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
c910171

This will get pushed to the ASF cannonical repo once the VOTE succeeds.
Yay, this is the way GIT works and before someone not familiar with GIT screams that this is not hosted on ASF: This got discussed on the board level a long time ago (when we did DeltaSpike and CouchDB as the very first GIT repos at the ASF) and is perfectly fine as all this is based on cryptographically strong steps.

LieGrue,
strub


> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]>:
>
> Hi folks!
>
> I'm currently preparing the release for commons-pool2-2.6.1
>
> So far I did
>
> * fix the missing parts in changes.xml
> * generate + copy the RELEASE_NOTES
> * run the maven release (after fixing the setup...)
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I will now continue with the follow up steps and then call an official VOTE.
>
> Please let me know if something went wrong so far!
>
> LieGrue,
> strub
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

Mark Struberg-2
Oki, now the full VOTE text!

I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
The release was run with JDK-1.7 to ensure Java7 compatibility.


The ASF staging repository is at
https://repository.apache.org/content/repositories/orgapachecommons-1396/

The source zip is at
https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388

I added my KEY (struberg at apache.org) to our dist KEYS file
https://dist.apache.org/repos/dist/release/commons/KEYS

I've created the release in a GIT manner and pushed the according changes to my ASF-linked github repo

https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
the sha1 of the commit is
https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019

the tag is
https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
c910171

This will get pushed to the ASF cannonical repo once the VOTE succeeds.

Site will be updated once the release has passed.

Please VOTE:

[+1] go ship it!
[+0] meh, I don't care
[-1] stop there is a ${showstopper} (that means something _important_ is missing!)


Here is my own +1
checked:
* signature
* hashes
* LICENSE
* NOTICE
* rat
* builds fine with various JDKs


LieGrue,
strub





> Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]>:
>
> PS: I've created the release in a GIT manner and pushed the according changes to my ASF-linked github repo
>
> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> the sha1 of the commit is
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>
> the tag is
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> c910171
>
> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> Yay, this is the way GIT works and before someone not familiar with GIT screams that this is not hosted on ASF: This got discussed on the board level a long time ago (when we did DeltaSpike and CouchDB as the very first GIT repos at the ASF) and is perfectly fine as all this is based on cryptographically strong steps.
>
> LieGrue,
> strub
>
>
>> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]>:
>>
>> Hi folks!
>>
>> I'm currently preparing the release for commons-pool2-2.6.1
>>
>> So far I did
>>
>> * fix the missing parts in changes.xml
>> * generate + copy the RELEASE_NOTES
>> * run the maven release (after fixing the setup...)
>>
>> The ASF staging repository is at
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>
>> The source zip is at
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>> The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>> The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>
>> I added my KEY (struberg at apache.org) to our dist KEYS file
>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>
>> I will now continue with the follow up steps and then call an official VOTE.
>>
>> Please let me know if something went wrong so far!
>>
>> LieGrue,
>> strub
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

Mark Struberg-2
PS: the VOTE is open for 72h from now on.

LieGrue,
strub


> Am 14.11.2018 um 16:58 schrieb Mark Struberg <[hidden email]>:
>
> Oki, now the full VOTE text!
>
> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> The release was run with JDK-1.7 to ensure Java7 compatibility.
>
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I've created the release in a GIT manner and pushed the according changes to my ASF-linked github repo
>
> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> the sha1 of the commit is
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>
> the tag is
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> c910171
>
> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>
> Site will be updated once the release has passed.
>
> Please VOTE:
>
> [+1] go ship it!
> [+0] meh, I don't care
> [-1] stop there is a ${showstopper} (that means something _important_ is missing!)
>
>
> Here is my own +1
> checked:
> * signature
> * hashes
> * LICENSE
> * NOTICE
> * rat
> * builds fine with various JDKs
>
>
> LieGrue,
> strub
>
>
>
>
>
>> Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]>:
>>
>> PS: I've created the release in a GIT manner and pushed the according changes to my ASF-linked github repo
>>
>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>> the sha1 of the commit is
>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>
>> the tag is
>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>> c910171
>>
>> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>> Yay, this is the way GIT works and before someone not familiar with GIT screams that this is not hosted on ASF: This got discussed on the board level a long time ago (when we did DeltaSpike and CouchDB as the very first GIT repos at the ASF) and is perfectly fine as all this is based on cryptographically strong steps.
>>
>> LieGrue,
>> strub
>>
>>
>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]>:
>>>
>>> Hi folks!
>>>
>>> I'm currently preparing the release for commons-pool2-2.6.1
>>>
>>> So far I did
>>>
>>> * fix the missing parts in changes.xml
>>> * generate + copy the RELEASE_NOTES
>>> * run the maven release (after fixing the setup...)
>>>
>>> The ASF staging repository is at
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>
>>> The source zip is at
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>> The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>> The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>
>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>
>>> I will now continue with the follow up steps and then call an official VOTE.
>>>
>>> Please let me know if something went wrong so far!
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

garydgregory
Per http://www.apache.org/legal/release-policy.html#host-rc it should be OK
to host the RC sources on the Apache Nexus repo instead of the dist tree.

This is different from how we usually do RCs but is should be OK.

Not sure about using GitHub though...

Gary

On Wed, Nov 14, 2018, 09:00 Mark Struberg <[hidden email] wrote:

> PS: the VOTE is open for 72h from now on.
>
> LieGrue,
> strub
>
>
> > Am 14.11.2018 um 16:58 schrieb Mark Struberg <[hidden email]>:
> >
> > Oki, now the full VOTE text!
> >
> > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > The release was run with JDK-1.7 to ensure Java7 compatibility.
> >
> >
> > The ASF staging repository is at
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >
> > The source zip is at
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >
> > I added my KEY (struberg at apache.org) to our dist KEYS file
> > https://dist.apache.org/repos/dist/release/commons/KEYS
> >
> > I've created the release in a GIT manner and pushed the according
> changes to my ASF-linked github repo
> >
> > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > the sha1 of the commit is
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >
> > the tag is
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > c910171
> >
> > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> >
> > Site will be updated once the release has passed.
> >
> > Please VOTE:
> >
> > [+1] go ship it!
> > [+0] meh, I don't care
> > [-1] stop there is a ${showstopper} (that means something _important_ is
> missing!)
> >
> >
> > Here is my own +1
> > checked:
> > * signature
> > * hashes
> > * LICENSE
> > * NOTICE
> > * rat
> > * builds fine with various JDKs
> >
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> >
> >> Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]
> >:
> >>
> >> PS: I've created the release in a GIT manner and pushed the according
> changes to my ASF-linked github repo
> >>
> >> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> >> the sha1 of the commit is
> >>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >>
> >> the tag is
> >> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> >> c910171
> >>
> >> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> >> Yay, this is the way GIT works and before someone not familiar with GIT
> screams that this is not hosted on ASF: This got discussed on the board
> level a long time ago (when we did DeltaSpike and CouchDB as the very first
> GIT repos at the ASF) and is perfectly fine as all this is based on
> cryptographically strong steps.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]
> >:
> >>>
> >>> Hi folks!
> >>>
> >>> I'm currently preparing the release for commons-pool2-2.6.1
> >>>
> >>> So far I did
> >>>
> >>> * fix the missing parts in changes.xml
> >>> * generate + copy the RELEASE_NOTES
> >>> * run the maven release (after fixing the setup...)
> >>>
> >>> The ASF staging repository is at
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>>
> >>> The source zip is at
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >>> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >>> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>>
> >>> I added my KEY (struberg at apache.org) to our dist KEYS file
> >>> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>>
> >>> I will now continue with the follow up steps and then call an official
> VOTE.
> >>>
> >>> Please let me know if something went wrong so far!
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

Mark Struberg-2
We've done this since 2011 in a few projects.
It might seem to not be usual for commons but if you think through then it's perfectly ok (and also acked by the board):

A GIT commit is uniquely identified by the sha1 of the parrent commit + the the diff of the commit.
That's the magic why a repo can be cloned and handled independently at all.

When the VOTE did pass we simply do 2 steps:
1.) propagate the staging repo to proper (and check in the source-release.zip to our dist/release)
2.) push/merge the changes to master and push it to our cannnonical GIT repo at the ASF. + push the tag as well.

The sha1 doesn't change during that step, so it's guaranteed that it's the exact same as we voted on.

LieGrue,
strub



> Am 14.11.2018 um 17:15 schrieb Gary Gregory <[hidden email]>:
>
> Per http://www.apache.org/legal/release-policy.html#host-rc it should be OK
> to host the RC sources on the Apache Nexus repo instead of the dist tree.
>
> This is different from how we usually do RCs but is should be OK.
>
> Not sure about using GitHub though...
>
> Gary
>
> On Wed, Nov 14, 2018, 09:00 Mark Struberg <[hidden email] wrote:
>
>> PS: the VOTE is open for 72h from now on.
>>
>> LieGrue,
>> strub
>>
>>
>>> Am 14.11.2018 um 16:58 schrieb Mark Struberg <[hidden email]>:
>>>
>>> Oki, now the full VOTE text!
>>>
>>> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
>>> The release was run with JDK-1.7 to ensure Java7 compatibility.
>>>
>>>
>>> The ASF staging repository is at
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>
>>> The source zip is at
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>> The sha1 of the source-release zip is
>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>> The sha512 is
>> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>
>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>
>>> I've created the release in a GIT manner and pushed the according
>> changes to my ASF-linked github repo
>>>
>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>>> the sha1 of the commit is
>>>
>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>>
>>> the tag is
>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>>> c910171
>>>
>>> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>>>
>>> Site will be updated once the release has passed.
>>>
>>> Please VOTE:
>>>
>>> [+1] go ship it!
>>> [+0] meh, I don't care
>>> [-1] stop there is a ${showstopper} (that means something _important_ is
>> missing!)
>>>
>>>
>>> Here is my own +1
>>> checked:
>>> * signature
>>> * hashes
>>> * LICENSE
>>> * NOTICE
>>> * rat
>>> * builds fine with various JDKs
>>>
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>>
>>>
>>>> Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]
>>> :
>>>>
>>>> PS: I've created the release in a GIT manner and pushed the according
>> changes to my ASF-linked github repo
>>>>
>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>>>> the sha1 of the commit is
>>>>
>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>>>
>>>> the tag is
>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>>>> c910171
>>>>
>>>> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>>>> Yay, this is the way GIT works and before someone not familiar with GIT
>> screams that this is not hosted on ASF: This got discussed on the board
>> level a long time ago (when we did DeltaSpike and CouchDB as the very first
>> GIT repos at the ASF) and is perfectly fine as all this is based on
>> cryptographically strong steps.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]
>>> :
>>>>>
>>>>> Hi folks!
>>>>>
>>>>> I'm currently preparing the release for commons-pool2-2.6.1
>>>>>
>>>>> So far I did
>>>>>
>>>>> * fix the missing parts in changes.xml
>>>>> * generate + copy the RELEASE_NOTES
>>>>> * run the maven release (after fixing the setup...)
>>>>>
>>>>> The ASF staging repository is at
>>>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>>>
>>>>> The source zip is at
>>>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>>>> The sha1 of the source-release zip is
>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>>>> The sha512 is
>> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>>>
>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>>>
>>>>> I will now continue with the follow up steps and then call an official
>> VOTE.
>>>>>
>>>>> Please let me know if something went wrong so far!
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

garydgregory
In reply to this post by Mark Struberg-2
Is there a site available?

Gary

On Wed, Nov 14, 2018, 08:59 Mark Struberg <[hidden email] wrote:

> Oki, now the full VOTE text!
>
> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> The release was run with JDK-1.7 to ensure Java7 compatibility.
>
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I've created the release in a GIT manner and pushed the according changes
> to my ASF-linked github repo
>
> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> the sha1 of the commit is
>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>
> the tag is
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> c910171
> <https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171>
>
> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>
> Site will be updated once the release has passed.
>
> Please VOTE:
>
> [+1] go ship it!
> [+0] meh, I don't care
> [-1] stop there is a ${showstopper} (that means something _important_ is
> missing!)
>
>
> Here is my own +1
> checked:
> * signature
> * hashes
> * LICENSE
> * NOTICE
> * rat
> * builds fine with various JDKs
>
>
> LieGrue,
> strub
>
>
>
>
>
> > Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]
> >:
> >
> > PS: I've created the release in a GIT manner and pushed the according
> changes to my ASF-linked github repo
> >
> > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > the sha1 of the commit is
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >
> > the tag is
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > c910171
> >
> > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > Yay, this is the way GIT works and before someone not familiar with GIT
> screams that this is not hosted on ASF: This got discussed on the board
> level a long time ago (when we did DeltaSpike and CouchDB as the very first
> GIT repos at the ASF) and is perfectly fine as all this is based on
> cryptographically strong steps.
> >
> > LieGrue,
> > strub
> >
> >
> >> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]
> >:
> >>
> >> Hi folks!
> >>
> >> I'm currently preparing the release for commons-pool2-2.6.1
> >>
> >> So far I did
> >>
> >> * fix the missing parts in changes.xml
> >> * generate + copy the RELEASE_NOTES
> >> * run the maven release (after fixing the setup...)
> >>
> >> The ASF staging repository is at
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>
> >> The source zip is at
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>
> >> I added my KEY (struberg at apache.org) to our dist KEYS file
> >> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>
> >> I will now continue with the follow up steps and then call an official
> VOTE.
> >>
> >> Please let me know if something went wrong so far!
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

garydgregory
In reply to this post by Mark Struberg-2
On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg <[hidden email]>
wrote:

> Oki, now the full VOTE text!
>
> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> The release was run with JDK-1.7 to ensure Java7 compatibility.
>
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>

For me:

$ sha512sum commons-pool2-2.6.1-src.zip
2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
*commons-pool2-2.6.1-src.zip

Which is not what you list above. Please advise.

Gary


>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I've created the release in a GIT manner and pushed the according changes
> to my ASF-linked github repo
>
> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> the sha1 of the commit is
>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>
> the tag is
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> c910171
> <https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171>
>
> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>
> Site will be updated once the release has passed.
>
> Please VOTE:
>
> [+1] go ship it!
> [+0] meh, I don't care
> [-1] stop there is a ${showstopper} (that means something _important_ is
> missing!)
>
>
> Here is my own +1
> checked:
> * signature
> * hashes
> * LICENSE
> * NOTICE
> * rat
> * builds fine with various JDKs
>
>
> LieGrue,
> strub
>
>
>
>
>
> > Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]
> >:
> >
> > PS: I've created the release in a GIT manner and pushed the according
> changes to my ASF-linked github repo
> >
> > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > the sha1 of the commit is
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >
> > the tag is
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > c910171
> >
> > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > Yay, this is the way GIT works and before someone not familiar with GIT
> screams that this is not hosted on ASF: This got discussed on the board
> level a long time ago (when we did DeltaSpike and CouchDB as the very first
> GIT repos at the ASF) and is perfectly fine as all this is based on
> cryptographically strong steps.
> >
> > LieGrue,
> > strub
> >
> >
> >> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]
> >:
> >>
> >> Hi folks!
> >>
> >> I'm currently preparing the release for commons-pool2-2.6.1
> >>
> >> So far I did
> >>
> >> * fix the missing parts in changes.xml
> >> * generate + copy the RELEASE_NOTES
> >> * run the maven release (after fixing the setup...)
> >>
> >> The ASF staging repository is at
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>
> >> The source zip is at
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>
> >> I added my KEY (struberg at apache.org) to our dist KEYS file
> >> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>
> >> I will now continue with the follow up steps and then call an official
> VOTE.
> >>
> >> Please let me know if something went wrong so far!
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

Romain Manni-Bucau
Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a écrit :

> On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg <[hidden email]>
> wrote:
>
> > Oki, now the full VOTE text!
> >
> > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > The release was run with JDK-1.7 to ensure Java7 compatibility.
> >
> >
> > The ASF staging repository is at
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >
> > The source zip is at
> >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > The sha1 of the source-release zip is
> > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > The sha512 is
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >
>
> For me:
>
> $ sha512sum commons-pool2-2.6.1-src.zip
>
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> *commons-pool2-2.6.1-src.zip
>
> Which is not what you list above. Please advise.
>

Src vs source-release?






> Gary
>
>
> >
> > I added my KEY (struberg at apache.org) to our dist KEYS file
> > https://dist.apache.org/repos/dist/release/commons/KEYS
> >
> > I've created the release in a GIT manner and pushed the according changes
> > to my ASF-linked github repo
> >
> > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > the sha1 of the commit is
> >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >
> > the tag is
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > c910171
> > <
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171>
> >
> > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> >
> > Site will be updated once the release has passed.
> >
> > Please VOTE:
> >
> > [+1] go ship it!
> > [+0] meh, I don't care
> > [-1] stop there is a ${showstopper} (that means something _important_ is
> > missing!)
> >
> >
> > Here is my own +1
> > checked:
> > * signature
> > * hashes
> > * LICENSE
> > * NOTICE
> > * rat
> > * builds fine with various JDKs
> >
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> >
> > > Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]
> > >:
> > >
> > > PS: I've created the release in a GIT manner and pushed the according
> > changes to my ASF-linked github repo
> > >
> > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > the sha1 of the commit is
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >
> > > the tag is
> > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > c910171
> > >
> > > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > > Yay, this is the way GIT works and before someone not familiar with GIT
> > screams that this is not hosted on ASF: This got discussed on the board
> > level a long time ago (when we did DeltaSpike and CouchDB as the very
> first
> > GIT repos at the ASF) and is perfectly fine as all this is based on
> > cryptographically strong steps.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> <[hidden email]
> > >:
> > >>
> > >> Hi folks!
> > >>
> > >> I'm currently preparing the release for commons-pool2-2.6.1
> > >>
> > >> So far I did
> > >>
> > >> * fix the missing parts in changes.xml
> > >> * generate + copy the RELEASE_NOTES
> > >> * run the maven release (after fixing the setup...)
> > >>
> > >> The ASF staging repository is at
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >>
> > >> The source zip is at
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > >> The sha1 of the source-release zip is
> > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > >> The sha512 is
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >>
> > >> I added my KEY (struberg at apache.org) to our dist KEYS file
> > >> https://dist.apache.org/repos/dist/release/commons/KEYS
> > >>
> > >> I will now continue with the follow up steps and then call an official
> > VOTE.
> > >>
> > >> Please let me know if something went wrong so far!
> > >>
> > >> LieGrue,
> > >> strub
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [hidden email]
> > >> For additional commands, e-mail: [hidden email]
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

garydgregory
On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <[hidden email]>
wrote:

> Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a écrit
> :
>
> > On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg <[hidden email]
> >
> > wrote:
> >
> > > Oki, now the full VOTE text!
> > >
> > > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > > The release was run with JDK-1.7 to ensure Java7 compatibility.
> > >
> > >
> > > The ASF staging repository is at
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >
> > > The source zip is at
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >
> >
> > For me:
> >
> > $ sha512sum commons-pool2-2.6.1-src.zip
> >
> >
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> > *commons-pool2-2.6.1-src.zip
> >
> > Which is not what you list above. Please advise.
> >
>
> Src vs source-release?
>

That's the problem with inventing a new release process... why do we have
BOTH:

https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
AND
https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip

And more importantly why are they _different_? Which one will be used in
the dist/release area?

Gary



>
>
>
>
>
> > Gary
> >
> >
> > >
> > > I added my KEY (struberg at apache.org) to our dist KEYS file
> > > https://dist.apache.org/repos/dist/release/commons/KEYS
> > >
> > > I've created the release in a GIT manner and pushed the according
> changes
> > > to my ASF-linked github repo
> > >
> > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > the sha1 of the commit is
> > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >
> > > the tag is
> > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > c910171
> > > <
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> >
> > >
> > > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > >
> > > Site will be updated once the release has passed.
> > >
> > > Please VOTE:
> > >
> > > [+1] go ship it!
> > > [+0] meh, I don't care
> > > [-1] stop there is a ${showstopper} (that means something _important_
> is
> > > missing!)
> > >
> > >
> > > Here is my own +1
> > > checked:
> > > * signature
> > > * hashes
> > > * LICENSE
> > > * NOTICE
> > > * rat
> > > * builds fine with various JDKs
> > >
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >
> > >
> > >
> > > > Am 14.11.2018 um 10:13 schrieb Mark Struberg
> <[hidden email]
> > > >:
> > > >
> > > > PS: I've created the release in a GIT manner and pushed the according
> > > changes to my ASF-linked github repo
> > > >
> > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > the sha1 of the commit is
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > >
> > > > the tag is
> > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > c910171
> > > >
> > > > This will get pushed to the ASF cannonical repo once the VOTE
> succeeds.
> > > > Yay, this is the way GIT works and before someone not familiar with
> GIT
> > > screams that this is not hosted on ASF: This got discussed on the board
> > > level a long time ago (when we did DeltaSpike and CouchDB as the very
> > first
> > > GIT repos at the ASF) and is perfectly fine as all this is based on
> > > cryptographically strong steps.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> > <[hidden email]
> > > >:
> > > >>
> > > >> Hi folks!
> > > >>
> > > >> I'm currently preparing the release for commons-pool2-2.6.1
> > > >>
> > > >> So far I did
> > > >>
> > > >> * fix the missing parts in changes.xml
> > > >> * generate + copy the RELEASE_NOTES
> > > >> * run the maven release (after fixing the setup...)
> > > >>
> > > >> The ASF staging repository is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > > >>
> > > >> The source zip is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > >> The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > >> The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > > >>
> > > >> I added my KEY (struberg at apache.org) to our dist KEYS file
> > > >> https://dist.apache.org/repos/dist/release/commons/KEYS
> > > >>
> > > >> I will now continue with the follow up steps and then call an
> official
> > > VOTE.
> > > >>
> > > >> Please let me know if something went wrong so far!
> > > >>
> > > >> LieGrue,
> > > >> strub
> > > >>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: [hidden email]
> > > >> For additional commands, e-mail: [hidden email]
> > > >>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

garydgregory
In reply to this post by Mark Struberg-2
Should we cancel this RC to include:

https://issues.apache.org/jira/browse/POOL-359

?

Gary

On Wed, Nov 14, 2018 at 1:17 AM Mark Struberg <[hidden email]>
wrote:

> Hi folks!
>
> I'm currently preparing the release for commons-pool2-2.6.1
>
> So far I did
>
> * fix the missing parts in changes.xml
> * generate + copy the RELEASE_NOTES
> * run the maven release (after fixing the setup...)
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I will now continue with the follow up steps and then call an official
> VOTE.
>
> Please let me know if something went wrong so far!
>
> LieGrue,
> strub
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

Romain Manni-Bucau
In reply to this post by garydgregory
Le ven. 16 nov. 2018 22:54, Gary Gregory <[hidden email]> a écrit :

> On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <[hidden email]>
> wrote:
>
> > Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a
> écrit
> > :
> >
> > > On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg
> <[hidden email]
> > >
> > > wrote:
> > >
> > > > Oki, now the full VOTE text!
> > > >
> > > > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > > > The release was run with JDK-1.7 to ensure Java7 compatibility.
> > > >
> > > >
> > > > The ASF staging repository is at
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > > >
> > > > The source zip is at
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > > The sha1 of the source-release zip is
> > > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > > The sha512 is
> > > >
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > > >
> > >
> > > For me:
> > >
> > > $ sha512sum commons-pool2-2.6.1-src.zip
> > >
> > >
> >
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> > > *commons-pool2-2.6.1-src.zip
> > >
> > > Which is not what you list above. Please advise.
> > >
> >
> > Src vs source-release?
> >
>
> That's the problem with inventing a new release process... why do we have
> BOTH:
>
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
> AND
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip
>
> And more importantly why are they _different_? Which one will be used in
> the dist/release area?
>


Looks like pool didnt do its homework and kept the old assembly (src),
source-release comes from the parent and is likely the one to keep IMHO


> Gary
>
>
>
> >
> >
> >
> >
> >
> > > Gary
> > >
> > >
> > > >
> > > > I added my KEY (struberg at apache.org) to our dist KEYS file
> > > > https://dist.apache.org/repos/dist/release/commons/KEYS
> > > >
> > > > I've created the release in a GIT manner and pushed the according
> > changes
> > > > to my ASF-linked github repo
> > > >
> > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > the sha1 of the commit is
> > > >
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > >
> > > > the tag is
> > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > c910171
> > > > <
> > >
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> > >
> > > >
> > > > This will get pushed to the ASF cannonical repo once the VOTE
> succeeds.
> > > >
> > > > Site will be updated once the release has passed.
> > > >
> > > > Please VOTE:
> > > >
> > > > [+1] go ship it!
> > > > [+0] meh, I don't care
> > > > [-1] stop there is a ${showstopper} (that means something _important_
> > is
> > > > missing!)
> > > >
> > > >
> > > > Here is my own +1
> > > > checked:
> > > > * signature
> > > > * hashes
> > > > * LICENSE
> > > > * NOTICE
> > > > * rat
> > > > * builds fine with various JDKs
> > > >
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > > Am 14.11.2018 um 10:13 schrieb Mark Struberg
> > <[hidden email]
> > > > >:
> > > > >
> > > > > PS: I've created the release in a GIT manner and pushed the
> according
> > > > changes to my ASF-linked github repo
> > > > >
> > > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > > the sha1 of the commit is
> > > > >
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > > >
> > > > > the tag is
> > > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > > c910171
> > > > >
> > > > > This will get pushed to the ASF cannonical repo once the VOTE
> > succeeds.
> > > > > Yay, this is the way GIT works and before someone not familiar with
> > GIT
> > > > screams that this is not hosted on ASF: This got discussed on the
> board
> > > > level a long time ago (when we did DeltaSpike and CouchDB as the very
> > > first
> > > > GIT repos at the ASF) and is perfectly fine as all this is based on
> > > > cryptographically strong steps.
> > > > >
> > > > > LieGrue,
> > > > > strub
> > > > >
> > > > >
> > > > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> > > <[hidden email]
> > > > >:
> > > > >>
> > > > >> Hi folks!
> > > > >>
> > > > >> I'm currently preparing the release for commons-pool2-2.6.1
> > > > >>
> > > > >> So far I did
> > > > >>
> > > > >> * fix the missing parts in changes.xml
> > > > >> * generate + copy the RELEASE_NOTES
> > > > >> * run the maven release (after fixing the setup...)
> > > > >>
> > > > >> The ASF staging repository is at
> > > > >>
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > > > >>
> > > > >> The source zip is at
> > > > >>
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > > >> The sha1 of the source-release zip is
> > > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > > >> The sha512 is
> > > >
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > > > >>
> > > > >> I added my KEY (struberg at apache.org) to our dist KEYS file
> > > > >> https://dist.apache.org/repos/dist/release/commons/KEYS
> > > > >>
> > > > >> I will now continue with the follow up steps and then call an
> > official
> > > > VOTE.
> > > > >>
> > > > >> Please let me know if something went wrong so far!
> > > > >>
> > > > >> LieGrue,
> > > > >> strub
> > > > >>
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: [hidden email]
> > > > >> For additional commands, e-mail: [hidden email]
> > > > >>
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

garydgregory
In reply to this post by Romain Manni-Bucau
On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <[hidden email]>
wrote:

> Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a écrit
> :
>
> > On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg <[hidden email]
> >
> > wrote:
> >
> > > Oki, now the full VOTE text!
> > >
> > > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > > The release was run with JDK-1.7 to ensure Java7 compatibility.
> > >
> > >
> > > The ASF staging repository is at
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >
> > > The source zip is at
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >
> >
> > For me:
> >
> > $ sha512sum commons-pool2-2.6.1-src.zip
> >
> >
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> > *commons-pool2-2.6.1-src.zip
> >
> > Which is not what you list above. Please advise.
> >
>
> Src vs source-release?
>

Yes, the hash matches source-release, thank you!

Gary


>
>
>
>
>
> > Gary
> >
> >
> > >
> > > I added my KEY (struberg at apache.org) to our dist KEYS file
> > > https://dist.apache.org/repos/dist/release/commons/KEYS
> > >
> > > I've created the release in a GIT manner and pushed the according
> changes
> > > to my ASF-linked github repo
> > >
> > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > the sha1 of the commit is
> > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >
> > > the tag is
> > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > c910171
> > > <
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> >
> > >
> > > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > >
> > > Site will be updated once the release has passed.
> > >
> > > Please VOTE:
> > >
> > > [+1] go ship it!
> > > [+0] meh, I don't care
> > > [-1] stop there is a ${showstopper} (that means something _important_
> is
> > > missing!)
> > >
> > >
> > > Here is my own +1
> > > checked:
> > > * signature
> > > * hashes
> > > * LICENSE
> > > * NOTICE
> > > * rat
> > > * builds fine with various JDKs
> > >
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >
> > >
> > >
> > > > Am 14.11.2018 um 10:13 schrieb Mark Struberg
> <[hidden email]
> > > >:
> > > >
> > > > PS: I've created the release in a GIT manner and pushed the according
> > > changes to my ASF-linked github repo
> > > >
> > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > the sha1 of the commit is
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > >
> > > > the tag is
> > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > c910171
> > > >
> > > > This will get pushed to the ASF cannonical repo once the VOTE
> succeeds.
> > > > Yay, this is the way GIT works and before someone not familiar with
> GIT
> > > screams that this is not hosted on ASF: This got discussed on the board
> > > level a long time ago (when we did DeltaSpike and CouchDB as the very
> > first
> > > GIT repos at the ASF) and is perfectly fine as all this is based on
> > > cryptographically strong steps.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> > <[hidden email]
> > > >:
> > > >>
> > > >> Hi folks!
> > > >>
> > > >> I'm currently preparing the release for commons-pool2-2.6.1
> > > >>
> > > >> So far I did
> > > >>
> > > >> * fix the missing parts in changes.xml
> > > >> * generate + copy the RELEASE_NOTES
> > > >> * run the maven release (after fixing the setup...)
> > > >>
> > > >> The ASF staging repository is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > > >>
> > > >> The source zip is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > >> The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > >> The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > > >>
> > > >> I added my KEY (struberg at apache.org) to our dist KEYS file
> > > >> https://dist.apache.org/repos/dist/release/commons/KEYS
> > > >>
> > > >> I will now continue with the follow up steps and then call an
> official
> > > VOTE.
> > > >>
> > > >> Please let me know if something went wrong so far!
> > > >>
> > > >> LieGrue,
> > > >> strub
> > > >>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: [hidden email]
> > > >> For additional commands, e-mail: [hidden email]
> > > >>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

Rob Tompkins
In reply to this post by Mark Struberg-2
Pardon my being a little late to the party here.

Thoughts in going through release validation (might be a tad redundant):
        - We’re not much used to the maven assemblies being deployed to nexus, but that isn’t necessarily a problem.
        - Why do we have a "-source-release” and a “-src” artifact?
        - Do you plan to put the artifacts in the dist.apache.org area when you’re ready to promote?
        - There don’t seem to be any build errors with the release.
       
Given this is considerably different than our standard release paradigm, what is your plan on ensuring that the commons site looks like it does today (with the new release candidate present)? It seems clear that you didn’t follow the directions laid out at https://commons.apache.org/releases/prepare.html, how are we to be sure you will follow the directions at https://commons.apache.org/releases/release.html? That said, the RC itself seems to be valid.

Do we want to cancel to include Gary’s https://issues.apache.org/jira/browse/POOL-359 <https://issues.apache.org/jira/browse/POOL-359> in 2.6.1?

I don’t think that have a solid vote until the questions above get answered. But, if we can ensure that the site will look proper and all of the requisite artifacts are in their requisite locations, I don’t see any reason to block this release.

Let me know what your thoughts are.

Cheers,
-Rob

> On Nov 14, 2018, at 10:58 AM, Mark Struberg <[hidden email]> wrote:
>
> Oki, now the full VOTE text!
>
> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> The release was run with JDK-1.7 to ensure Java7 compatibility.
>
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I've created the release in a GIT manner and pushed the according changes to my ASF-linked github repo
>
> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> the sha1 of the commit is
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>
> the tag is
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> c910171
>
> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>
> Site will be updated once the release has passed.
>
> Please VOTE:
>
> [+1] go ship it!
> [+0] meh, I don't care
> [-1] stop there is a ${showstopper} (that means something _important_ is missing!)
>
>
> Here is my own +1
> checked:
> * signature
> * hashes
> * LICENSE
> * NOTICE
> * rat
> * builds fine with various JDKs
>
>
> LieGrue,
> strub
>
>
>
>
>
>> Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]>:
>>
>> PS: I've created the release in a GIT manner and pushed the according changes to my ASF-linked github repo
>>
>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>> the sha1 of the commit is
>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>
>> the tag is
>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>> c910171
>>
>> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>> Yay, this is the way GIT works and before someone not familiar with GIT screams that this is not hosted on ASF: This got discussed on the board level a long time ago (when we did DeltaSpike and CouchDB as the very first GIT repos at the ASF) and is perfectly fine as all this is based on cryptographically strong steps.
>>
>> LieGrue,
>> strub
>>
>>
>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]>:
>>>
>>> Hi folks!
>>>
>>> I'm currently preparing the release for commons-pool2-2.6.1
>>>
>>> So far I did
>>>
>>> * fix the missing parts in changes.xml
>>> * generate + copy the RELEASE_NOTES
>>> * run the maven release (after fixing the setup...)
>>>
>>> The ASF staging repository is at
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>
>>> The source zip is at
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>> The sha1 of the source-release zip is 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>> The sha512 is 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>
>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>
>>> I will now continue with the follow up steps and then call an official VOTE.
>>>
>>> Please let me know if something went wrong so far!
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons Pool2 2.6.1

garydgregory
Site build fails because we refer to

https://svn.apache.org/repos/infra/websites/production/commons/content/proper/pool

instead of
https://svn.apache.org/repos/infra/websites/production/commons/content/proper/commons-pool

Gary

On Sat, Nov 17, 2018 at 7:55 AM Rob Tompkins <[hidden email]> wrote:

> Pardon my being a little late to the party here.
>
> Thoughts in going through release validation (might be a tad redundant):
>         - We’re not much used to the maven assemblies being deployed to
> nexus, but that isn’t necessarily a problem.
>         - Why do we have a "-source-release” and a “-src” artifact?
>         - Do you plan to put the artifacts in the dist.apache.org area
> when you’re ready to promote?
>         - There don’t seem to be any build errors with the release.
>
> Given this is considerably different than our standard release paradigm,
> what is your plan on ensuring that the commons site looks like it does
> today (with the new release candidate present)? It seems clear that you
> didn’t follow the directions laid out at
> https://commons.apache.org/releases/prepare.html, how are we to be sure
> you will follow the directions at
> https://commons.apache.org/releases/release.html? That said, the RC
> itself seems to be valid.
>
> Do we want to cancel to include Gary’s
> https://issues.apache.org/jira/browse/POOL-359 <
> https://issues.apache.org/jira/browse/POOL-359> in 2.6.1?
>
> I don’t think that have a solid vote until the questions above get
> answered. But, if we can ensure that the site will look proper and all of
> the requisite artifacts are in their requisite locations, I don’t see any
> reason to block this release.
>
> Let me know what your thoughts are.
>
> Cheers,
> -Rob
>
> > On Nov 14, 2018, at 10:58 AM, Mark Struberg <[hidden email]>
> wrote:
> >
> > Oki, now the full VOTE text!
> >
> > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > The release was run with JDK-1.7 to ensure Java7 compatibility.
> >
> >
> > The ASF staging repository is at
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >
> > The source zip is at
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >
> > I added my KEY (struberg at apache.org) to our dist KEYS file
> > https://dist.apache.org/repos/dist/release/commons/KEYS
> >
> > I've created the release in a GIT manner and pushed the according
> changes to my ASF-linked github repo
> >
> > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > the sha1 of the commit is
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >
> > the tag is
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > c910171
> >
> > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> >
> > Site will be updated once the release has passed.
> >
> > Please VOTE:
> >
> > [+1] go ship it!
> > [+0] meh, I don't care
> > [-1] stop there is a ${showstopper} (that means something _important_ is
> missing!)
> >
> >
> > Here is my own +1
> > checked:
> > * signature
> > * hashes
> > * LICENSE
> > * NOTICE
> > * rat
> > * builds fine with various JDKs
> >
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> >
> >> Am 14.11.2018 um 10:13 schrieb Mark Struberg <[hidden email]
> >:
> >>
> >> PS: I've created the release in a GIT manner and pushed the according
> changes to my ASF-linked github repo
> >>
> >> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> >> the sha1 of the commit is
> >>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >>
> >> the tag is
> >> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> >> c910171
> >>
> >> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> >> Yay, this is the way GIT works and before someone not familiar with GIT
> screams that this is not hosted on ASF: This got discussed on the board
> level a long time ago (when we did DeltaSpike and CouchDB as the very first
> GIT repos at the ASF) and is perfectly fine as all this is based on
> cryptographically strong steps.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>> Am 14.11.2018 um 09:17 schrieb Mark Struberg <[hidden email]
> >:
> >>>
> >>> Hi folks!
> >>>
> >>> I'm currently preparing the release for commons-pool2-2.6.1
> >>>
> >>> So far I did
> >>>
> >>> * fix the missing parts in changes.xml
> >>> * generate + copy the RELEASE_NOTES
> >>> * run the maven release (after fixing the setup...)
> >>>
> >>> The ASF staging repository is at
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>>
> >>> The source zip is at
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >>> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >>> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>>
> >>> I added my KEY (struberg at apache.org) to our dist KEYS file
> >>> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>>
> >>> I will now continue with the follow up steps and then call an official
> VOTE.
> >>>
> >>> Please let me know if something went wrong so far!
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] [CANCEL] Release Apache Commons Pool2 2.6.1

Mark Struberg-2
In reply to this post by Romain Manni-Bucau
Oki, I now see what you mean.

We actually have 3 source zips now.

.src.zip
.source-release.zip
src.jar

That's a mess.

There should only be 2:
* source-release.zip is the official ASF packages whole build sources. This includes the pom, build structure etc.
* src.jar is the sources which are automatically downloaded by the IDEs for debugging purpose.

We have both of them because commons-pool2 is a single-module project.
And yes, we need both of them. What we do not need is the src.zip. I have no clue yet where this comes from but it shouldn't be here.


The good news:
By leveraging native GIT we now can simply a.) drop the maven stating repo in repository.a.o and b.) drop the release branch and tag from my github account and re-roll the release without any weird RC hacks.

Will do that,
* fix the maven setup
* happy to also include the new ticket
* re-roll the release this afternoon.

LieGrue,
strub

> Am 16.11.2018 um 23:10 schrieb Romain Manni-Bucau <[hidden email]>:
>
> Le ven. 16 nov. 2018 22:54, Gary Gregory <[hidden email]> a écrit :
>
>> On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <[hidden email]>
>> wrote:
>>
>>> Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a
>> écrit
>>> :
>>>
>>>> On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg
>> <[hidden email]
>>>>
>>>> wrote:
>>>>
>>>>> Oki, now the full VOTE text!
>>>>>
>>>>> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
>>>>> The release was run with JDK-1.7 to ensure Java7 compatibility.
>>>>>
>>>>>
>>>>> The ASF staging repository is at
>>>>>
>>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>>>
>>>>> The source zip is at
>>>>>
>>>>>
>>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>>>> The sha1 of the source-release zip is
>>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>>>> The sha512 is
>>>>>
>>>>
>>>
>> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>>>
>>>>
>>>> For me:
>>>>
>>>> $ sha512sum commons-pool2-2.6.1-src.zip
>>>>
>>>>
>>>
>> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
>>>> *commons-pool2-2.6.1-src.zip
>>>>
>>>> Which is not what you list above. Please advise.
>>>>
>>>
>>> Src vs source-release?
>>>
>>
>> That's the problem with inventing a new release process... why do we have
>> BOTH:
>>
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
>> AND
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip
>>
>> And more importantly why are they _different_? Which one will be used in
>> the dist/release area?
>>
>
>
> Looks like pool didnt do its homework and kept the old assembly (src),
> source-release comes from the parent and is likely the one to keep IMHO
>
>
>> Gary
>>
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>> Gary
>>>>
>>>>
>>>>>
>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>>>
>>>>> I've created the release in a GIT manner and pushed the according
>>> changes
>>>>> to my ASF-linked github repo
>>>>>
>>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>>>>> the sha1 of the commit is
>>>>>
>>>>>
>>>>
>>>
>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>>>>
>>>>> the tag is
>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>>>>> c910171
>>>>> <
>>>>
>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
>>>>
>>>>>
>>>>> This will get pushed to the ASF cannonical repo once the VOTE
>> succeeds.
>>>>>
>>>>> Site will be updated once the release has passed.
>>>>>
>>>>> Please VOTE:
>>>>>
>>>>> [+1] go ship it!
>>>>> [+0] meh, I don't care
>>>>> [-1] stop there is a ${showstopper} (that means something _important_
>>> is
>>>>> missing!)
>>>>>
>>>>>
>>>>> Here is my own +1
>>>>> checked:
>>>>> * signature
>>>>> * hashes
>>>>> * LICENSE
>>>>> * NOTICE
>>>>> * rat
>>>>> * builds fine with various JDKs
>>>>>
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Am 14.11.2018 um 10:13 schrieb Mark Struberg
>>> <[hidden email]
>>>>>> :
>>>>>>
>>>>>> PS: I've created the release in a GIT manner and pushed the
>> according
>>>>> changes to my ASF-linked github repo
>>>>>>
>>>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>>>>>> the sha1 of the commit is
>>>>>>
>>>>>
>>>>
>>>
>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>>>>>
>>>>>> the tag is
>>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>>>>>> c910171
>>>>>>
>>>>>> This will get pushed to the ASF cannonical repo once the VOTE
>>> succeeds.
>>>>>> Yay, this is the way GIT works and before someone not familiar with
>>> GIT
>>>>> screams that this is not hosted on ASF: This got discussed on the
>> board
>>>>> level a long time ago (when we did DeltaSpike and CouchDB as the very
>>>> first
>>>>> GIT repos at the ASF) and is perfectly fine as all this is based on
>>>>> cryptographically strong steps.
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>>
>>>>>>
>>>>>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg
>>>> <[hidden email]
>>>>>> :
>>>>>>>
>>>>>>> Hi folks!
>>>>>>>
>>>>>>> I'm currently preparing the release for commons-pool2-2.6.1
>>>>>>>
>>>>>>> So far I did
>>>>>>>
>>>>>>> * fix the missing parts in changes.xml
>>>>>>> * generate + copy the RELEASE_NOTES
>>>>>>> * run the maven release (after fixing the setup...)
>>>>>>>
>>>>>>> The ASF staging repository is at
>>>>>>>
>>>>>
>>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>>>>>
>>>>>>> The source zip is at
>>>>>>>
>>>>>
>>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>>>>>> The sha1 of the source-release zip is
>>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>>>>>> The sha512 is
>>>>>
>>>>
>>>
>> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>>>>>
>>>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>>>>>
>>>>>>> I will now continue with the follow up steps and then call an
>>> official
>>>>> VOTE.
>>>>>>>
>>>>>>> Please let me know if something went wrong so far!
>>>>>>>
>>>>>>> LieGrue,
>>>>>>> strub
>>>>>>>
>>>>>>>
>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] [CANCEL] Release Apache Commons Pool2 2.6.1

Rob Tompkins
I’d be happy to roll the release if we get master to where you want it.

Cheers,
-Rob

> On Nov 19, 2018, at 7:18 AM, Mark Struberg <[hidden email]> wrote:
>
> Oki, I now see what you mean.
>
> We actually have 3 source zips now.
>
> .src.zip
> .source-release.zip
> src.jar
>
> That's a mess.
>
> There should only be 2:
> * source-release.zip is the official ASF packages whole build sources. This includes the pom, build structure etc.
> * src.jar is the sources which are automatically downloaded by the IDEs for debugging purpose.
>
> We have both of them because commons-pool2 is a single-module project.
> And yes, we need both of them. What we do not need is the src.zip. I have no clue yet where this comes from but it shouldn't be here.
>
>
> The good news:
> By leveraging native GIT we now can simply a.) drop the maven stating repo in repository.a.o and b.) drop the release branch and tag from my github account and re-roll the release without any weird RC hacks.
>
> Will do that,
> * fix the maven setup
> * happy to also include the new ticket
> * re-roll the release this afternoon.
>
> LieGrue,
> strub
>
>> Am 16.11.2018 um 23:10 schrieb Romain Manni-Bucau <[hidden email]>:
>>
>> Le ven. 16 nov. 2018 22:54, Gary Gregory <[hidden email]> a écrit :
>>
>>> On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <[hidden email]>
>>> wrote:
>>>
>>>> Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a
>>> écrit
>>>> :
>>>>
>>>>> On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg
>>> <[hidden email]
>>>>>
>>>>> wrote:
>>>>>
>>>>>> Oki, now the full VOTE text!
>>>>>>
>>>>>> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
>>>>>> The release was run with JDK-1.7 to ensure Java7 compatibility.
>>>>>>
>>>>>>
>>>>>> The ASF staging repository is at
>>>>>>
>>>>>
>>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>>>>
>>>>>> The source zip is at
>>>>>>
>>>>>>
>>>>>
>>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>>>>> The sha1 of the source-release zip is
>>>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>>>>> The sha512 is
>>>>>>
>>>>>
>>>>
>>> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>>>>
>>>>>
>>>>> For me:
>>>>>
>>>>> $ sha512sum commons-pool2-2.6.1-src.zip
>>>>>
>>>>>
>>>>
>>> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
>>>>> *commons-pool2-2.6.1-src.zip
>>>>>
>>>>> Which is not what you list above. Please advise.
>>>>>
>>>>
>>>> Src vs source-release?
>>>>
>>>
>>> That's the problem with inventing a new release process... why do we have
>>> BOTH:
>>>
>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
>>> AND
>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip
>>>
>>> And more importantly why are they _different_? Which one will be used in
>>> the dist/release area?
>>>
>>
>>
>> Looks like pool didnt do its homework and kept the old assembly (src),
>> source-release comes from the parent and is likely the one to keep IMHO
>>
>>
>>> Gary
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Gary
>>>>>
>>>>>
>>>>>>
>>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>>>>
>>>>>> I've created the release in a GIT manner and pushed the according
>>>> changes
>>>>>> to my ASF-linked github repo
>>>>>>
>>>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>>>>>> the sha1 of the commit is
>>>>>>
>>>>>>
>>>>>
>>>>
>>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>>>>>
>>>>>> the tag is
>>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>>>>>> c910171
>>>>>> <
>>>>>
>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
>>>>>
>>>>>>
>>>>>> This will get pushed to the ASF cannonical repo once the VOTE
>>> succeeds.
>>>>>>
>>>>>> Site will be updated once the release has passed.
>>>>>>
>>>>>> Please VOTE:
>>>>>>
>>>>>> [+1] go ship it!
>>>>>> [+0] meh, I don't care
>>>>>> [-1] stop there is a ${showstopper} (that means something _important_
>>>> is
>>>>>> missing!)
>>>>>>
>>>>>>
>>>>>> Here is my own +1
>>>>>> checked:
>>>>>> * signature
>>>>>> * hashes
>>>>>> * LICENSE
>>>>>> * NOTICE
>>>>>> * rat
>>>>>> * builds fine with various JDKs
>>>>>>
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Am 14.11.2018 um 10:13 schrieb Mark Struberg
>>>> <[hidden email]
>>>>>>> :
>>>>>>>
>>>>>>> PS: I've created the release in a GIT manner and pushed the
>>> according
>>>>>> changes to my ASF-linked github repo
>>>>>>>
>>>>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
>>>>>>> the sha1 of the commit is
>>>>>>>
>>>>>>
>>>>>
>>>>
>>> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>>>>>>>
>>>>>>> the tag is
>>>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
>>>>>>> c910171
>>>>>>>
>>>>>>> This will get pushed to the ASF cannonical repo once the VOTE
>>>> succeeds.
>>>>>>> Yay, this is the way GIT works and before someone not familiar with
>>>> GIT
>>>>>> screams that this is not hosted on ASF: This got discussed on the
>>> board
>>>>>> level a long time ago (when we did DeltaSpike and CouchDB as the very
>>>>> first
>>>>>> GIT repos at the ASF) and is perfectly fine as all this is based on
>>>>>> cryptographically strong steps.
>>>>>>>
>>>>>>> LieGrue,
>>>>>>> strub
>>>>>>>
>>>>>>>
>>>>>>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg
>>>>> <[hidden email]
>>>>>>> :
>>>>>>>>
>>>>>>>> Hi folks!
>>>>>>>>
>>>>>>>> I'm currently preparing the release for commons-pool2-2.6.1
>>>>>>>>
>>>>>>>> So far I did
>>>>>>>>
>>>>>>>> * fix the missing parts in changes.xml
>>>>>>>> * generate + copy the RELEASE_NOTES
>>>>>>>> * run the maven release (after fixing the setup...)
>>>>>>>>
>>>>>>>> The ASF staging repository is at
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>>>>>>>>
>>>>>>>> The source zip is at
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
>>>>>>>> The sha1 of the source-release zip is
>>>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
>>>>>>>> The sha512 is
>>>>>>
>>>>>
>>>>
>>> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>>>>>>>>
>>>>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
>>>>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
>>>>>>>>
>>>>>>>> I will now continue with the follow up steps and then call an
>>>> official
>>>>>> VOTE.
>>>>>>>>
>>>>>>>> Please let me know if something went wrong so far!
>>>>>>>>
>>>>>>>> LieGrue,
>>>>>>>> strub
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] [CANCEL] Release Apache Commons Pool2 2.6.1

garydgregory
In reply to this post by Mark Struberg-2
On Mon, Nov 19, 2018 at 5:22 AM Mark Struberg <[hidden email]>
wrote:

> Oki, I now see what you mean.
>
> We actually have 3 source zips now.
>
> .src.zip
> .source-release.zip
> src.jar
>
> That's a mess.
>
> There should only be 2:
> * source-release.zip is the official ASF packages whole build sources.
> This includes the pom, build structure etc.
> * src.jar is the sources which are automatically downloaded by the IDEs
> for debugging purpose.
>

Nope, it's the "-sources" jar that is used in IDEs. The "-src" jar is what
_should_ contain all sources needed to build the jar and site.

"source-release" is not something we've used here before IIRC.

Gary


>
> We have both of them because commons-pool2 is a single-module project.
> And yes, we need both of them. What we do not need is the src.zip. I have
> no clue yet where this comes from but it shouldn't be here.
>
>
> The good news:
> By leveraging native GIT we now can simply a.) drop the maven stating repo
> in repository.a.o and b.) drop the release branch and tag from my github
> account and re-roll the release without any weird RC hacks.
>
> Will do that,
> * fix the maven setup
> * happy to also include the new ticket
> * re-roll the release this afternoon.
>
> LieGrue,
> strub
>
> > Am 16.11.2018 um 23:10 schrieb Romain Manni-Bucau <[hidden email]
> >:
> >
> > Le ven. 16 nov. 2018 22:54, Gary Gregory <[hidden email]> a
> écrit :
> >
> >> On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <
> [hidden email]>
> >> wrote:
> >>
> >>> Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a
> >> écrit
> >>> :
> >>>
> >>>> On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg
> >> <[hidden email]
> >>>>
> >>>> wrote:
> >>>>
> >>>>> Oki, now the full VOTE text!
> >>>>>
> >>>>> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> >>>>> The release was run with JDK-1.7 to ensure Java7 compatibility.
> >>>>>
> >>>>>
> >>>>> The ASF staging repository is at
> >>>>>
> >>>>
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>>>>
> >>>>> The source zip is at
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >>>>> The sha1 of the source-release zip is
> >>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >>>>> The sha512 is
> >>>>>
> >>>>
> >>>
> >>
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>>>>
> >>>>
> >>>> For me:
> >>>>
> >>>> $ sha512sum commons-pool2-2.6.1-src.zip
> >>>>
> >>>>
> >>>
> >>
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> >>>> *commons-pool2-2.6.1-src.zip
> >>>>
> >>>> Which is not what you list above. Please advise.
> >>>>
> >>>
> >>> Src vs source-release?
> >>>
> >>
> >> That's the problem with inventing a new release process... why do we
> have
> >> BOTH:
> >>
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
> >> AND
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip
> >>
> >> And more importantly why are they _different_? Which one will be used in
> >> the dist/release area?
> >>
> >
> >
> > Looks like pool didnt do its homework and kept the old assembly (src),
> > source-release comes from the parent and is likely the one to keep IMHO
> >
> >
> >> Gary
> >>
> >>
> >>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> Gary
> >>>>
> >>>>
> >>>>>
> >>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
> >>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>>>>
> >>>>> I've created the release in a GIT manner and pushed the according
> >>> changes
> >>>>> to my ASF-linked github repo
> >>>>>
> >>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> >>>>> the sha1 of the commit is
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >>>>>
> >>>>> the tag is
> >>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> >>>>> c910171
> >>>>> <
> >>>>
> >>
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> >>>>
> >>>>>
> >>>>> This will get pushed to the ASF cannonical repo once the VOTE
> >> succeeds.
> >>>>>
> >>>>> Site will be updated once the release has passed.
> >>>>>
> >>>>> Please VOTE:
> >>>>>
> >>>>> [+1] go ship it!
> >>>>> [+0] meh, I don't care
> >>>>> [-1] stop there is a ${showstopper} (that means something _important_
> >>> is
> >>>>> missing!)
> >>>>>
> >>>>>
> >>>>> Here is my own +1
> >>>>> checked:
> >>>>> * signature
> >>>>> * hashes
> >>>>> * LICENSE
> >>>>> * NOTICE
> >>>>> * rat
> >>>>> * builds fine with various JDKs
> >>>>>
> >>>>>
> >>>>> LieGrue,
> >>>>> strub
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Am 14.11.2018 um 10:13 schrieb Mark Struberg
> >>> <[hidden email]
> >>>>>> :
> >>>>>>
> >>>>>> PS: I've created the release in a GIT manner and pushed the
> >> according
> >>>>> changes to my ASF-linked github repo
> >>>>>>
> >>>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> >>>>>> the sha1 of the commit is
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >>>>>>
> >>>>>> the tag is
> >>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> >>>>>> c910171
> >>>>>>
> >>>>>> This will get pushed to the ASF cannonical repo once the VOTE
> >>> succeeds.
> >>>>>> Yay, this is the way GIT works and before someone not familiar with
> >>> GIT
> >>>>> screams that this is not hosted on ASF: This got discussed on the
> >> board
> >>>>> level a long time ago (when we did DeltaSpike and CouchDB as the very
> >>>> first
> >>>>> GIT repos at the ASF) and is perfectly fine as all this is based on
> >>>>> cryptographically strong steps.
> >>>>>>
> >>>>>> LieGrue,
> >>>>>> strub
> >>>>>>
> >>>>>>
> >>>>>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> >>>> <[hidden email]
> >>>>>> :
> >>>>>>>
> >>>>>>> Hi folks!
> >>>>>>>
> >>>>>>> I'm currently preparing the release for commons-pool2-2.6.1
> >>>>>>>
> >>>>>>> So far I did
> >>>>>>>
> >>>>>>> * fix the missing parts in changes.xml
> >>>>>>> * generate + copy the RELEASE_NOTES
> >>>>>>> * run the maven release (after fixing the setup...)
> >>>>>>>
> >>>>>>> The ASF staging repository is at
> >>>>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>>>>>>
> >>>>>>> The source zip is at
> >>>>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >>>>>>> The sha1 of the source-release zip is
> >>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >>>>>>> The sha512 is
> >>>>>
> >>>>
> >>>
> >>
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>>>>>>
> >>>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
> >>>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>>>>>>
> >>>>>>> I will now continue with the follow up steps and then call an
> >>> official
> >>>>> VOTE.
> >>>>>>>
> >>>>>>> Please let me know if something went wrong so far!
> >>>>>>>
> >>>>>>> LieGrue,
> >>>>>>> strub
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: [hidden email]
> >>>>> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] [CANCEL] Release Apache Commons Pool2 2.6.1

Romain Manni-Bucau
AFAIK source-release is quite standard @asf so likely saner to use that
from now on IMHO.
Agree sources is needed but Think Mark's point was more about assemblies
than default release artifacts.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le lun. 19 nov. 2018 à 15:54, Gary Gregory <[hidden email]> a
écrit :

> On Mon, Nov 19, 2018 at 5:22 AM Mark Struberg <[hidden email]>
> wrote:
>
> > Oki, I now see what you mean.
> >
> > We actually have 3 source zips now.
> >
> > .src.zip
> > .source-release.zip
> > src.jar
> >
> > That's a mess.
> >
> > There should only be 2:
> > * source-release.zip is the official ASF packages whole build sources.
> > This includes the pom, build structure etc.
> > * src.jar is the sources which are automatically downloaded by the IDEs
> > for debugging purpose.
> >
>
> Nope, it's the "-sources" jar that is used in IDEs. The "-src" jar is what
> _should_ contain all sources needed to build the jar and site.
>
> "source-release" is not something we've used here before IIRC.
>
> Gary
>
>
> >
> > We have both of them because commons-pool2 is a single-module project.
> > And yes, we need both of them. What we do not need is the src.zip. I have
> > no clue yet where this comes from but it shouldn't be here.
> >
> >
> > The good news:
> > By leveraging native GIT we now can simply a.) drop the maven stating
> repo
> > in repository.a.o and b.) drop the release branch and tag from my github
> > account and re-roll the release without any weird RC hacks.
> >
> > Will do that,
> > * fix the maven setup
> > * happy to also include the new ticket
> > * re-roll the release this afternoon.
> >
> > LieGrue,
> > strub
> >
> > > Am 16.11.2018 um 23:10 schrieb Romain Manni-Bucau <
> [hidden email]
> > >:
> > >
> > > Le ven. 16 nov. 2018 22:54, Gary Gregory <[hidden email]> a
> > écrit :
> > >
> > >> On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <
> > [hidden email]>
> > >> wrote:
> > >>
> > >>> Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a
> > >> écrit
> > >>> :
> > >>>
> > >>>> On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg
> > >> <[hidden email]
> > >>>>
> > >>>> wrote:
> > >>>>
> > >>>>> Oki, now the full VOTE text!
> > >>>>>
> > >>>>> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > >>>>> The release was run with JDK-1.7 to ensure Java7 compatibility.
> > >>>>>
> > >>>>>
> > >>>>> The ASF staging repository is at
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >>>>>
> > >>>>> The source zip is at
> > >>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > >>>>> The sha1 of the source-release zip is
> > >>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > >>>>> The sha512 is
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >>>>>
> > >>>>
> > >>>> For me:
> > >>>>
> > >>>> $ sha512sum commons-pool2-2.6.1-src.zip
> > >>>>
> > >>>>
> > >>>
> > >>
> >
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> > >>>> *commons-pool2-2.6.1-src.zip
> > >>>>
> > >>>> Which is not what you list above. Please advise.
> > >>>>
> > >>>
> > >>> Src vs source-release?
> > >>>
> > >>
> > >> That's the problem with inventing a new release process... why do we
> > have
> > >> BOTH:
> > >>
> > >>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
> > >> AND
> > >>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip
> > >>
> > >> And more importantly why are they _different_? Which one will be used
> in
> > >> the dist/release area?
> > >>
> > >
> > >
> > > Looks like pool didnt do its homework and kept the old assembly (src),
> > > source-release comes from the parent and is likely the one to keep IMHO
> > >
> > >
> > >> Gary
> > >>
> > >>
> > >>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>> Gary
> > >>>>
> > >>>>
> > >>>>>
> > >>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
> > >>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
> > >>>>>
> > >>>>> I've created the release in a GIT manner and pushed the according
> > >>> changes
> > >>>>> to my ASF-linked github repo
> > >>>>>
> > >>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > >>>>> the sha1 of the commit is
> > >>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >>>>>
> > >>>>> the tag is
> > >>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > >>>>> c910171
> > >>>>> <
> > >>>>
> > >>
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> > >>>>
> > >>>>>
> > >>>>> This will get pushed to the ASF cannonical repo once the VOTE
> > >> succeeds.
> > >>>>>
> > >>>>> Site will be updated once the release has passed.
> > >>>>>
> > >>>>> Please VOTE:
> > >>>>>
> > >>>>> [+1] go ship it!
> > >>>>> [+0] meh, I don't care
> > >>>>> [-1] stop there is a ${showstopper} (that means something
> _important_
> > >>> is
> > >>>>> missing!)
> > >>>>>
> > >>>>>
> > >>>>> Here is my own +1
> > >>>>> checked:
> > >>>>> * signature
> > >>>>> * hashes
> > >>>>> * LICENSE
> > >>>>> * NOTICE
> > >>>>> * rat
> > >>>>> * builds fine with various JDKs
> > >>>>>
> > >>>>>
> > >>>>> LieGrue,
> > >>>>> strub
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> Am 14.11.2018 um 10:13 schrieb Mark Struberg
> > >>> <[hidden email]
> > >>>>>> :
> > >>>>>>
> > >>>>>> PS: I've created the release in a GIT manner and pushed the
> > >> according
> > >>>>> changes to my ASF-linked github repo
> > >>>>>>
> > >>>>>>
> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > >>>>>> the sha1 of the commit is
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >>>>>>
> > >>>>>> the tag is
> > >>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > >>>>>> c910171
> > >>>>>>
> > >>>>>> This will get pushed to the ASF cannonical repo once the VOTE
> > >>> succeeds.
> > >>>>>> Yay, this is the way GIT works and before someone not familiar
> with
> > >>> GIT
> > >>>>> screams that this is not hosted on ASF: This got discussed on the
> > >> board
> > >>>>> level a long time ago (when we did DeltaSpike and CouchDB as the
> very
> > >>>> first
> > >>>>> GIT repos at the ASF) and is perfectly fine as all this is based on
> > >>>>> cryptographically strong steps.
> > >>>>>>
> > >>>>>> LieGrue,
> > >>>>>> strub
> > >>>>>>
> > >>>>>>
> > >>>>>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> > >>>> <[hidden email]
> > >>>>>> :
> > >>>>>>>
> > >>>>>>> Hi folks!
> > >>>>>>>
> > >>>>>>> I'm currently preparing the release for commons-pool2-2.6.1
> > >>>>>>>
> > >>>>>>> So far I did
> > >>>>>>>
> > >>>>>>> * fix the missing parts in changes.xml
> > >>>>>>> * generate + copy the RELEASE_NOTES
> > >>>>>>> * run the maven release (after fixing the setup...)
> > >>>>>>>
> > >>>>>>> The ASF staging repository is at
> > >>>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >>>>>>>
> > >>>>>>> The source zip is at
> > >>>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > >>>>>>> The sha1 of the source-release zip is
> > >>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > >>>>>>> The sha512 is
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >>>>>>>
> > >>>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
> > >>>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
> > >>>>>>>
> > >>>>>>> I will now continue with the follow up steps and then call an
> > >>> official
> > >>>>> VOTE.
> > >>>>>>>
> > >>>>>>> Please let me know if something went wrong so far!
> > >>>>>>>
> > >>>>>>> LieGrue,
> > >>>>>>> strub
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>> ---------------------------------------------------------------------
> > >>>>>>> To unsubscribe, e-mail: [hidden email]
> > >>>>>>> For additional commands, e-mail: [hidden email]
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >> ---------------------------------------------------------------------
> > >>>>>> To unsubscribe, e-mail: [hidden email]
> > >>>>>> For additional commands, e-mail: [hidden email]
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> ---------------------------------------------------------------------
> > >>>>> To unsubscribe, e-mail: [hidden email]
> > >>>>> For additional commands, e-mail: [hidden email]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] [CANCEL] Release Apache Commons Pool2 2.6.1

garydgregory
In reply to this post by Rob Tompkins
On Mon, Nov 19, 2018 at 6:04 AM Rob Tompkins <[hidden email]> wrote:

> I’d be happy to roll the release if we get master to where you want it.
>

IMO, we should integrate the recent PR I mentioned and roll RC3. Note that
this vote subject thread did not contain an RC number. Sticking to the
usual process would be less troublesome IMO.

Gary


>
> Cheers,
> -Rob
>
> > On Nov 19, 2018, at 7:18 AM, Mark Struberg <[hidden email]>
> wrote:
> >
> > Oki, I now see what you mean.
> >
> > We actually have 3 source zips now.
> >
> > .src.zip
> > .source-release.zip
> > src.jar
> >
> > That's a mess.
> >
> > There should only be 2:
> > * source-release.zip is the official ASF packages whole build sources.
> This includes the pom, build structure etc.
> > * src.jar is the sources which are automatically downloaded by the IDEs
> for debugging purpose.
> >
> > We have both of them because commons-pool2 is a single-module project.
> > And yes, we need both of them. What we do not need is the src.zip. I
> have no clue yet where this comes from but it shouldn't be here.
> >
> >
> > The good news:
> > By leveraging native GIT we now can simply a.) drop the maven stating
> repo in repository.a.o and b.) drop the release branch and tag from my
> github account and re-roll the release without any weird RC hacks.
> >
> > Will do that,
> > * fix the maven setup
> > * happy to also include the new ticket
> > * re-roll the release this afternoon.
> >
> > LieGrue,
> > strub
> >
> >> Am 16.11.2018 um 23:10 schrieb Romain Manni-Bucau <
> [hidden email]>:
> >>
> >> Le ven. 16 nov. 2018 22:54, Gary Gregory <[hidden email]> a
> écrit :
> >>
> >>> On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau <
> [hidden email]>
> >>> wrote:
> >>>
> >>>> Le ven. 16 nov. 2018 21:23, Gary Gregory <[hidden email]> a
> >>> écrit
> >>>> :
> >>>>
> >>>>> On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg
> >>> <[hidden email]
> >>>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Oki, now the full VOTE text!
> >>>>>>
> >>>>>> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> >>>>>> The release was run with JDK-1.7 to ensure Java7 compatibility.
> >>>>>>
> >>>>>>
> >>>>>> The ASF staging repository is at
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>>>>>
> >>>>>> The source zip is at
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >>>>>> The sha1 of the source-release zip is
> >>>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >>>>>> The sha512 is
> >>>>>>
> >>>>>
> >>>>
> >>>
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>>>>>
> >>>>>
> >>>>> For me:
> >>>>>
> >>>>> $ sha512sum commons-pool2-2.6.1-src.zip
> >>>>>
> >>>>>
> >>>>
> >>>
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> >>>>> *commons-pool2-2.6.1-src.zip
> >>>>>
> >>>>> Which is not what you list above. Please advise.
> >>>>>
> >>>>
> >>>> Src vs source-release?
> >>>>
> >>>
> >>> That's the problem with inventing a new release process... why do we
> have
> >>> BOTH:
> >>>
> >>>
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
> >>> AND
> >>>
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip
> >>>
> >>> And more importantly why are they _different_? Which one will be used
> in
> >>> the dist/release area?
> >>>
> >>
> >>
> >> Looks like pool didnt do its homework and kept the old assembly (src),
> >> source-release comes from the parent and is likely the one to keep IMHO
> >>
> >>
> >>> Gary
> >>>
> >>>
> >>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> Gary
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
> >>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>>>>>
> >>>>>> I've created the release in a GIT manner and pushed the according
> >>>> changes
> >>>>>> to my ASF-linked github repo
> >>>>>>
> >>>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> >>>>>> the sha1 of the commit is
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >>>>>>
> >>>>>> the tag is
> >>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> >>>>>> c910171
> >>>>>> <
> >>>>>
> >>>
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> >>>>>
> >>>>>>
> >>>>>> This will get pushed to the ASF cannonical repo once the VOTE
> >>> succeeds.
> >>>>>>
> >>>>>> Site will be updated once the release has passed.
> >>>>>>
> >>>>>> Please VOTE:
> >>>>>>
> >>>>>> [+1] go ship it!
> >>>>>> [+0] meh, I don't care
> >>>>>> [-1] stop there is a ${showstopper} (that means something
> _important_
> >>>> is
> >>>>>> missing!)
> >>>>>>
> >>>>>>
> >>>>>> Here is my own +1
> >>>>>> checked:
> >>>>>> * signature
> >>>>>> * hashes
> >>>>>> * LICENSE
> >>>>>> * NOTICE
> >>>>>> * rat
> >>>>>> * builds fine with various JDKs
> >>>>>>
> >>>>>>
> >>>>>> LieGrue,
> >>>>>> strub
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> Am 14.11.2018 um 10:13 schrieb Mark Struberg
> >>>> <[hidden email]
> >>>>>>> :
> >>>>>>>
> >>>>>>> PS: I've created the release in a GIT manner and pushed the
> >>> according
> >>>>>> changes to my ASF-linked github repo
> >>>>>>>
> >>>>>>> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> >>>>>>> the sha1 of the commit is
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >>>>>>>
> >>>>>>> the tag is
> >>>>>>> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> >>>>>>> c910171
> >>>>>>>
> >>>>>>> This will get pushed to the ASF cannonical repo once the VOTE
> >>>> succeeds.
> >>>>>>> Yay, this is the way GIT works and before someone not familiar with
> >>>> GIT
> >>>>>> screams that this is not hosted on ASF: This got discussed on the
> >>> board
> >>>>>> level a long time ago (when we did DeltaSpike and CouchDB as the
> very
> >>>>> first
> >>>>>> GIT repos at the ASF) and is perfectly fine as all this is based on
> >>>>>> cryptographically strong steps.
> >>>>>>>
> >>>>>>> LieGrue,
> >>>>>>> strub
> >>>>>>>
> >>>>>>>
> >>>>>>>> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> >>>>> <[hidden email]
> >>>>>>> :
> >>>>>>>>
> >>>>>>>> Hi folks!
> >>>>>>>>
> >>>>>>>> I'm currently preparing the release for commons-pool2-2.6.1
> >>>>>>>>
> >>>>>>>> So far I did
> >>>>>>>>
> >>>>>>>> * fix the missing parts in changes.xml
> >>>>>>>> * generate + copy the RELEASE_NOTES
> >>>>>>>> * run the maven release (after fixing the setup...)
> >>>>>>>>
> >>>>>>>> The ASF staging repository is at
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>>>>>>>
> >>>>>>>> The source zip is at
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >>>>>>>> The sha1 of the source-release zip is
> >>>>>> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >>>>>>>> The sha512 is
> >>>>>>
> >>>>>
> >>>>
> >>>
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>>>>>>>
> >>>>>>>> I added my KEY (struberg at apache.org) to our dist KEYS file
> >>>>>>>> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>>>>>>>
> >>>>>>>> I will now continue with the follow up steps and then call an
> >>>> official
> >>>>>> VOTE.
> >>>>>>>>
> >>>>>>>> Please let me know if something went wrong so far!
> >>>>>>>>
> >>>>>>>> LieGrue,
> >>>>>>>> strub
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>> ---------------------------------------------------------------------
> >>>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>> For additional commands, e-mail: [hidden email]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
123