They are independent of each other, it is nicer for a component to use the lastest parent pom but it is usually not a requirement.
I will work on releasing Compress over the next week or so. Gary On Fri, Apr 25, 2025, 08:37 Karaman, Mehmet <mehmet.kara...@advantest.com.invalid> wrote: > Hi, > > Is the commons parent released before the commons compress or should > happen after that? > > Best regards, > Mehmet > ________________________________ > From: Gary Gregory <garydgreg...@gmail.com> > Sent: Friday, April 25, 2025 2:12 PM > To: Commons Developers List <dev@commons.apache.org> > Subject: [RESULT][VOTE][LAZY] Release Apache Commons Parent 82 based on RC1 > > [EXTERNAL] This email is from outside, please confirm sender, title, > content and whether you're expecting an email from this sender. If you have > any doubt about the legitimacy of this email, please use the Report feature > of Microsoft Outlook (instructions< > https://myadvantest.sharepoint.com/sites/InformationSecurity/SitePages/en/report_email.aspx > >). > In case of a security incident click here< > https://helpdesk.advantest.com/servicePortal/submitIncident?populateSR_id=334272 > >. > > > This lazy vote passes with the following binding +1: > > - Gary Gregory (ggregory) > > Gary > > > On Sun, Apr 20, 2025 at 12:01 PM Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > We have fixed a few bugs and added enhancements since Apache Commons > > Parent 81 was released, so I would like to release Apache Commons > > Parent 82. > > > > Apache Commons Parent 82 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/parent/82-RC1 (svn > > revision 76390) > > > > The Git tag commons-parent-82-RC1 commit for this RC is > > 2cc7f6c136a0436c6638ca57b9f1a407558ccdd5 which you can browse here: > > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=2cc7f6c136a0436c6638ca57b9f1a407558ccdd5 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > --branch commons-parent-82-RC1 commons-parent-82-RC1 > > > > Maven artifacts are here: > > > https://repository.apache.org/content/repositories/orgapachecommons-1830/org/apache/commons/commons-parent/82/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Sun Apr 20 15:56:31 UTC 2025 > > > commons-parent-82-bom.json=6610f6ebcdd01ea9a4c686ae73fa4c7ed681c1f0d65e6fd28edd7c7cd6eeed2c4320bdc0e76dbfe5ce3e79cb060426ae049a0767b93258207d9d8ec90781ef09 > > > commons-parent-82-bom.xml=f9bbbe9dbd7172ebe6430b278324c11d38d6370d9bc3406432f2f41af1a2493a3e67e636cdd612ca314c56fb62055dd0c94a3126e1c20915a450e9f8e981a01f > > > commons-parent-82-site.xml=07c3de38227fd28664777636162d583dc0cb5061c8133f827023ca3188b641a53ee2aed1192a8842f76071b2db8c5aeef7d4c58457c8688c89d577ae23d51a86 > > > commons-parent-82-src.tar.gz=10e5a9559b1693e9b4046c52b3281662c86093a537f62053f6d03f47c2b5c8aa083d1dc569d2c4d46ff0b5e06ddcbb8fbe1ce54e7f2f1ed9d7686a0cdfd418e3 > > > commons-parent-82-src.zip=f717d03c284d5d952e73348f5ed94e2c3fcf5dc1fe779d934338459e556fa7a84a06a09b30cd0b6200bc535a44ac95143daa252d8c35beede5a92bf5f449a1ff > > > org.apache.commons_commons-parent-82.spdx.json=94cb2d844dbb5362cab00f62f05a89755d9928e572f3563a4fa34d23d796720b72ec24594c453a91e327cae100e558f77756b7d97c4185deac465c5b302538c4 > > > > > > > > I have tested this with 'mvn' and 'mvn -e -V -P release -P test-deploy > > -P jacoco -P japicmp clean package site deploy' using: > > > > openjdk version "21.0.7" 2025-04-15 > > OpenJDK Runtime Environment Homebrew (build 21.0.7) > > OpenJDK 64-Bit Server VM Homebrew (build 21.0.7, mixed mode, sharing) > > > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > > Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec > > Java version: 21.0.7, vendor: Homebrew, runtime: > > /opt/homebrew/Cellar/openjdk@21/21.0.7/libexec/openjdk.jdk/Contents/Home > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "15.4.1", arch: "aarch64", family: "mac" > > > > Darwin Garys-MacBook-Pro.local 24.4.0 Darwin Kernel Version 24.4.0: > > Fri Apr 11 18:32:50 PDT 2025; > > root:xnu-11417.101.15~117/RELEASE_ARM64_T6041 arm64 > > > > Docker version 28.0.4, build b8034c0 > > > > > > Details of changes since 81 are in the release notes: > > > https://dist.apache.org/repos/dist/dev/commons/parent/82-RC1/RELEASE-NOTES.txt > > > https://dist.apache.org/repos/dist/dev/commons/parent/82-RC1/site/changes.html > > > > Site: > > > https://dist.apache.org/repos/dist/dev/commons/parent/82-RC1/site/index.html > > (note some *relative* links are broken and the 82 directories are > > not yet created - these will be OK once the site is deployed.) > > > > JApiCmp Report (compared to 81): > > > https://dist.apache.org/repos/dist/dev/commons/parent/82-RC1/site/japicmp.html > > > > RAT Report: > > > https://dist.apache.org/repos/dist/dev/commons/parent/82-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, 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/parent/82-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-parent.git > > --branch commons-parent-82-RC1 commons-parent-82-RC1 > > cd commons-parent-82-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: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
