My +1 Gary
On Sat, Oct 18, 2025 at 10:36 AM Rob Tompkins <[email protected]> wrote: > > +1 > > > On Oct 18, 2025, at 8:38 AM, Gary Gregory <[email protected]> wrote: > > > > We have a new Oak-based logo since Apache Commons Skin 5.1.0 was > > released, so I would like to release Apache Commons Skin 5.2.0. > > > > Due to the nature of the website skin component, there is no Subversion > > staging. > > > > The Git tag commons-skin-5.2.0-RC1 commit for this RC is > > 4d56b679484a63621b9ac1821dc7900ea1b76872, which you can browse here: > > > > https://gitbox.apache.org/repos/asf?p=commons-skin.git;a=commit;h=4d56b679484a63621b9ac1821dc7900ea1b76872 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-skin.git > > --branch commons-skin-5.2.0-RC1 commons-skin-5.2.0-RC1 > > > > Maven artifacts are here: > > > > https://repository.apache.org/content/repositories/orgapachecommons-1866/org/apache/commons/commons-skin/5.2.0/ > > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > > > If you build the site locally, you will see the old logo instead of > > the new one until the new skin version is pushed in a new > > commons-parent. > > > > openjdk version "21.0.8" 2025-07-15 > > OpenJDK Runtime Environment Homebrew (build 21.0.8) > > OpenJDK 64-Bit Server VM Homebrew (build 21.0.8, mixed mode, sharing) > > > > Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) > > Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec > > Java version: 21.0.8, vendor: Homebrew, runtime: > > /opt/homebrew/Cellar/openjdk@21/21.0.8/libexec/openjdk.jdk/Contents/Home > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "15.7.1", arch: "aarch64", family: "mac" > > > > Darwin ****-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Mon > > Aug 11 21:15:09 PDT 2025; > > root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T6041 arm64 > > > > Docker version 28.4.0, build d8eb465 > > > > > > Details of changes since 5.1.0 are in the release notes: > > > > https://github.com/apache/commons-skin/blob/commons-skin-5.2.0-RC1/RELEASE-NOTES.txt > > > > Site: > > Due to the special nature of the website skin component, there is no > > Subversion staging. > > > > 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, and Maven. > > > > You can validate a release from a release candidate (RC) tag as follows. > > > > 1a) Download and decompress the source archive from: > > > > https://dist.apache.org/repos/dist/dev/commons/skin/5.2.0-RC1/source > > > > 1b) Check out the RC tag from git (optional) > > > > This is optional, as a reviewer must check source distributions as a > > minimum. > > > > git clone https://gitbox.apache.org/repos/asf/commons-skin.git > > --branch commons-skin-5.2.0-RC1 commons-skin-5.2.0-RC1 > > cd commons-skin-5.2.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- > > > > --------------------------------------------------------------------- > > 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]
