This release candidate vote passes with the following binding votes:

- Gary Gregory (ggregory)
- Alex Herbert (aherbert)
- Rob Tompkins (chtompki)

Gary

On Mon, Jul 15, 2024 at 5:06 PM Rob Tompkins <chtom...@apache.org> wrote:
>
> +1
>
> Signatures good, site looks good, release notes good, reports are reasonable
>
> Thanks Gary and all,
>
> -Rob
>
> > On Jul 12, 2024, at 12:29 PM, Gary Gregory <ggreg...@apache.org> wrote:
> >
> > We have added one enhancement and updated some dependencies since
> > Apache Commons Codec 1.17.0 was released, so I would like to release
> > Apache Commons Codec 1.17.1.
> >
> > Apache Commons Codec 1.17.1 RC1 is available for review here:
> >    https://dist.apache.org/repos/dist/dev/commons/codec/1.17.1-RC1
> > (svn revision 70271)
> >
> > The Git tag commons-codec-1.17.1-RC1 commit for this RC is
> > 965109705c5236b05011e1c45f47d991abfa521e which you can browse here:
> >    
> > https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=commit;h=965109705c5236b05011e1c45f47d991abfa521e
> > You may checkout this tag using:
> >    git clone https://gitbox.apache.org/repos/asf/commons-codec.git
> > --branch commons-codec-1.17.1-RC1 commons-codec-1.17.1-RC1
> >
> > Maven artifacts are here:
> >    
> > https://repository.apache.org/content/repositories/orgapachecommons-1756/commons-codec/commons-codec/1.17.1/
> >
> > These are the artifacts and their hashes:
> >
> > #Release SHA-512s
> > #Fri Jul 12 16:20:56 UTC 2024
> > commons-codec-1.17.1-bin.tar.gz=6b7f60cc545b7524c8145ea2894983445db216feb06559809606c2fa274ab05cae72e9bd85fa1ae6f6f9997c13f940e18c5d6ac3019acfd77fcbb90f92402b5b
> > commons-codec-1.17.1-bin.zip=2733187cbb65cea05bbd92b09f175c85440db594b5021505d71f580600e9e50a3aeb0d389f8c109ed3227c34ca395a34a764a4f4799fcc86d4ab174829b2aff5
> > commons-codec-1.17.1-bom.json=8990802e9d665e8c151b0650268bbe767a1877349a8ab4b6fc271c19594c4304d6bab8250b13d8f1e67a4e01b49db83d10359c49d0597e3d8aceb0a69f697cd5
> > commons-codec-1.17.1-bom.xml=0fd310815ceb760981120732a3e71d92fe5aff4f36e076a4341618019d2e6540bdfdb2bbb7e2c9e3865791156a26868707c3e3bd6bc576b6212f4264b341d36e
> > commons-codec-1.17.1-javadoc.jar=67ed6f8748842fc81789e96ab6081344950b0986a36b512bfc3502ac696e5142fad6a29d5b27d581dd55e1892c7d99bb478ffa88d25dc0612b067c9a3a2796fc
> > commons-codec-1.17.1-sources.jar=91853458bdc6d6cf9a1f344b30218ca28e9270341346a5431b714007456e8f08be700fd8fb7cc509afda69d996dde20e1f01022c59240428f5b41e3db2cf20c0
> > commons-codec-1.17.1-src.tar.gz=c98456664396d4d9cb794c185a479e6bb4a5055ed1f526a8e358fe3a59409c057dbb16f59c251bb52976995dbca14d8f15857074c9d19fbc7bdfed625a13abf0
> > commons-codec-1.17.1-src.zip=8375246b08c7c7c9f4f8d07f229c7b4dcc2eed8c1e9f2f7d59319a755c4b8f2b81e8ec5b0de995f239246f06e9b8ca373ae1563c385a5bb2a2377249b2662690
> > commons-codec-1.17.1-test-sources.jar=d1fe18cffa43fec7e12f6d9e367872cad2539b1c6e9befd4dbbd7cc097137f780a0d86d0d15e6c921494f22a37077df94ee4c008fe395f76d9041cc8df86fed5
> > commons-codec-1.17.1-tests.jar=52bfb28dad735490444a4f8ff96102013d23d9ecb22236aa0fb30d060113953105f65083eb831d34162b11bcc1de9c89a0a02b78e0582d04789182f8fd559aec
> > commons-codec_commons-codec-1.17.1.spdx.json=402887cb1d559aa75efe3546c1d50e6a8e632339ff0fe66447878cbbd487df822232582d49c5b385e44cfd3adb0d6e06029ae561844f4d0eed1172441e853102
> >
> > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy
> > -P jacoco -P japicmp clean package site deploy' using:
> >
> > openjdk version "17.0.11" 2024-04-16
> > OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> > OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
> >
> > Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
> > Maven home: /usr/local/Cellar/maven/3.9.8/libexec
> > Java version: 17.0.11, vendor: Homebrew, runtime:
> > /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
> >
> > Darwin **** 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> > PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
> >
> > Details of changes since 1.17.0 are in the release notes:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.17.1-RC1/RELEASE-NOTES.txt
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.17.1-RC1/site/changes-report.html
> >
> > Site:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.17.1-RC1/site/index.html
> >    (note some *relative* links are broken and the 1.17.1 directories
> > are not yet created - these will be OK once the site is deployed.)
> >
> > JApiCmp Report (compared to 1.17.0):
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.17.1-RC1/site/japicmp.html
> >
> > RAT Report:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.17.1-RC1/site/rat-report.html
> >
> > KEYS:
> >  https://downloads.apache.org/commons/KEYS
> >
> > Please review the release candidate and vote.
> > This vote will close no sooner than 72 hours from now.
> >
> >  [ ] +1 Release these artifacts
> >  [ ] +0 OK, but...
> >  [ ] -0 OK, but really should fix...
> >  [ ] -1 I oppose this release because...
> >
> > Thank you,
> >
> > Gary Gregory,
> > Release Manager (using key 86fdc7e2a11262cb)
> >
> > The following is intended as a helper and refresher for reviewers.
> >
> > Validating a release candidate
> > ==============================
> >
> > These guidelines are NOT complete.
> >
> > Requirements: Git, Java, Maven.
> >
> > You can validate a release from a release candidate (RC) tag as follows.
> >
> > 1a) Clone and checkout the RC tag
> >
> > git clone https://gitbox.apache.org/repos/asf/commons-codec.git
> > --branch commons-codec-1.17.1-RC1 commons-codec-1.17.1-RC1
> > cd commons-codec-1.17.1-RC1
> >
> > 1b) Download and unpack the source archive from:
> >
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.17.1-RC1/source
> >
> > 2) Check Apache licenses
> >
> > This step is not required if the site includes a RAT report page which
> > you then must check.
> >
> > mvn apache-rat:check
> >
> > 3) Check binary compatibility
> >
> > Older components still use Apache Clirr:
> >
> > This step is not required if the site includes a Clirr report page
> > which you then must check.
> >
> > mvn clirr:check
> >
> > Newer components use JApiCmp with the japicmp Maven Profile:
> >
> > This step is not required if the site includes a JApiCmp report page
> > which you then must check.
> >
> > mvn install -DskipTests -P japicmp japicmp:cmp
> >
> > 4) Build the package
> >
> > mvn -V clean package
> >
> > You can record the Maven and Java version produced by -V in your VOTE reply.
> > To gather OS information from a command line:
> > Windows: ver
> > Linux: uname -a
> >
> > 5) Build the site for a single module project
> >
> > Note: Some plugins require the components to be installed instead of 
> > packaged.
> >
> > mvn site
> > Check the site reports in:
> > - Windows: target\site\index.html
> > - Linux: target/site/index.html
> >
> > -the end-
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

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

Reply via email to