commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [RESULT][VOTE] Release Commons Pool 1.6-RC3.
Date Mon, 09 Jan 2012 17:02:35 GMT
On 9 January 2012 15:09, Gary Gregory <garydgregory@gmail.com> wrote:
> On Mon, Jan 9, 2012 at 7:35 AM, sebb <sebbaz@gmail.com> wrote:
>> On 9 January 2012 06:35, Gary Gregory <garydgregory@gmail.com> wrote:
>>> On Sun, Jan 8, 2012 at 10:03 PM, sebb <sebbaz@gmail.com> wrote:
>>>> On 8 January 2012 21:55, Gary Gregory <garydgregory@gmail.com> wrote:
>>>>> Hi All:
>>>>>
>>>>> I am pushing out 1.6 and it's time to click release out of Nexus. I
>>>>> see that there are a ton of files there and the instructions say to
>>>>> remove *-bin* and *-src*. Ok fine, I delete those one at a time, no
>>>>> multiple selection allowed, one annoyance.
>>>>
>>>> Hopefully you copied them first, as they are needed for dist.
>>>
>>> They are already in /x1/www/www.apache.org/content/dist/commons/pool/
>>>
>> OK.
>>
>>>>
>>>>> Then I think to myself, hm, are the instructions complete? So I look
>>>>> at what 1.5.7 files are in Maven Central and I notice that there are
>>>>> no sha1 or md5 files.
>>>>
>>>> AFAIK, Maven does normally contain md5 and sha1 - see for example:
>>>>
>>>> http://repo1.maven.org/maven2/org/apache/commons/commons-jexl/2.1.1/
>>>>
>>>>> So what do I, silly me? I delete them! When I then click release in
>>>>> Nexus, I get:
>>>>>
>>>>> Staging ruleset evaluation on repository 'org.apache.commons-012
>>>>> (u:ggregory, a:24.250.160.61)' has failed.
>>>>>
>>>>> Staging Checksum Validation
>>>>>
>>>>>    -Missing SHA1: '/commons-pool/commons-pool/1.6/commons-pool-1.6.jar.sha1'.
>>>>>    -Missing MD5: '/commons-pool/commons-pool/1.6/commons-pool-1.6.jar.md5.'
>>>>>    -Missing SHA1:
>>>>> '/commons-pool/commons-pool/1.6/commons-pool-1.6-javadoc.jar.sha1'.
>>>>>    -Missing MD5:
>>>>> '/commons-pool/commons-pool/1.6/commons-pool-1.6-javadoc.jar.md5.'
>>>>>    -Missing SHA1: '/commons-pool/commons-pool/1.6/commons-pool-1.6.pom.sha1'.
>>>>>    -Missing MD5: '/commons-pool/commons-pool/1.6/commons-pool-1.6.pom.md5.'
>>>>>    -Missing SHA1:
>>>>> '/commons-pool/commons-pool/1.6/commons-pool-1.6-sources.jar.sha1'.
>>>>>    -Missing MD5:
>>>>> '/commons-pool/commons-pool/1.6/commons-pool-1.6-sources.jar.md5.'
>>>>>
>>>>> !$#$@# I can't believe I shot myself in the foot!
>>>>>
>>>>> I have the sha1 and md5 files on my people.apache.org home dir.
>>>>>
>>>>> Can I copy them to Nexus?
>>>>
>>>> I don't think you can update the staging repo once it is closed.
>>>>
>>>> However, you may be able to create a new one using the existihg files,
>>>> by using the Nexus Staging Upload feature.
>>>> Create a bundle that contains copies of all the Maven files from Nexus
>>>> + the recovered hashes.
>>>> You can try using the Maven Repository plugin, but I had problems with
>>>> that; it may be simpler to create the jar file manually.
>>>>
>>>> Or you can upload each file singly, but that quickly becomes boring...
>>>
>>> Here is what I did: All the files we voted on were copied from Nexus
>>> (before I deleted the sha1's and md5's) with wget to my people.a.o
>>> home dir per the wiki instructions.
>>>
>>> I copied them from my home dir down to my local machine. Then I used
>>> the Nexus Staging Upload feature to upload the POM, and jars. The
>>> files have been uploading for five minutes now which is very long. I'm
>>> going to let it upload while I sleep and check in the AM (EST).
>>>
>>> If that does not work, I'll drop the previous repo and try again. If
>>> that does not work, then I'm stuck with an RC4. Arg.
>>
>> As I already wrote, the vote was on the current staging repo. If you
>> release from a new staging repo, then the vote is invalid.
>>
>> So I think you need to tie the files in the new staging area to the
>> old staging area; you can do this by getting agreement on which sigs
>> were used.
>
> What is the difference b/w a "staging area" and a "staging repo"? The
> staging repo is the dir in Nexus after a deploy, that's clear.

Just a different name for the same thing; I was not being consistent.

