Re: [ALL] release instructions warning

[sebb]

On 23 April 2013 02:19, Gary Gregory  wrote:

> To release Codec 1.8, I just tried following
> https://commons.apache.org/releases/prepare.html
>
> In particular:
>
> "Before you close<
> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage>the
> staging repository you must remove the tarballs/zips together with
> their PGP signatures and checksums using the Nexus web interface. While you
> are at it you can also remove the checksums Nexus created for the PGP
> signatures of the remaining artifacts, they are not needed at all."
>
>
[BTW, this does not have to be done before closing; it can be done before
publishing. Not sure why Nexus allows deletion from a closed repo, but it
does]

If a mistake is made, just delete and recreate the staging repo.It's not
that difficult.

Nexus / Maven is not ideal in that it creates hashes for .ASC files, but
having a staging repo is a huge benefit compared with the pre-Nexus
situation.
If you look around Maven Central, you will see a lot of mistaken releases
(e.g. snapshots in the release area). Once released to Maven, it cannot be
unreleased.

I don't want to go back to that time.

So I dutifully deleted .md5 and sha1 files and guess what? I messed it up
> by deleting all MD5 and SHA1 files instead of just this one and that one
> out of the 61 files that are presented in the UI. Frak! So beware, our
> release process sucks rocks and does not do it well, as it has for years.
>

It still takes a bit of care, but I think it's a lot better / safer than it
used to be.

Note: it's possible to prevent the non-Maven artifacts from being uploaded
to Nexus.
It would then be possible to just leave the useless hashes in place
However, this means additional work has to be done to create the
tarballs/zips and their sigs/hashes.

We just need a Maven expert to help fix up the process now that svnpubsub
is in use.



