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 <[email protected]> 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 <[email protected]>:
>>
>> 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 <[email protected]>:
>>>
>>> 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: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
