This lazy vote passes with the following votes: +1: Alex Herbert (aherbert) - binding
On Fri, 28 Aug 2026 at 17:38, Alex Herbert <[email protected]> wrote: > My +1. > > On Tue, 25 Aug 2026 at 16:59, Alex Herbert <[email protected]> > wrote: > >> The previous vote e-mail did not register the commit hash for the browse >> URL. This is the correct URL: >> >> The Git tag commons-skin-5.3.0-RC1 commit for this RC is >> 8e1b3b1146c0d5b66fda437eb52123bbc48ad0b7, which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-skin.git;a=commit;h=8e1b3b1146c0d5b66fda437eb52123bbc48ad0b7 >> >> >> >> On Tue, 25 Aug 2026 at 16:38, Alex Herbert <[email protected]> >> wrote: >> >>> We have fixed a few bugs and added enhancements since the release of >>> Apache Commons Skin 5.2.0, so I would like to release Apache Commons Skin >>> 5.3.0. >>> >>> This is a lazy vote as the release does not contain a source archive; >>> this is a dependency of the Commons site build for components. >>> >>> The Git tag commons-skin-5.3.0-RC1 commit for this RC is >>> commons-skin-5.3.0-RC1, which you can browse here: >>> https://github.com/apache/commons-skin/tree/commons-skin-5.3.0-RC1 >>> You may checkout this tag using: >>> git clone https://gitbox.apache.org/repos/asf/commons-skin.git >>> --branch commons-skin-5.3.0-RC1 commons-skin-5.3.0-RC1 >>> >>> Maven artifacts are here: >>> >>> https://repository.apache.org/content/repositories/orgapachecommons-1960/org/apache/commons/commons-skin/5.3.0/ >>> >>> I have tested this with 'mvn' and 'mvn clean install site' using: >>> >>> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) >>> Maven home: /Users/ah403/software/apache-maven-3 >>> Java version: 21.0.9, vendor: Eclipse Adoptium, runtime: >>> /Library/Java/JavaVirtualMachines/temurin-21.jdk/Contents/Home >>> Default locale: en_GB, platform encoding: UTF-8 >>> OS name: "mac os x", version: "26.6", arch: "aarch64", family: "mac" >>> >>> Testing the skin requires building a Commons project site. I tested >>> Numbers and RNG by updating 'src/site/site.xml' to include the following >>> tag above the <body> tag: >>> >>> <skin> >>> <groupId>org.apache.commons</groupId> >>> <artifactId>commons-skin</artifactId> >>> <version>5.3.0</version> >>> </skin> >>> >>> The site HTML can be built and verified using: >>> >>> mvn site:site -DgenerateReports=False >>> open target/site/index.html >>> >>> >>> Details of changes since 5.2.0 are in the release notes: >>> >>> https://dist.apache.org/repos/dist/dev/commons/skin/5.3.0-RC1/RELEASE-NOTES.txt >>> >>> https://dist.apache.org/repos/dist/dev/commons/skin/5.3.0-RC1/site/changes.html >>> >>> Site: >>> >>> https://dist.apache.org/repos/dist/dev/commons/skin/5.3.0-RC1/site/index.html >>> (Note some *relative* links are broken and the 5.3.0 directories are >>> not yet created - these will be OK once the site is deployed.) >>> >>> RAT Report: >>> >>> https://dist.apache.org/repos/dist/dev/commons/skin/5.3.0-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, >>> >>> Alex Herbert, >>> Release Manager (using key BC87A3FD0A54480F0BADBEBD21939FF0CA2A6567) >>> >>> The following is intended as a helper and refresher for reviewers. >>> >>> Validating a release candidate >>> ============================== >>> >>> These guidelines are NOT complete. >>> >>> Requirements: Git, Java, and Maven. >>> >>> You can validate a release from a release candidate (RC) tag as follows. >>> >>> 1a) This release does not contain a source archive. >>> >>> Check out the RC tag from git: >>> >>> git clone https://gitbox.apache.org/repos/asf/commons-skin.git --branch >>> commons-skin-5.3.0-RC1 commons-skin-5.3.0-RC1 >>> cd commons-skin-5.3.0-RC1 >>> >>> 2) Checking the build >>> >>> All components should include a default Maven goal, such that you can >>> run 'mvn' from the command line by itself. >>> >>> 2) Check Apache licenses >>> >>> This step is not required if the site includes a RAT report page, which >>> you then must check. >>> This check should be included in the default Maven build, but you can >>> check it with: >>> >>> mvn apache-rat:check >>> >>> 3) Check binary compatibility >>> >>> This step is not required if the site includes a JApiCmp report page, >>> which you then must check. >>> This check should be included in the default Maven build, but you can >>> check it with: >>> >>> mvn verify -DskipTests -P japicmp japicmp:cmp >>> >>> 4) Build the package >>> >>> This check should be included in the default Maven build, but you can >>> check it with: >>> >>> 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 >>> >>> 4b) Check reproducibility >>> >>> To check that a build is reproducible, run: >>> >>> mvn clean verify artifact:compare -DskipTests -Dreference.repo= >>> https://repository.apache.org/content/repositories/staging/ >>> '-Dbuildinfo.ignore=*/*.spdx.json' >>> >>> Note that this excludes SPDX files from the check. >>> >>> 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- >>> >>>