> :(
>
> Gary
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

Re: [ALL] release instructions warning

[Gary Gregory]

On Tue, Apr 23, 2013 at 8:39 AM, sebb  wrote:

> On 23 April 2013 02:19, Gary Gregory  wrote:
>
> > To release Codec 1.8, I just tried following
> > https://commons.apache.org/releases/prepare.html
> >
> > In particular:
> >
> > "Before you close<
> > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> >the
> > staging repository you must remove the tarballs/zips together with
> > their PGP signatures and checksums using the Nexus web interface. While
> you
> > are at it you can also remove the checksums Nexus created for the PGP
> > signatures of the remaining artifacts, they are not needed at all."
> >
> >
> [BTW, this does not have to be done before closing; it can be done before
> publishing. Not sure why Nexus allows deletion from a closed repo, but it
> does]
>
> If a mistake is made, just delete and recreate the staging repo.It's not
> that difficult.
>

OK, will do.

Gary


>
> Nexus / Maven is not ideal in that it creates hashes for .ASC files, but
> having a staging repo is a huge benefit compared with the pre-Nexus
> situation.
> If you look around Maven Central, you will see a lot of mistaken releases
> (e.g. snapshots in the release area). Once released to Maven, it cannot be
> unreleased.
>
> I don't want to go back to that time.
>
> So I dutifully deleted .md5 and sha1 files and guess what? I messed it up
> > by deleting all MD5 and SHA1 files instead of just this one and that one
> > out of the 61 files that are presented in the UI. Frak! So beware, our
> > release process sucks rocks and does not do it well, as it has for years.
> >
>
> It still takes a bit of care, but I think it's a lot better / safer than it
> used to be.
>
> Note: it's possible to prevent the non-Maven artifacts from being uploaded
> to Nexus.
> It would then be possible to just leave the useless hashes in place
> However, this means additional work has to be done to create the
> tarballs/zips and their sigs/hashes.
>
> We just need a Maven expert to help fix up the process now that svnpubsub
> is in use.
>
>
>
> > :(
> >
> > Gary
> >
> > --
> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > Java Persistence with Hibernate, Second Edition<
> > http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition 
> > Spring Batch in Action 
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [ALL] release instructions warning

[Gary Gregory]

On Tue, Apr 23, 2013 at 8:51 AM, Gary Gregory wrote:

> On Tue, Apr 23, 2013 at 8:39 AM, sebb  wrote:
>
>> On 23 April 2013 02:19, Gary Gregory  wrote:
>>
>> > To release Codec 1.8, I just tried following
>> > https://commons.apache.org/releases/prepare.html
>> >
>> > In particular:
>> >
>> > "Before you close<
>> > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
>> >the
>> > staging repository you must remove the tarballs/zips together with
>> > their PGP signatures and checksums using the Nexus web interface. While
>> you
>> > are at it you can also remove the checksums Nexus created for the PGP
>> > signatures of the remaining artifacts, they are not needed at all."
>> >
>> >
>> [BTW, this does not have to be done before closing; it can be done before
>> publishing. Not sure why Nexus allows deletion from a closed repo, but it
>> does]
>>
>> If a mistake is made, just delete and recreate the staging repo.It's not
>> that difficult.
>>
>
> OK, will do.
>

Here:
https://repository.apache.org/content/repositories/orgapachecommons-129/

Gary


>
> Gary
>
>
>>
>> Nexus / Maven is not ideal in that it creates hashes for .ASC files, but
>> having a staging repo is a huge benefit compared with the pre-Nexus
>> situation.
>> If you look around Maven Central, you will see a lot of mistaken releases
>> (e.g. snapshots in the release area). Once released to Maven, it cannot be
>> unreleased.
>>
>> I don't want to go back to that time.
>>
>> So I dutifully deleted .md5 and sha1 files and guess what? I messed it up
>> > by deleting all MD5 and SHA1 files instead of just this one and that one
>> > out of the 61 files that are presented in the UI. Frak! So beware, our
>> > release process sucks rocks and does not do it well, as it has for
>> years.
>> >
>>
>> It still takes a bit of care, but I think it's a lot better / safer than
>> it
>> used to be.
>>
>> Note: it's possible to prevent the non-Maven artifacts from being uploaded
>> to Nexus.
>> It would then be possible to just leave the useless hashes in place
>> However, this means additional work has to be done to create the
>> tarballs/zips and their sigs/hashes.
>>
>> We just need a Maven expert to help fix up the process now that svnpubsub
>> is in use.
>>
>>
>>
>> > :(
>> >
>> > Gary
>> >
>> > --
>> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> > Java Persistence with Hibernate, Second Edition<
>> > http://www.manning.com/bauer3/>
>> > JUnit in Action, Second Edition 
>> > Spring Batch in Action 
>> > Blog: http://garygregory.wordpress.com
>> > Home: http://garygregory.com/
>> > Tweet! http://twitter.com/GaryGregory
>> >
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second 
> Edition
> JUnit in Action, Second Edition 
> Spring Batch in Action 
>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE] Release Commons Codec 1.8-RC4

[Gary Gregory]

For record, I deleted the wrong checksum files, so I had to redo the
staging repo:

https://repository.apache.org/content/repositories/orgapachecommons-129/

Gary


On Mon, Apr 22, 2013 at 4:42 PM, Gary Gregory wrote:

> My +1.
>
> Gary
>
>
> On Fri, Apr 19, 2013 at 12:56 PM, Gary Gregory wrote:
>
>> Hello All:
>>
>> This is a VOTE to release Commons Codec 1.8-RC4.
>>
>> Commons Codec 1.8 requires a minimum of Java 1.6
>>
>> Changes from 1.8-RC3 are:
>>
>> Add pmd.xml to source distribution to build the site.
>>
>> Changes from 1.8-RC2 are:
>>
>> Clarify NOTICE.txt
>>
>> Changes from 1.8-RC1 are:
>>
>> o Set the correct version for the Ant build in default.properties
>> o Fix URLs in NOTICE.txt file and Java source for ASpell.
>>
>> Changes in this version include:
>>
>> New features:
>> o CODEC-168:  Add DigestUtils.updateDigest(MessageDigest, InputStream).
>> Thanks to Daniel Cassidy.
>> o CODEC-167:  Add JUnit to test our decode with pad character in the
>> middle.
>> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
>> Thanks to crice.
>>
>> Fixed Bugs:
>> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
>> arrays on every loop run. Thanks to leo141.
>> o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
>> characters at the end.
>>
>> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM
>> EST.
>>
>> The files:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-121/
>>
>> The tag:
>>
>> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4
>>
>> The site:
>>
>> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/
>>
>> Thank you,
>> Gary Gregory
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second 
>> Edition
>> JUnit in Action, Second Edition 
>> Spring Batch in Action 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second 
> Edition
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE] Release Commons Codec 1.8-RC4

[sebb]

On 23 April 2013 14:04, Gary Gregory  wrote:

> For record, I deleted the wrong checksum files, so I had to redo the
> staging repo:
>
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
>
In that case, I think you need to restart the VOTE.


> Gary
>
>
> On Mon, Apr 22, 2013 at 4:42 PM, Gary Gregory  >wrote:
>
> > My +1.
> >
> > Gary
> >
> >
> > On Fri, Apr 19, 2013 at 12:56 PM, Gary Gregory  >wrote:
> >
> >> Hello All:
> >>
> >> This is a VOTE to release Commons Codec 1.8-RC4.
> >>
> >> Commons Codec 1.8 requires a minimum of Java 1.6
> >>
> >> Changes from 1.8-RC3 are:
> >>
> >> Add pmd.xml to source distribution to build the site.
> >>
> >> Changes from 1.8-RC2 are:
> >>
> >> Clarify NOTICE.txt
> >>
> >> Changes from 1.8-RC1 are:
> >>
> >> o Set the correct version for the Ant build in default.properties
> >> o Fix URLs in NOTICE.txt file and Java source for ASpell.
> >>
> >> Changes in this version include:
> >>
> >> New features:
> >> o CODEC-168:  Add DigestUtils.updateDigest(MessageDigest, InputStream).
> >> Thanks to Daniel Cassidy.
> >> o CODEC-167:  Add JUnit to test our decode with pad character in the
> >> middle.
> >> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm
> encoder.
> >> Thanks to crice.
> >>
> >> Fixed Bugs:
> >> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
> >> arrays on every loop run. Thanks to leo141.
> >> o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
> >> characters at the end.
> >>
> >> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM
> >> EST.
> >>
> >> The files:
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-121/
> >>
> >> The tag:
> >>
> >> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4
> >>
> >> The site:
> >>
> >> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/
> >>
> >> Thank you,
> >> Gary Gregory
> >> --
> >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> >> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> >> JUnit in Action, Second Edition 
> >> Spring Batch in Action 
> >> Blog: http://garygregory.wordpress.com
> >> Home: http://garygregory.com/
> >> Tweet! http://twitter.com/GaryGregory
> >>
> >
> >
> >
> > --
> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition 
> > Spring Batch in Action 
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

[VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[Gary Gregory]

Hello All:

This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)

Commons Codec 1.8 requires a minimum of Java 1.6

Changes from 1.8-RC4 VOTE take 1 are:

NOTHING. I deleted too many checksum files in Nexus before trying to
release the repo, so I created a new staging repo:
https://repository.apache.org/content/repositories/orgapachecommons-129/

Changes from 1.8-RC3 are:

Add pmd.xml to source distribution to build the site.

Changes from 1.8-RC2 are:

Clarify NOTICE.txt

Changes from 1.8-RC1 are:

o Set the correct version for the Ant build in default.properties
o Fix URLs in NOTICE.txt file and Java source for ASpell.

Changes in this version include:

New features:
o CODEC-168:  Add DigestUtils.updateDigest(
MessageDigest, InputStream). Thanks to Daniel Cassidy.
o CODEC-167:  Add JUnit to test our decode with pad character in the middle.
o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
Thanks to crice.

Fixed Bugs:
o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
arrays on every loop run. Thanks to leo141.
o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
characters at the end.

This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM EST.

The files:

https://repository.apache.org/content/repositories/orgapachecommons-129/

The tag:

https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4

The site:

https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/

Thank you,
Gary Gregory

-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[Gary Gregory]

My +1.

Gary


On Tue, Apr 23, 2013 at 9:20 AM, Gary Gregory  wrote:

> Hello All:
>
> This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)
>
> Commons Codec 1.8 requires a minimum of Java 1.6
>
> Changes from 1.8-RC4 VOTE take 1 are:
>
> NOTHING. I deleted too many checksum files in Nexus before trying to
> release the repo, so I created a new staging repo:
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
> Changes from 1.8-RC3 are:
>
> Add pmd.xml to source distribution to build the site.
>
> Changes from 1.8-RC2 are:
>
> Clarify NOTICE.txt
>
> Changes from 1.8-RC1 are:
>
> o Set the correct version for the Ant build in default.properties
> o Fix URLs in NOTICE.txt file and Java source for ASpell.
>
> Changes in this version include:
>
> New features:
> o CODEC-168:  Add DigestUtils.updateDigest(
> MessageDigest, InputStream). Thanks to Daniel Cassidy.
> o CODEC-167:  Add JUnit to test our decode with pad character in the
> middle.
> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
> Thanks to crice.
>
> Fixed Bugs:
> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
> arrays on every loop run. Thanks to leo141.
> o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
> characters at the end.
>
> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM EST.
>
> The files:
>
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
> The tag:
>
> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4
>
> The site:
>
> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/
>
> Thank you,
> Gary Gregory
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second 
> Edition
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [ALL] release instructions warning

