So is it safe to add a rel/ tag for the same commit as 2.6 RC3? Will you do
that or shall I?

Gary

On Fri, Sep 20, 2019 at 8:37 AM sebb <[email protected]> wrote:

> On Fri, 20 Sep 2019 at 13:30, Gary Gregory <[email protected]> wrote:
> >
> > Based on the "I’ll publish the release tomorrow." below it looks like he
> > did publish it since it is in the maven repo, on dist, and the site is
> up,
> > but seems to have not completed all the steps.
> > I could not find an announce email for 2.5 either, could you?
>
> April 2016
>
>
> https://lists.apache.org/thread.html/0ad029ed99e3004c2b71b4d19f0e8eaef61fb35a2e39ddeebe4de0f5@1461287297@%3Cannounce.apache.org%3E
> and
>
> http://mail-archives.apache.org/mod_mbox/www-announce/201604.mbox/%3cCALhtWkdb_PO6FpATTwRAvBn7=imer-abvnspoz-c+dtz+_1...@mail.gmail.com%3e
>
> The Subject does not use the standard ANNOUNCE prefix, instead it uses ANN.
>
> > Gary
> >
> > On Fri, Sep 20, 2019 at 7:38 AM sebb <[email protected]> wrote:
> >
> > > It looks like this was not completed: could not find an announce
> > > email, and the tag has not been created (see recent user@ email)
> > >
> > > On Wed, 18 Oct 2017 at 19:26, Benedikt Ritter <[email protected]>
> wrote:
> > > >
> > > > Hello,
> > > >
> > > > > Am 15.10.2017 um 12:22 schrieb Benedikt Ritter <[email protected]
> >:
> > > > >
> > > > > Hello,
> > > > >
> > > > > we have fixed quite a few bugs and added some nice new features
> since
> > > Apache Commons IO 2.5 was released, so I would like to release Apache
> > > Commons IO 2.6 based on RC3.
> > > > >
> > > > > The changes between RC1 and RC2 are:
> > > > > - Worked on the design of the ByteOrderParser class
> > > > > - Fixed IO-546
> > > > > - Fixed IO-553
> > > > >
> > > > > The changes between RC2 and RC3 are:
> > > > > - RC2 contained cobertura instrumented class files (thanks to
> Oliver
> > > Heger to catching this one!)
> > > > >
> > > > > Commons IO 2.6 RC3 is available for review here:
> > > https://dist.apache.org/repos/dist/dev/commons/io/commons-io-2.6-RC3
> (svn
> > > revision 22482)
> > > > >
> > > > > The tag is here:
> > >
> https://git-wip-us.apache.org/repos/asf?p=commons-io.git;a=tag;h=027aebfbfcebad7dfa8603201d4b0ec4859904e8
> > > > >
> > > > > Commit ID the tag points at:
> 2ae025fe5c4a7d2046c53072b0898e37a079fe62
> > > > >
> > > > > Maven Artifacts:
> > >
> https://repository.apache.org/content/repositories/orgapachecommons-1278
> > > > >
> > > > > These are the Maven artifacts and their hashes:
> > > > >
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-test-sources.jar.asc
> > > > > (SHA1: 2a6e16c3f135851b5a907bd50655db9f9bff73a2)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6.pom.asc
> > > > > (SHA1: 177e5b7e423cb9747f5b3cb982af326d24698c64)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-tests.jar.asc
> > > > > (SHA1: 38ccc2062ed998df95910eda9982e5c9623eb8cc)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6.pom
> > > > > (SHA1: 5060835593e5b6ed18c82fc2e782f0a3c30a00b1)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6.jar.asc
> > > > > (SHA1: 7a389502e94871e30f3330634925dff61e4e098a)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-test-sources.jar
> > > > > (SHA1: 75c8aa60dc4623dca0311b38f317ba56596a70ec)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-javadoc.jar
> > > > > (SHA1: 2d1132e48d5d2b698cc27290758dca7905031cfa)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-sources.jar
> > > > > (SHA1: db473f690e219b0566e7f1a8a991bf0e6f08a3c6)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-tests.jar
> > > > > (SHA1: 02a08a358025f15d44b5f0aaaa4410d89b413b97)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6.jar
> > > > > (SHA1: adac173d974250643940c7836caf2726f11a0dc0)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-javadoc.jar.asc
> > > > > (SHA1: 7d78d02ce0d96c511de696b518f1c12133662417)
> > > > > /commons-io/commons-io/2.6/commons-io-2.6-sources.jar.asc
> > > > > (SHA1: 8debf732bc0e5187432f723c01503d75145dbd19)
> > > > >
> > > > > I have tested this with JDK 8 using Maven 3.5.0.
> > > > >
> > > > > Details of changes since 2.5 are in the release notes:
> > > > >
> > >
> https://dist.apache.org/repos/dist/dev/commons/io/commons-io-2.6-RC3/RELEASE-NOTES.txt
> > > > >
> > >
> http://home.apache.org/~britter/commons/commons-io-2.6-RC3/changes-report.html
> > > > >
> > > > > Site:
> > > > > http://home.apache.org/~britter/commons/commons-io-2.6-RC3/
> > > > > (note some *relative* links are broken and the 2.6 directories are
> not
> > > yet created - these will be OK once the site is deployed)
> > > > >
> > > > > Clirr Report (compared to 2.5):
> > > > >
> > >
> http://home.apache.org/~britter/commons/commons-io-2.6-RC3/clirr-report.html
> > > > >
> > > > > RAT Report:
> > > > >
> > >
> http://home.apache.org/~britter/commons/commons-io-2.6-RC3/rat-report.html
> > > > >
> > > > > KEYS:
> > > > > https://www.apache.org/dist/commons/KEYS
> > > > >
> > > > > Please review the release candidate and vote. This vote will close
> no
> > > sooner that 72 hours from now, i.e. sometime after 12:30 CEST (UTC+2)
> > > 18-October 2017
> > > > >
> > > > > [ ] +1 Release these artifacts
> > > > > [ ] +0 OK, but…
> > > > > [ ] -0 OK, but really should fix…
> > > > > [ ] -1 I oppose this release because...
> > > > >
> > > > > Thanks!
> > > >
> > > > This vote passes with the following binding votes:
> > > >
> > > > - Gary Gregory: +1
> > > > - Oliver Heger: +1
> > > > - Benedikt Ritter: +1
> > > >
> > > >  I’ll publish the release tomorrow.
> > > >
> > > > Thank you!
> > > > Benedikt
> > > >
> > > > >
> > > > > Benedikt
> > > > >
> ---------------------------------------------------------------------
> > > > > 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]
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to