> It seems that I cannot update a closed repo, which makes sense, I
> would not expect to be able to do that.
>
> So the best I can do is create a new repo with the same files and
> close, and release it./

Yes.

> Right now, I cannot even do that, the Nexus upload was stuck in a loop
> for 6 hours over night, so I killed that one. I was trying to upload
> the POM with attached atrifacts.

No idea why that should be.

> Now it is looping ("Uploading..." dialog) on uploading a bundle zip I
> created myself which contains the same files we voted on.
>
> So killed that and create a bundle the maven way instead of using
> WinRar: mvn javadoc:jar source:jar repository:bundle-create

But that creates new versions of the jars ...

> Now it is looping uploading that! I'm not lucky today.
>
> This is an abject failure. :( blech.
>
> The cleanest thing is to RC again.

The cleanest would be to re-create the staging area from the previous
files, but that may no longer be possible if you don't have the files.
And anyway, there's no way to tie the original vote to the replaced
files, now that the original staging repo has been dropped.

> Gary
>
>> But this *must* be done before deleting the staging area that was voted on.
>>
>>> Gary
>>>
>>>
>>>>
>>>> Nexus may prevent you from creating a new staging repo until you have
>>>> dropped the old one.
>>>> If so, be very careful not to delete the files till you have secured copies.
>>>>
>>>> The problem arises - how can you prove that the artifacts you release
>>>> are the ones we voted on?
>>>> Unless there is a valid PMC vote, the RM is personally responsible for
>>>> the content of the release.
>>>> That's not a risk I would be willing to take, but YMMV.
>>>>
>>>> It's a pity that you did not include hashes (or sigs) of the files in
>>>> the vote e-mail, as that would be a way to prove that the voted-on
>>>> artifacts were the ones that were re-staged.
>>>>
>>>> One possibility would be to add the .asc files to the vote e-mail, and
>>>> ask the original voters to confirm that these correspond with the .asc
>>>> files they voted on (i.e. the current contents of the Nexus staging
>>>> repo).
>>>>
>>>>> Gary
>>>>>
>>>>> On Sun, Jan 8, 2012 at 12:42 PM, Gary Gregory <garydgregory@gmail.com>
wrote:
>>>>>> This vote passes with 5 +1s from the PMC:
>>>>>>
>>>>>> Simone Tripodi
>>>>>> Oliver Heger
>>>>>> Christian Grobmeier
>>>>>> Jörg Schaible
>>>>>> Gary Gregory
>>>>>>
>>>>>> No other votes were cast.
>>>>>>
>>>>>> Cheers,
>>>>>> Gary
>>>>>>
>>>>>> On Wed, Jan 4, 2012 at 2:20 PM, Gary Gregory <ggregory@apache.org>
wrote:
>>>>>>> Good day to you all:
>>>>>>>
>>>>>>> I have prepared Commons Pool 1.6-RC3.
>>>>>>>
>>>>>>> The only change from RC2 is that the build was run from a clean
SVN checkout
>>>>>>> to avoid issues with using a mixed-revision working copy.
>>>>>>>
>>>>>>> The only changes from 1.5.7 are the additions of generics and
therefore
>>>>>>> requires Java 5.
>>>>>>>
>>>>>>> Tag:
>>>>>>>
>>>>>>> https://svn.apache.org/repos/asf/commons/proper/pool/tags/POOL_1_6_RC3/
>>>>>>>
>>>>>>> Site:
>>>>>>>
>>>>>>> https://people.apache.org/builds/commons/pool/1.6/RC3/
>>>>>>>
>>>>>>> Binaries:
>>>>>>>
>>>>>>> https://repository.apache.org/content/repositories/orgapachecommons-012/
>>>>>>>
>>>>>>> The link above includes checksum files.
>>>>>>>
>>>>>>> [ ] +1 release it
>>>>>>> [ ] +0 almost, please fix:
>>>>>>> [ ] -1 no because:
>>>>>>>
>>>>>>> This VOTE is open for at least 72 hours, until Janurary 7 2011,
15:00 EST.
>>>>>>>
>>>>>>> Changes:
>>>>>>> o [POOL-208] Support Java 1.5 Generics in version 1.x.
>>>>>>>
>>>>>>> Thank you and happy new year,
>>>>>>> Gary
>>>>>>>
>>>>>>> --
>>>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>>>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>>>>>>> Spring Batch in Action: http://bit.ly/bqpbCK
>>>>>>> Blog: http://garygregory.wordpress.com
>>>>>>> Home: http://garygregory.com/
>>>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>>>>>> Spring Batch in Action: http://bit.ly/bqpbCK
>>>>>> Blog: http://garygregory.wordpress.com
>>>>>> Home: http://garygregory.com/
>>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>>>>> Spring Batch in Action: http://bit.ly/bqpbCK
>>>>> Blog: http://garygregory.wordpress.com
>>>>> Home: http://garygregory.com/
>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>>> Spring Batch in Action: http://bit.ly/bqpbCK
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message