[sebb]

Some follow-up: the .ASC hashes can (should) be deleted before the vote
starts.

As to the (non-Maven) tarballs: another approach would be to create them in
Nexus as per usual, but move them (copy/delete) to the svnpubsub staging
area [1] before the vote starts.

It would make the reviewers job slighly harder - one extra URL to download
and check - but there would then be no need to adjust either staging area
after the vote.
So any mistakes would have fewer consequences.

It would hopefully be possible to automate at least some of that process.

[1] https://dist.apache.org/repos/dist/dev/commons/



On 23 April 2013 14:03, Gary Gregory  wrote:

> On Tue, Apr 23, 2013 at 8:51 AM, Gary Gregory  >wrote:
>
> > On Tue, Apr 23, 2013 at 8:39 AM, sebb  wrote:
> >
> >> On 23 April 2013 02:19, Gary Gregory  wrote:
> >>
> >> > To release Codec 1.8, I just tried following
> >> > https://commons.apache.org/releases/prepare.html
> >> >
> >> > In particular:
> >> >
> >> > "Before you close<
> >> > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> >> >the
> >> > staging repository you must remove the tarballs/zips together with
> >> > their PGP signatures and checksums using the Nexus web interface.
> While
> >> you
> >> > are at it you can also remove the checksums Nexus created for the PGP
> >> > signatures of the remaining artifacts, they are not needed at all."
> >> >
> >> >
> >> [BTW, this does not have to be done before closing; it can be done
> before
> >> publishing. Not sure why Nexus allows deletion from a closed repo, but
> it
> >> does]
> >>
> >> If a mistake is made, just delete and recreate the staging repo.It's not
> >> that difficult.
> >>
> >
> > OK, will do.
> >
>
> Here:
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
> Gary
>
>
> >
> > Gary
> >
> >
> >>
> >> Nexus / Maven is not ideal in that it creates hashes for .ASC files, but
> >> having a staging repo is a huge benefit compared with the pre-Nexus
> >> situation.
> >> If you look around Maven Central, you will see a lot of mistaken
> releases
> >> (e.g. snapshots in the release area). Once released to Maven, it cannot
> be
> >> unreleased.
> >>
> >> I don't want to go back to that time.
> >>
> >> So I dutifully deleted .md5 and sha1 files and guess what? I messed it
> up
> >> > by deleting all MD5 and SHA1 files instead of just this one and that
> one
> >> > out of the 61 files that are presented in the UI. Frak! So beware, our
> >> > release process sucks rocks and does not do it well, as it has for
> >> years.
> >> >
> >>
> >> It still takes a bit of care, but I think it's a lot better / safer than
> >> it
> >> used to be.
> >>
> >> Note: it's possible to prevent the non-Maven artifacts from being
> uploaded
> >> to Nexus.
> >> It would then be possible to just leave the useless hashes in place
> >> However, this means additional work has to be done to create the
> >> tarballs/zips and their sigs/hashes.
> >>
> >> We just need a Maven expert to help fix up the process now that
> svnpubsub
> >> is in use.
> >>
> >>
> >>
> >> > :(
> >> >
> >> > Gary
> >> >
> >> > --
> >> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> >> > Java Persistence with Hibernate, Second Edition<
> >> > http://www.manning.com/bauer3/>
> >> > JUnit in Action, Second Edition 
> >> > Spring Batch in Action 
> >> > Blog: http://garygregory.wordpress.com
> >> > Home: http://garygregory.com/
> >> > Tweet! http://twitter.com/GaryGregory
> >> >
> >>
> >
> >
> >
> > --
> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition 
> > Spring Batch in Action 
> >
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

Re: [ALL] release instructions warning

[Stefan Bodewig]

On 2013-04-23, sebb wrote:

> As to the (non-Maven) tarballs: another approach would be to create them in
> Nexus as per usual, but move them (copy/delete) to the svnpubsub staging
> area [1] before the vote starts.

> It would make the reviewers job slighly harder - one extra URL to download
> and check - but there would then be no need to adjust either staging area
> after the vote.
> So any mistakes would have fewer consequences.

This is exactly what

suggests :-)

Stefan

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

Re: [ALL] release instructions warning

[sebb]

On 23 April 2013 15:39, Stefan Bodewig  wrote:

> On 2013-04-23, sebb wrote:
>
> > As to the (non-Maven) tarballs: another approach would be to create them
> in
> > Nexus as per usual, but move them (copy/delete) to the svnpubsub staging
> > area [1] before the vote starts.
>
> > It would make the reviewers job slighly harder - one extra URL to
> download
> > and check - but there would then be no need to adjust either staging area
> > after the vote.
> > So any mistakes would have fewer consequences.
>
> This is exactly what
> <
> https://commons.apache.org/releases/prepare.html#Create_the_Release_Candidate
> >
> suggests :-)
>
>
Yes, I see.

I think we need a link from that document to the next stage - publishing
the release.
I'll see about adding that later.

It might also be useful to have a section on how to respin a release vote
if it fails - what needs to be deleted and when etc.

As to the following comment:

"*If anybody knows how we can avoid uploading the distributions, please
lend a hand. The manual step is not only annoying, uploading the files also
wastes time and bandwidth."*

Yes, the manual stages are annoying, but at least the process generates all
the required files, even if they are not all uploaded to the correct place.
It's easy enough to avoid uploading the tarballs - just detach them from
the relevant Maven phase - but then Maven does not create the hashes or the
sigs.

So there are some possibilities:
- stick with the full Nexus upload, and find a way to automate the move of
the files from Nexus to dist/dev staging
- exclude the tarballs from Nexus, and update the build procedures to
create the sigs and hashes; also automate upload to dist/dev staging
- have Nexus publish the tarballs and Maven artifacts to the correct
places. I raised a JIRA [1] about this, but unfortunately it got nowhere.

[1] https://issues.apache.org/jira/browse/INFRA-4144

Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[Gary Gregory]

This VOTE is open for at least 72 hours until April 26 2013 at 1:00 PM EST.

Gary


On Tue, Apr 23, 2013 at 9:20 AM, Gary Gregory  wrote:

> Hello All:
>
> This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)
>
> Commons Codec 1.8 requires a minimum of Java 1.6
>
> Changes from 1.8-RC4 VOTE take 1 are:
>
> NOTHING. I deleted too many checksum files in Nexus before trying to
> release the repo, so I created a new staging repo:
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
> Changes from 1.8-RC3 are:
>
> Add pmd.xml to source distribution to build the site.
>
> Changes from 1.8-RC2 are:
>
> Clarify NOTICE.txt
>
> Changes from 1.8-RC1 are:
>
> o Set the correct version for the Ant build in default.properties
> o Fix URLs in NOTICE.txt file and Java source for ASpell.
>
> Changes in this version include:
>
> New features:
> o CODEC-168:  Add DigestUtils.updateDigest(
> MessageDigest, InputStream). Thanks to Daniel Cassidy.
> o CODEC-167:  Add JUnit to test our decode with pad character in the
> middle.
> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
> Thanks to crice.
>
> Fixed Bugs:
> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
> arrays on every loop run. Thanks to leo141.
> o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
> characters at the end.
>
> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM EST.
>
> The files:
>
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
> The tag:
>
> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4
>
> The site:
>
> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/
>
> Thank you,
> Gary Gregory
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second 
> Edition
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Staging site?

[Henri Yandell]

Looking at the site building docs, I could see how to modify the site
(install a CMS plugin or just modify SVN and test locally, I went with the
latter). My commit was then built by the buildbot.

Where is the staging site to look at the buildbot output so I can then be
happy pressing Publish? I couldn't see anything in the docs or the buildbot
that seemed to link to such a thing.

Hen

Re: Staging site?

[sebb]

On 23 April 2013 19:25, Henri Yandell  wrote:

> Looking at the site building docs, I could see how to modify the site
> (install a CMS plugin or just modify SVN and test locally, I went with the
> latter). My commit was then built by the buildbot.
>
> Where is the staging site to look at the buildbot output so I can then be
> happy pressing Publish? I couldn't see anything in the docs or the buildbot
> that seemed to link to such a thing.
>
>
If you use the CMS bookmarklet (it's not a plugin) it's one of the links
shown at the top of the page when you commit.
The link is to a protected private directory - e.g. [1] however that
redirects to a shared directory [2]

The ASF CMS docs could be updated with this info somewhere suitable.

[1]
https://cms.apache.org/commons/wc/edit/sebb-{ramdomtag}/trunk/content/xdoc/releases/prepare.xml?action=staged
[2] http://commons.staging.apache.org/releases/prepare.html

Hen
>

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[Oliver Heger]

Hi Gary,

I am very sorry that this happened to you. When I did my last release, I 
was pretty nervous when doing this manual deletion step. It would really 
be cool if this somehow could be automated.


Regarding the vote: I am not sure what exactly I have to check. This 
time the staging repository does not seem to contain the distribution 
archives. Is this intended?


Oliver

Am 23.04.2013 15:20, schrieb Gary Gregory:

Hello All:

This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)

Commons Codec 1.8 requires a minimum of Java 1.6

Changes from 1.8-RC4 VOTE take 1 are:

NOTHING. I deleted too many checksum files in Nexus before trying to
release the repo, so I created a new staging repo:
https://repository.apache.org/content/repositories/orgapachecommons-129/

Changes from 1.8-RC3 are:

Add pmd.xml to source distribution to build the site.

Changes from 1.8-RC2 are:

Clarify NOTICE.txt

Changes from 1.8-RC1 are:

o Set the correct version for the Ant build in default.properties
o Fix URLs in NOTICE.txt file and Java source for ASpell.

Changes in this version include:

New features:
o CODEC-168:  Add DigestUtils.updateDigest(
MessageDigest, InputStream). Thanks to Daniel Cassidy.
o CODEC-167:  Add JUnit to test our decode with pad character in the middle.
o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
Thanks to crice.

Fixed Bugs:
o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
arrays on every loop run. Thanks to leo141.
o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
characters at the end.

This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM EST.

The files:

https://repository.apache.org/content/repositories/orgapachecommons-129/

The tag:

https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4

The site:

https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/

Thank you,
Gary Gregory




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

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[Gary Gregory]

On Tue, Apr 23, 2013 at 3:51 PM, Oliver Heger
wrote:

> Hi Gary,
>
> I am very sorry that this happened to you. When I did my last release, I
> was pretty nervous when doing this manual deletion step. It would really be
> cool if this somehow could be automated.
>
> Regarding the vote: I am not sure what exactly I have to check. This time
> the staging repository does not seem to contain the distribution archives.
> Is this intended?
>

Yes and no.

Yes, I deleted them on purpose as I was following Sebb's suggestion to
re-spin a stagging repo. What I did not understand, I think, is that he
must have meant to upload the missing files to the /existing/ repository.

Instead, I dropped the repo and created another one, from the same local
build as the previous repo.

Then Sebb, said, nope, new repo = new VOTE. So there we are.

And to top it all off, I now realize I need to respin another repo, so that
folks can download the -bin and -src.

I am beyond disgusted the whole process and its ~20 steps just to get to a
VOTE, and the additional crap we have to deal with beyond that.

:(

Gary


>
> Oliver
>
> Am 23.04.2013 15:20, schrieb Gary Gregory:
>
>  Hello All:
>>
>> This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)
>>
>> Commons Codec 1.8 requires a minimum of Java 1.6
>>
>> Changes from 1.8-RC4 VOTE take 1 are:
>>
>> NOTHING. I deleted too many checksum files in Nexus before trying to
>> release the repo, so I created a new staging repo:
>> https://repository.apache.org/**content/repositories/**
>> orgapachecommons-129/
>>
>> Changes from 1.8-RC3 are:
>>
>> Add pmd.xml to source distribution to build the site.
>>
>> Changes from 1.8-RC2 are:
>>
>> Clarify NOTICE.txt
>>
>> Changes from 1.8-RC1 are:
>>
>> o Set the correct version for the Ant build in default.properties
>> o Fix URLs in NOTICE.txt file and Java source for ASpell.
>>
>> Changes in this version include:
>>
>> New features:
>> o CODEC-168:  Add DigestUtils.updateDigest(
>> MessageDigest, InputStream). Thanks to Daniel Cassidy.
>> o CODEC-167:  Add JUnit to test our decode with pad character in the
>> middle.
>> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
>> Thanks to crice.
>>
>> Fixed Bugs:
>> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
>> arrays on every loop run. Thanks to leo141.
>> o CODEC-160:  Base64.**encodeBase64URLSafeString doesn't add padding
>> characters at the end.
>>
>> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM
>> EST.
>>
>> The files:
>>
>> https://repository.apache.org/**content/repositories/**
>> orgapachecommons-129/
>>
>> The tag:
>>
>> https://svn.apache.org/repos/**asf/commons/proper/codec/tags/**1.8-RC4
>>
>> The site:
>>
>> https://people.apache.org/~**ggregory/commons-codec/1.8-**RC4/site/
>>
>> Thank you,
>> Gary Gregory
>>
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@commons.**apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

[CANCEL][VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[Gary Gregory]

Canceled as the Nexus staging repo is missing -bin and -src files.

Gary


On Tue, Apr 23, 2013 at 9:20 AM, Gary Gregory  wrote:

> Hello All:
>
> This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)
>
> Commons Codec 1.8 requires a minimum of Java 1.6
>
> Changes from 1.8-RC4 VOTE take 1 are:
>
> NOTHING. I deleted too many checksum files in Nexus before trying to
> release the repo, so I created a new staging repo:
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
> Changes from 1.8-RC3 are:
>
> Add pmd.xml to source distribution to build the site.
>
> Changes from 1.8-RC2 are:
>
> Clarify NOTICE.txt
>
> Changes from 1.8-RC1 are:
>
> o Set the correct version for the Ant build in default.properties
> o Fix URLs in NOTICE.txt file and Java source for ASpell.
>
> Changes in this version include:
>
> New features:
> o CODEC-168:  Add DigestUtils.updateDigest(
> MessageDigest, InputStream). Thanks to Daniel Cassidy.
> o CODEC-167:  Add JUnit to test our decode with pad character in the
> middle.
> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
> Thanks to crice.
>
> Fixed Bugs:
> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
> arrays on every loop run. Thanks to leo141.
> o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
> characters at the end.
>
> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM EST.
>
> The files:
>
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
> The tag:
>
> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4
>
> The site:
>
> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/
>
> Thank you,
> Gary Gregory
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second 
> Edition
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

[VOTE] Release Commons Codec 1.8-RC4 [Take 3]

[Gary Gregory]

Hello All:

This is a VOTE to release Commons Codec 1.8-RC4 (yes, sigh, /again/)

Commons Codec 1.8 requires a minimum of Java 1.6

Changes from 1.8-RC4 VOTE take 2 are:

NOTHING. In Nexus, I deleted the bin and src archive by mistake.

Changes from 1.8-RC4 VOTE take 1 are:

NOTHING. In Nexus, I deleted too many checksum files before trying to
release the repo, so I created a new staging repo:
https://repository.apache.org/content/repositories/orgapachecommons-129/

Changes from 1.8-RC3 are:

Add pmd.xml to source distribution to build the site.

Changes from 1.8-RC2 are:

Clarify NOTICE.txt

Changes from 1.8-RC1 are:

o Set the correct version for the Ant build in default.properties
o Fix URLs in NOTICE.txt file and Java source for ASpell.

Changes in this version include:

New features:
o CODEC-168:  Add DigestUtils.updateDigest(
MessageDigest, InputStream). Thanks to Daniel Cassidy.
o CODEC-167:  Add JUnit to test our decode with pad character in the middle.
o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
Thanks to crice.

Fixed Bugs:
o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
arrays on every loop run. Thanks to leo141.
o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
characters at the end.

This VOTE is open for at least 72 hours until April 26 2013 at 5:00 PM EST.

The files:

https://repository.apache.org/content/repositories/orgapachecommons-130/

The tag:

https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4

The site:

https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/

Thank you,
Gary Gregory

-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[sebb]

On 23 April 2013 21:02, Gary Gregory  wrote:

> On Tue, Apr 23, 2013 at 3:51 PM, Oliver Heger
> wrote:
>
> > Hi Gary,
> >
> > I am very sorry that this happened to you. When I did my last release, I
> > was pretty nervous when doing this manual deletion step. It would really
> be
> > cool if this somehow could be automated.
> >
> > Regarding the vote: I am not sure what exactly I have to check. This time
> > the staging repository does not seem to contain the distribution
> archives.
> > Is this intended?
> >
>
> Yes and no.
>
> Yes, I deleted them on purpose as I was following Sebb's suggestion to
> re-spin a stagging repo. What I did not understand, I think, is that he
> must have meant to upload the missing files to the /existing/ repository.
>
>
No, I did mean to upload the files again.
However that was intended in the context of how to fix a  damaged staging
repo before the vote.
Sorry, I should have made that clear.

I'm not sure it's possible to upload files to a closed staging repo - you
can delete files, but not add them AFAIK.

I don't know if Nexus allows the staging repo to be published if any of the
hashes are missing, but even if it does, Maven downloads may well complain
if the hashes are missing, and repairing that may be tricky - Maven Central
has its own rules about such things.

Instead, I dropped the repo and created another one, from the same local
> build as the previous repo.
>
> Then Sebb, said, nope, new repo = new VOTE. So there we are.
>

Yes, once the repo has been changed, it clearly needs a new vote; we can
only release source that has been voted on.


> And to top it all off, I now realize I need to respin another repo, so that
> folks can download the -bin and -src.
>
> I am beyond disgusted the whole process and its ~20 steps just to get to a
> VOTE, and the additional crap we have to deal with beyond that.
>
>
The tarballs don't have to be in the Nexus staging repo, but they do have
to be voted on.
The release preparation doc suggests moving them from the staging repo to
the dist/dev SVN repo.
The URL for it can then be included in the RC vote.

:(
>
> Gary
>
>
> >
> > Oliver
> >
> > Am 23.04.2013 15:20, schrieb Gary Gregory:
> >
> >  Hello All:
> >>
> >> This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)
> >>
> >> Commons Codec 1.8 requires a minimum of Java 1.6
> >>
> >> Changes from 1.8-RC4 VOTE take 1 are:
> >>
> >> NOTHING. I deleted too many checksum files in Nexus before trying to
> >> release the repo, so I created a new staging repo:
> >> https://repository.apache.org/**content/repositories/**
> >> orgapachecommons-129/<
> https://repository.apache.org/content/repositories/orgapachecommons-129/>
> >>
> >> Changes from 1.8-RC3 are:
> >>
> >> Add pmd.xml to source distribution to build the site.
> >>
> >> Changes from 1.8-RC2 are:
> >>
> >> Clarify NOTICE.txt
> >>
> >> Changes from 1.8-RC1 are:
> >>
> >> o Set the correct version for the Ant build in default.properties
> >> o Fix URLs in NOTICE.txt file and Java source for ASpell.
> >>
> >> Changes in this version include:
> >>
> >> New features:
> >> o CODEC-168:  Add DigestUtils.updateDigest(
> >> MessageDigest, InputStream). Thanks to Daniel Cassidy.
> >> o CODEC-167:  Add JUnit to test our decode with pad character in the
> >> middle.
> >> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm
> encoder.
> >> Thanks to crice.
> >>
> >> Fixed Bugs:
> >> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
> >> arrays on every loop run. Thanks to leo141.
> >> o CODEC-160:  Base64.**encodeBase64URLSafeString doesn't add padding
> >> characters at the end.
> >>
> >> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM
> >> EST.
> >>
> >> The files:
> >>
> >> https://repository.apache.org/**content/repositories/**
> >> orgapachecommons-129/<
> https://repository.apache.org/content/repositories/orgapachecommons-129/>
> >>
> >> The tag:
> >>
> >> https://svn.apache.org/repos/**asf/commons/proper/codec/tags/**1.8-RC4<
> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4>
> >>
> >> The site:
> >>
> >> https://people.apache.org/~**ggregory/commons-codec/1.8-**RC4/site/<
> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/>
> >>
> >> Thank you,
> >> Gary Gregory
> >>
> >>
> >
> > --**--**-
> > To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<
> dev-unsubscr...@commons.apache.org>
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 3]

[sebb]

On 23 April 2013 21:52, Gary Gregory  wrote:

> Hello All:
>
> This is a VOTE to release Commons Codec 1.8-RC4 (yes, sigh, /again/)
>
> Commons Codec 1.8 requires a minimum of Java 1.6
>
> Changes from 1.8-RC4 VOTE take 2 are:
>
> NOTHING. In Nexus, I deleted the bin and src archive by mistake.
>
> Changes from 1.8-RC4 VOTE take 1 are:
>
> NOTHING. In Nexus, I deleted too many checksum files before trying to
> release the repo, so I created a new staging repo:
> https://repository.apache.org/content/repositories/orgapachecommons-129/
>
>
I think you mean:
https://repository.apache.org/content/repositories/orgapachecommons-130/


> Changes from 1.8-RC3 are:
>
> Add pmd.xml to source distribution to build the site.
>
> Changes from 1.8-RC2 are:
>
> Clarify NOTICE.txt
>
> Changes from 1.8-RC1 are:
>
> o Set the correct version for the Ant build in default.properties
> o Fix URLs in NOTICE.txt file and Java source for ASpell.
>
> Changes in this version include:
>
> New features:
> o CODEC-168:  Add DigestUtils.updateDigest(
> MessageDigest, InputStream). Thanks to Daniel Cassidy.
> o CODEC-167:  Add JUnit to test our decode with pad character in the
> middle.
> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
> Thanks to crice.
>
> Fixed Bugs:
> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
> arrays on every loop run. Thanks to leo141.
> o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
> characters at the end.
>
> This VOTE is open for at least 72 hours until April 26 2013 at 5:00 PM EST.
>
> The files:
>
> https://repository.apache.org/content/repositories/orgapachecommons-130/
>
> The tag:
>
> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4
>
> The site:
>
> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/
>
> Thank you,
> Gary Gregory
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 3]

[Gary Gregory]

On Apr 23, 2013, at 16:54, sebb  wrote:

> On 23 April 2013 21:52, Gary Gregory  wrote:
>
>> Hello All:
>>
>> This is a VOTE to release Commons Codec 1.8-RC4 (yes, sigh, /again/)
>>
>> Commons Codec 1.8 requires a minimum of Java 1.6
>>
>> Changes from 1.8-RC4 VOTE take 2 are:
>>
>> NOTHING. In Nexus, I deleted the bin and src archive by mistake.
>>
>> Changes from 1.8-RC4 VOTE take 1 are:
>>
>> NOTHING. In Nexus, I deleted too many checksum files before trying to
>> release the repo, so I created a new staging repo:
>> https://repository.apache.org/content/repositories/orgapachecommons-129/
> I think you mean:
> https://repository.apache.org/content/repositories/orgapachecommons-130/

Yes, thank you.

Gary

>
>
>> Changes from 1.8-RC3 are:
>>
>> Add pmd.xml to source distribution to build the site.
>>
>> Changes from 1.8-RC2 are:
>>
>> Clarify NOTICE.txt
>>
>> Changes from 1.8-RC1 are:
>>
>> o Set the correct version for the Ant build in default.properties
>> o Fix URLs in NOTICE.txt file and Java source for ASpell.
>>
>> Changes in this version include:
>>
>> New features:
>> o CODEC-168:  Add DigestUtils.updateDigest(
>> MessageDigest, InputStream). Thanks to Daniel Cassidy.
>> o CODEC-167:  Add JUnit to test our decode with pad character in the
>> middle.
>> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm encoder.
>> Thanks to crice.
>>
>> Fixed Bugs:
>> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
>> arrays on every loop run. Thanks to leo141.
>> o CODEC-160:  Base64.encodeBase64URLSafeString doesn't add padding
>> characters at the end.
>>
>> This VOTE is open for at least 72 hours until April 26 2013 at 5:00 PM EST.
>>
>> The files:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-130/
>>
>> The tag:
>>
>> https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4
>>
>> The site:
>>
>> https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/
>>
>> Thank you,
>> Gary Gregory
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition<
>> http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition 
>> Spring Batch in Action 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>

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

[beans] Documentation unavailable

[Paul Benedict]

FYI, the website no longer hosts the API and user guide. The links are
broken.

Paul

Re: [VOTE] Release Commons Codec 1.8-RC4 [Take 2]

[Gary Gregory]

On Tue, Apr 23, 2013 at 4:52 PM, sebb  wrote:

> On 23 April 2013 21:02, Gary Gregory  wrote:
>
> > On Tue, Apr 23, 2013 at 3:51 PM, Oliver Heger
> > wrote:
> >
> > > Hi Gary,
> > >
> > > I am very sorry that this happened to you. When I did my last release,
> I
> > > was pretty nervous when doing this manual deletion step. It would
> really
> > be
> > > cool if this somehow could be automated.
> > >
> > > Regarding the vote: I am not sure what exactly I have to check. This
> time
> > > the staging repository does not seem to contain the distribution
> > archives.
> > > Is this intended?
> > >
> >
> > Yes and no.
> >
> > Yes, I deleted them on purpose as I was following Sebb's suggestion to
> > re-spin a stagging repo. What I did not understand, I think, is that he
> > must have meant to upload the missing files to the /existing/ repository.
> >
> >
> No, I did mean to upload the files again.
> However that was intended in the context of how to fix a  damaged staging
> repo before the vote.
> Sorry, I should have made that clear.
>
> I'm not sure it's possible to upload files to a closed staging repo - you
> can delete files, but not add them AFAIK.
>
> I don't know if Nexus allows the staging repo to be published if any of the
> hashes are missing, but even if it does, Maven downloads may well complain
> if the hashes are missing, and repairing that may be tricky - Maven Central
> has its own rules about such things.
>

That's the complaint I got from Nexus: Missing MD5 and SHA1 hashes.

Gary


>
> Instead, I dropped the repo and created another one, from the same local
> > build as the previous repo.
> >
> > Then Sebb, said, nope, new repo = new VOTE. So there we are.
> >
>
> Yes, once the repo has been changed, it clearly needs a new vote; we can
> only release source that has been voted on.
>
>
> > And to top it all off, I now realize I need to respin another repo, so
> that
> > folks can download the -bin and -src.
> >
> > I am beyond disgusted the whole process and its ~20 steps just to get to
> a
> > VOTE, and the additional crap we have to deal with beyond that.
> >
> >
> The tarballs don't have to be in the Nexus staging repo, but they do have
> to be voted on.
> The release preparation doc suggests moving them from the staging repo to
> the dist/dev SVN repo.
> The URL for it can then be included in the RC vote.
>
> :(
> >
> > Gary
> >
> >
> > >
> > > Oliver
> > >
> > > Am 23.04.2013 15:20, schrieb Gary Gregory:
> > >
> > >  Hello All:
> > >>
> > >> This is a VOTE to release Commons Codec 1.8-RC4 (yes, /again/)
> > >>
> > >> Commons Codec 1.8 requires a minimum of Java 1.6
> > >>
> > >> Changes from 1.8-RC4 VOTE take 1 are:
> > >>
> > >> NOTHING. I deleted too many checksum files in Nexus before trying to
> > >> release the repo, so I created a new staging repo:
> > >> https://repository.apache.org/**content/repositories/**
> > >> orgapachecommons-129/<
> > https://repository.apache.org/content/repositories/orgapachecommons-129/
> >
> > >>
> > >> Changes from 1.8-RC3 are:
> > >>
> > >> Add pmd.xml to source distribution to build the site.
> > >>
> > >> Changes from 1.8-RC2 are:
> > >>
> > >> Clarify NOTICE.txt
> > >>
> > >> Changes from 1.8-RC1 are:
> > >>
> > >> o Set the correct version for the Ant build in default.properties
> > >> o Fix URLs in NOTICE.txt file and Java source for ASpell.
> > >>
> > >> Changes in this version include:
> > >>
> > >> New features:
> > >> o CODEC-168:  Add DigestUtils.updateDigest(
> > >> MessageDigest, InputStream). Thanks to Daniel Cassidy.
> > >> o CODEC-167:  Add JUnit to test our decode with pad character in the
> > >> middle.
> > >> o CODEC-161:  Add Match Rating Approach (MRA) phonetic algorithm
> > encoder.
> > >> Thanks to crice.
> > >>
> > >> Fixed Bugs:
> > >> o CODEC-163:  ColognePhonetic encoder unnecessarily creates many char
> > >> arrays on every loop run. Thanks to leo141.
> > >> o CODEC-160:  Base64.**encodeBase64URLSafeString doesn't add padding
> > >> characters at the end.
> > >>
> > >> This VOTE is open for at least 72 hours until April 22 2013 at 1:00 PM
> > >> EST.
> > >>
> > >> The files:
> > >>
> > >> https://repository.apache.org/**content/repositories/**
> > >> orgapachecommons-129/<
> > https://repository.apache.org/content/repositories/orgapachecommons-129/
> >
> > >>
> > >> The tag:
> > >>
> > >>
> https://svn.apache.org/repos/**asf/commons/proper/codec/tags/**1.8-RC4<
> > https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4>
> > >>
> > >> The site:
> > >>
> > >> https://people.apache.org/~**ggregory/commons-codec/1.8-**RC4/site/<
> > https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/>
> > >>
> > >> Thank you,
> > >> Gary Gregory
> > >>
> > >>
> > >
> > >
> --**--**-
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<
> > dev-unsubscr...@commons.apache.org>
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > 

[beans] Documentation links are broken

[Paul Benedict]

FYI, the site points to non-existent API and user guide. The links are
broken on both the LHS navigation and the main content.

Paul

Re: [beans] Documentation links are broken

[sebb]

On 23 April 2013 22:53, Paul Benedict  wrote:

> FYI, the site points to non-existent API and user guide. The links are
> broken on both the LHS navigation and the main content.
>
>
Beans does not exist. I assume you meant Beanutils?


> Paul
>

Re: [beansutils] Documentation links are broken

[Paul Benedict]

yes :-)


On Tue, Apr 23, 2013 at 4:58 PM, sebb  wrote:

> On 23 April 2013 22:53, Paul Benedict  wrote:
>
> > FYI, the site points to non-existent API and user guide. The links are
> > broken on both the LHS navigation and the main content.
> >
> >
> Beans does not exist. I assume you meant Beanutils?
>
>
> > Paul
> >
>

Re: [IO] CharSequenceInputStream - strange code

[sebb]

On 22 April 2013 18:10, Gary Gregory  wrote:

> I looked at this a couple of month ago and found it equally confusing.
>
>
I think I've finally sorted out the issues...

skip() now skips the byte buffer (i.e. the same buffer as read) and AFAICT
mark/reset is working OK.
Also available() does now include the encoded bytes in the count
(previously the count was 0 if the last chunk of input had been encoded)

There are still some @Ignored tests - these relate to multi-byte charsets.
Not sure if the tests can be fixed (or indeed if they would serve any
additional purpose).

Gary
>
>
> On Mon, Apr 22, 2013 at 12:14 PM, sebb  wrote:
>
> > I'm trying to fix IO-356, and having problems.
> >
> > I think this is because the code is a bit confused.
> >
> > The read() method reads bytes from the encoded byte buffer.
> >
> > However skip(int) skips the underlying CharBuf, and available() checks
> the
> > CharBuf
> >
> > I would expect read() and skip(1) to have the same effect (except
> possibly
> > at EOF).
> > However that is not the case currently.
> >
> > Also I would expect available() to relate to the number of characters
> > available for read().
> >
> > The class extends InputStream, and I would expect all the
> > overridden/implemented methods to relate to the InputStream, not the
> source
> > Charset.
> >
> > Or am I missing something here?
> >
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

Re: Staging site?

[Henri Yandell]

So if you're using the SVN approach, you check locally, then commit and go
hit publish on the CMS?

Hen

On Tue, Apr 23, 2013 at 11:50 AM, sebb  wrote:

> On 23 April 2013 19:25, Henri Yandell  wrote:
>
> > Looking at the site building docs, I could see how to modify the site
> > (install a CMS plugin or just modify SVN and test locally, I went with
> the
> > latter). My commit was then built by the buildbot.
> >
> > Where is the staging site to look at the buildbot output so I can then be
> > happy pressing Publish? I couldn't see anything in the docs or the
> buildbot
> > that seemed to link to such a thing.
> >
> >
> If you use the CMS bookmarklet (it's not a plugin) it's one of the links
> shown at the top of the page when you commit.
> The link is to a protected private directory - e.g. [1] however that
> redirects to a shared directory [2]
>
> The ASF CMS docs could be updated with this info somewhere suitable.
>
> [1]
>
> https://cms.apache.org/commons/wc/edit/sebb-{ramdomtag}/trunk/content/xdoc/releases/prepare.xml?action=staged
> [2] http://commons.staging.apache.org/releases/prepare.html
>
> Hen
> >
>