Re: [ALL] pom.xml should not contain RM details
On Thu, 5 Oct 2023 at 00:13, Phil Steitz wrote: > > On Tue, Oct 3, 2023 at 1:26 AM sebb wrote: > > > > The properties are used by the release plugin. > > > > But since they are unique to the user, they do not belong in the shared pom. > > So they should be blank in the component pom? No, they must be absent. > Why do they need to be there at all? It seems they are used by the vote-text goal. > Can't they just be provided on the command line? Yes. > I detest settings.xml, btw. Not under source control, throw-back to the old > special local voodoo build days. Most (all?) of it can be provided on the command line. However, that gets tedious; settings.xml provides useful short-cuts. It should only be used for settings specific to the user. It cannot therefore be added to shared source control. However, you could always keep your copy under source control. > Phil > > > > On Tue, 3 Oct 2023 at 02:33, Phil Steitz wrote: > > > > > > +1 but why then are those properties there? > > > > > > Phil > > > > > > > On Oct 2, 2023, at 3:58 PM, sebb wrote: > > > > > > > > As the subject says, please do not use the pom to store RM details > > > > such as > > > > > > > > commons.releaseManagerName > > > > commons.releaseManagerKey > > > > > > > > These properties are personal to the user, and should be defined in > > > > ~/.m2/settings.xml. > > > > See https://commons.apache.org/proper/commons-release-plugin/index.html > > > > > > > > Or you can define them on the command line. > > > > > > > > If the RM details are stored in the pom, then it is all too easy for > > > > the wrong values to be used. > > > > > > > > Thanks, > > > > Sebb > > > > > > > > - > > > > 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 > > > > - > 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
Re: [all] stopping dependabot and security analyses on dormant components
The dependabot check is once a week on Friday which is, IMO, just right. Gary On Wed, Oct 4, 2023, 7:18 PM Phil Steitz wrote: > On Tue, Oct 3, 2023 at 1:42 PM Emmanuel Bourg wrote: > > > > Le 03/10/2023 à 20:18, Bruno Kinoshita a écrit : > > > Same for me, I prefer to know ahead of time if there are any issues > with > > > dependencies. > > > > But the Commons components are mostly dependency-less, we are flooded by > > dependabot requests to update non code related dependencies (Maven > > plugins, GitHub actions) for non critical purposes. It would be better > > to have such notifications for CVEs only. > > I also hate the noise, but I share the pay-as-you-go mentality that > Gary and Bruno express. Shoving too many updates in the runup to the > release can make things harder and cause things to be missed. I was > bitten badly some years back by a plugin update that caused release > jars to be borked. I would have more likely caught it if the update > had happened sooner. I think sebb's suggestion of decreasing check > frequency is practical. > > Phil > > > > Emmanuel Bourg > > > > > > - > > 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 > >
Re: [VOTE] Release Apache Commons Net 3.10.0 based on RC1
My +1 Gary On Sun, Oct 1, 2023 at 9:48 AM Gary Gregory wrote: > > We have fixed a few bugs and added some enhancements since Apache > Commons Net 3.9.0 was released, so I would like to release Apache > Commons Net 3.10.0. > > Apache Commons Net 3.10.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1 (svn > revision 64282) > > The Git tag commons-net-3.10.0-RC1 commit for this RC is > c3f36eb9078971a159a93065389983fd60ee95f6 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-net.git;a=commit;h=c3f36eb9078971a159a93065389983fd60ee95f6 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-net.git > --branch commons-net-3.10.0-RC1 commons-net-3.10.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1661/commons-net/commons-net/3.10.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Oct 01 09:35:09 EDT 2023 > commons-net-examples-3.10.0.jar=f39be82d6f72f551a723467ca381de363290a4ebd2f885a939ee548b4c5469353bfc4dd6e8ba5c881ded85c5d5245cb70a1940729a61c3fbae9e0bb3d822333a > commons-net-3.10.0-tests.jar=75428b4d6446f98a87ec5ffd76fecc96b292a585903e57b83626c488a8ef106ad682274db9b2964aded4a5a0321abaa48342d86076d5702714c8e80698bb017d > commons-net_commons-net-3.10.0.spdx.json=bc092ab2f294d55df36ca306f072ddbe956e769c99c68867ad671eec6dde5d0de3888de02daf60b4440e87275f20a7271aebfbdc528dbd9f2a6f4f1b833c545b > commons-net-3.10.0-test-sources.jar=7f5e769997dbb322c476ee16df08d32c85082f7a5cb2da0dbe971414df9bc18fff9454bf273913e4f6b2ebe3c680405108c877b2f3d2f66afb746f0b30956302 > commons-net-3.10.0-src.zip=a29748689c64660969fab26f4c33a86114fec6c680707ac78f51c84b3b0dd5465005e24b4e8ce2112e367d7a452b77147a00bb446573613759672265ec3c1891 > commons-net-3.10.0-sources.jar=acb8f07ac5a1f4e3369370f8549eb0951ae340933c851daa3271e072d42c2709789d2c5f62ca138c787787a9dcec5585666ad737f80f4e7c17f0cd6eff3ce26d > commons-net-3.10.0-bin.zip=42d48be13ee3945d7e1ac1dc7cb467f698fed9b87e54f9fd02e8a37d95087823dc961c385f676e7b626f12552b2950f4c965f2f5ea309917a31b3faf2c2c08e6 > commons-net-3.10.0-bom.xml=b42bf3ab0403d66c6fffde48fe6cafcd0b332d2b8f960bd14e0725a3ec476f968907493182bb171dafe376060fa22fd119094d8f1ceece5d8476d4316d4938cb > commons-net-3.10.0-bom.json=bc2c94f269b5cee82345b3e4d23ce3f2673a6cbc8ad1e1b212aa903a7a089017f5e8f30952495b24313d8d2bcb9209048a29a00fc208d7bab3ae6b59ecf7db59 > commons-net-3.10.0-javadoc.jar=ade9ed8ffc50a7d01867c2c60b6abb9da2657bb022cf9e3c1f85203887451b9cde1ee975e459fbcf222366f8d84ea3e883f69c90831b8ab63cd243a80f7716ee > commons-net-ftp-3.10.0.jar=251ffd3ac6d516823aa5c0cba39793db01b65c17c974f1014f8315bf7775cc60f17f0411ec14ed8fd14d62e42963487ee0500ed42cd03a19f88a2fed2dee7874 > commons-net-3.10.0-src.tar.gz=d9d80255feddfb434d3baa629aa9e6d8feffd530c5e3172106fec55bbc986f6423a46dc9e737a1bb7020c62447229e6b83d0b7f9582d041e1def423536cc92dd > commons-net-3.10.0-bin.tar.gz=8707be9410ee8d58889c142f1bf0628445278d38e941aaef2a1be1e16757fad5c50f0ebb3e4f6603bc18955822a8fd383476d4137085e769ddec5b68326015bf > > I have tested this with: > > mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy > > using: > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > Maven home: /usr/local/Cellar/maven/3.9.4/libexec > Java version: 17.0.8.1, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac" > Darwin 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42 > PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64 > > Details of changes since 3.9.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/index.html > (note some *relative* links are broken and the 3.10.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 3.9.0): > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.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, > > Gary Gregory, > Release Manager (using key 86fdc7e2a11262cb) > > For following is intended as a helper and refresher for reviewers. > > Validating a release candidate > == > > These
[RESULT][VOTE] Release Apache Commons Net 3.10.0 based on RC1
This vote passes with the following +1 binding votes: - Bruno Kinoshita - Phil Steitz - Henri Biestro - Gary Gregory Gary On Thu, Oct 5, 2023 at 6:55 AM Gary Gregory wrote: > > My +1 > > Gary > > On Sun, Oct 1, 2023 at 9:48 AM Gary Gregory wrote: > > > > We have fixed a few bugs and added some enhancements since Apache > > Commons Net 3.9.0 was released, so I would like to release Apache > > Commons Net 3.10.0. > > > > Apache Commons Net 3.10.0 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1 (svn > > revision 64282) > > > > The Git tag commons-net-3.10.0-RC1 commit for this RC is > > c3f36eb9078971a159a93065389983fd60ee95f6 which you can browse here: > > > > https://gitbox.apache.org/repos/asf?p=commons-net.git;a=commit;h=c3f36eb9078971a159a93065389983fd60ee95f6 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-net.git > > --branch commons-net-3.10.0-RC1 commons-net-3.10.0-RC1 > > > > Maven artifacts are here: > > > > https://repository.apache.org/content/repositories/orgapachecommons-1661/commons-net/commons-net/3.10.0/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Sun Oct 01 09:35:09 EDT 2023 > > commons-net-examples-3.10.0.jar=f39be82d6f72f551a723467ca381de363290a4ebd2f885a939ee548b4c5469353bfc4dd6e8ba5c881ded85c5d5245cb70a1940729a61c3fbae9e0bb3d822333a > > commons-net-3.10.0-tests.jar=75428b4d6446f98a87ec5ffd76fecc96b292a585903e57b83626c488a8ef106ad682274db9b2964aded4a5a0321abaa48342d86076d5702714c8e80698bb017d > > commons-net_commons-net-3.10.0.spdx.json=bc092ab2f294d55df36ca306f072ddbe956e769c99c68867ad671eec6dde5d0de3888de02daf60b4440e87275f20a7271aebfbdc528dbd9f2a6f4f1b833c545b > > commons-net-3.10.0-test-sources.jar=7f5e769997dbb322c476ee16df08d32c85082f7a5cb2da0dbe971414df9bc18fff9454bf273913e4f6b2ebe3c680405108c877b2f3d2f66afb746f0b30956302 > > commons-net-3.10.0-src.zip=a29748689c64660969fab26f4c33a86114fec6c680707ac78f51c84b3b0dd5465005e24b4e8ce2112e367d7a452b77147a00bb446573613759672265ec3c1891 > > commons-net-3.10.0-sources.jar=acb8f07ac5a1f4e3369370f8549eb0951ae340933c851daa3271e072d42c2709789d2c5f62ca138c787787a9dcec5585666ad737f80f4e7c17f0cd6eff3ce26d > > commons-net-3.10.0-bin.zip=42d48be13ee3945d7e1ac1dc7cb467f698fed9b87e54f9fd02e8a37d95087823dc961c385f676e7b626f12552b2950f4c965f2f5ea309917a31b3faf2c2c08e6 > > commons-net-3.10.0-bom.xml=b42bf3ab0403d66c6fffde48fe6cafcd0b332d2b8f960bd14e0725a3ec476f968907493182bb171dafe376060fa22fd119094d8f1ceece5d8476d4316d4938cb > > commons-net-3.10.0-bom.json=bc2c94f269b5cee82345b3e4d23ce3f2673a6cbc8ad1e1b212aa903a7a089017f5e8f30952495b24313d8d2bcb9209048a29a00fc208d7bab3ae6b59ecf7db59 > > commons-net-3.10.0-javadoc.jar=ade9ed8ffc50a7d01867c2c60b6abb9da2657bb022cf9e3c1f85203887451b9cde1ee975e459fbcf222366f8d84ea3e883f69c90831b8ab63cd243a80f7716ee > > commons-net-ftp-3.10.0.jar=251ffd3ac6d516823aa5c0cba39793db01b65c17c974f1014f8315bf7775cc60f17f0411ec14ed8fd14d62e42963487ee0500ed42cd03a19f88a2fed2dee7874 > > commons-net-3.10.0-src.tar.gz=d9d80255feddfb434d3baa629aa9e6d8feffd530c5e3172106fec55bbc986f6423a46dc9e737a1bb7020c62447229e6b83d0b7f9582d041e1def423536cc92dd > > commons-net-3.10.0-bin.tar.gz=8707be9410ee8d58889c142f1bf0628445278d38e941aaef2a1be1e16757fad5c50f0ebb3e4f6603bc18955822a8fd383476d4137085e769ddec5b68326015bf > > > > I have tested this with: > > > > mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site > > deploy > > > > using: > > > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > > Maven home: /usr/local/Cellar/maven/3.9.4/libexec > > Java version: 17.0.8.1, vendor: Homebrew, runtime: > > /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac" > > Darwin 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42 > > PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64 > > > > Details of changes since 3.9.0 are in the release notes: > > > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/RELEASE-NOTES.txt > > > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/changes-report.html > > > > Site: > > > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/index.html > > (note some *relative* links are broken and the 3.10.0 directories > > are not yet created - these will be OK once the site is deployed.) > > > > JApiCmp Report (compared to 3.9.0): > > > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/japicmp.html > > > > RAT Report: > > > > https://dist.apache.org/repos/dist/dev/commons/net/3.10.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 Relea
Re: [VOTE][LAZY] Release Apache Commons Parent 63 based on RC2
My +1 Gary On Mon, Oct 2, 2023 at 8:26 AM Gary Gregory wrote: > > We have fixed a few bugs and added some enhancements since Apache > Commons Parent 62 was released, so I would like to release Apache > Commons Parent 63. > > Apache Commons Parent 63 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2 > (svn revision 64292) > > The Git tag commons-parent-63-RC2 commit for this RC is > cf512e1352e886a50c1f292420dbc052bdedbf39 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=cf512e1352e886a50c1f292420dbc052bdedbf39 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > --branch commons-parent-63-RC2 commons-parent-63-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1662/org/apache/commons/commons-parent/63/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Mon Oct 02 07:53:04 EDT 2023 > commons-parent-63-src.tar.gz=415919a83c9a84101c586e36da25aeacad9126119e5f3bee1de8db8e4dbda46c5b0a28a0c440ea64254533f31d31be5e2904838e1dd72d456e7befde7a6b2f77 > org.apache.commons_commons-parent-63.spdx.json=51ef87a005d61ad1aa1318770ad79f4decbe717d7a570266c3ad24223fe5f7e7fcaf0ef162a5e6dc232ba6f79799f484ce68345a8bf164bf52f6992bf6d5cc7c > commons-parent-63-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c > commons-parent-63-src.zip=3674e727c8a770117d40d21812d581774446d9144a9625d3b45535231ccc9ad7e923397d1e9df16133888fbcc8745c573639f89523ba3dd360d459d08069eea1 > commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2 > commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744 > > I have tested this with: > > mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy > > using: > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > Maven home: /usr/local/Cellar/maven/3.9.4/libexec > Java version: 17.0.8.1, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac" > > Darwin 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42 > PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64 > > Details of changes since 62 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/index.html > (note some *relative* links are broken and the 63 directories are > not yet created - these will be OK once the site is deployed.) > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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, > > garydgregory, > Release Manager (using key DEADBEEF) > > For 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-parent.git > --branch commons-parent-63-RC2 commons-parent-63-RC2 > cd commons-parent-63-RC2 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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 > Li
Re: [VOTE][LAZY] Release Apache Commons Parent 63 based on RC2
I've not tried to dig into that one. Maybe running with -X will be revealing... Gary On Mon, Oct 2, 2023 at 4:58 PM sebb wrote: > > I get the following warnings on the parent pom with Java 11+: > > $ mvn clean install > [WARNING] Unknown keyword additionalItems - you should define your own > Meta Schema. If the keyword is irrelevant for validation, just use a > NonValidationKeyword > [INFO]attaching as commons-parent-63-SNAPSHOT-cyclonedx.json > [INFO] > [INFO] --- spdx-maven-plugin:0.7.0:createSPDX (build-sbom-spdx) @ > commons-parent --- > [INFO] spdx file type = .json > [INFO] Creating SPDX File > /private/var/sebb/git/commons/parent/target/site/org.apache.commons_commons-parent-63-SNAPSHOT.spdx.json > [WARNING] Unable to map maven licenses to a declared license. Using > NOASSERTION > [WARNING] Null package file > > On Mon, 2 Oct 2023 at 14:20, Gary Gregory wrote: > > > > I plan on eventually having all configs for checkstyle, spotbugs and so on > > under the same dir in each component such that each component is not forced > > to declare checkstyle, spotbugs and so on. > > > > Gary > > > > > > On Mon, Oct 2, 2023, 9:05 AM Alex Herbert wrote: > > > > > Can you provide the usage for the new property? > > > This is listed in the release notes as a new feature thanks to > > > dependabot. But the commit was a single line added by Gary. I do not > > > think it is attributed to dependabot. It is added under the release > > > management section for properties for the Commons Release plugin but I > > > cannot find 'commons.conf.dir' referenced in the current release > > > plugin code. > > > > > > Alex > > > > > > On Mon, 2 Oct 2023 at 13:28, Gary Gregory wrote: > > > > > > > > We have fixed a few bugs and added some enhancements since Apache > > > > Commons Parent 62 was released, so I would like to release Apache > > > > Commons Parent 63. > > > > > > > > Apache Commons Parent 63 RC2 is available for review here: > > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2 > > > > (svn revision 64292) > > > > > > > > The Git tag commons-parent-63-RC2 commit for this RC is > > > > cf512e1352e886a50c1f292420dbc052bdedbf39 which you can browse here: > > > > > > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=cf512e1352e886a50c1f292420dbc052bdedbf39 > > > > You may checkout this tag using: > > > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > > > --branch commons-parent-63-RC2 commons-parent-63-RC2 > > > > > > > > Maven artifacts are here: > > > > > > > https://repository.apache.org/content/repositories/orgapachecommons-1662/org/apache/commons/commons-parent/63/ > > > > > > > > These are the artifacts and their hashes: > > > > > > > > #Release SHA-512s > > > > #Mon Oct 02 07:53:04 EDT 2023 > > > > > > > commons-parent-63-src.tar.gz=415919a83c9a84101c586e36da25aeacad9126119e5f3bee1de8db8e4dbda46c5b0a28a0c440ea64254533f31d31be5e2904838e1dd72d456e7befde7a6b2f77 > > > > > > > org.apache.commons_commons-parent-63.spdx.json=51ef87a005d61ad1aa1318770ad79f4decbe717d7a570266c3ad24223fe5f7e7fcaf0ef162a5e6dc232ba6f79799f484ce68345a8bf164bf52f6992bf6d5cc7c > > > > > > > commons-parent-63-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c > > > > > > > commons-parent-63-src.zip=3674e727c8a770117d40d21812d581774446d9144a9625d3b45535231ccc9ad7e923397d1e9df16133888fbcc8745c573639f89523ba3dd360d459d08069eea1 > > > > > > > commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2 > > > > > > > commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744 > > > > > > > > I have tested this with: > > > > > > > > mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site > > > deploy > > > > > > > > using: > > > > > > > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > > > > Maven home: /usr/local/Cellar/maven/3.9.4/libexec > > > > Java version: 17.0.8.1, vendor: Homebrew, runtime: > > > > /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home > > > > Default locale: en_US, platform encoding: UTF-8 > > > > OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac" > > > > > > > > Darwin 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42 > > > > PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64 > > > > > > > > Details of changes since 62 are in the release notes: > > > > > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/RELEASE-NOTES.txt > > > > > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/changes-report.html > > > > > > > > Site: > > > > > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/index.html > > > > (note so
Re: [VOTE][LAZY] Release Apache Commons Parent 63 based on RC2
This lazy vote passes with one binding +1 from Gary Gregory (me) and comments from Alex Herbert and sebb. Gary On Thu, Oct 5, 2023 at 8:28 AM Gary Gregory wrote: > > I've not tried to dig into that one. Maybe running with -X will be > revealing... > > Gary > > On Mon, Oct 2, 2023 at 4:58 PM sebb wrote: > > > > I get the following warnings on the parent pom with Java 11+: > > > > $ mvn clean install > > [WARNING] Unknown keyword additionalItems - you should define your own > > Meta Schema. If the keyword is irrelevant for validation, just use a > > NonValidationKeyword > > [INFO]attaching as commons-parent-63-SNAPSHOT-cyclonedx.json > > [INFO] > > [INFO] --- spdx-maven-plugin:0.7.0:createSPDX (build-sbom-spdx) @ > > commons-parent --- > > [INFO] spdx file type = .json > > [INFO] Creating SPDX File > > /private/var/sebb/git/commons/parent/target/site/org.apache.commons_commons-parent-63-SNAPSHOT.spdx.json > > [WARNING] Unable to map maven licenses to a declared license. Using > > NOASSERTION > > [WARNING] Null package file > > > > On Mon, 2 Oct 2023 at 14:20, Gary Gregory wrote: > > > > > > I plan on eventually having all configs for checkstyle, spotbugs and so on > > > under the same dir in each component such that each component is not > > > forced > > > to declare checkstyle, spotbugs and so on. > > > > > > Gary > > > > > > > > > On Mon, Oct 2, 2023, 9:05 AM Alex Herbert > > > wrote: > > > > > > > Can you provide the usage for the new property? > > > > This is listed in the release notes as a new feature thanks to > > > > dependabot. But the commit was a single line added by Gary. I do not > > > > think it is attributed to dependabot. It is added under the release > > > > management section for properties for the Commons Release plugin but I > > > > cannot find 'commons.conf.dir' referenced in the current release > > > > plugin code. > > > > > > > > Alex > > > > > > > > On Mon, 2 Oct 2023 at 13:28, Gary Gregory > > > > wrote: > > > > > > > > > > We have fixed a few bugs and added some enhancements since Apache > > > > > Commons Parent 62 was released, so I would like to release Apache > > > > > Commons Parent 63. > > > > > > > > > > Apache Commons Parent 63 RC2 is available for review here: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2 > > > > > (svn revision 64292) > > > > > > > > > > The Git tag commons-parent-63-RC2 commit for this RC is > > > > > cf512e1352e886a50c1f292420dbc052bdedbf39 which you can browse here: > > > > > > > > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=cf512e1352e886a50c1f292420dbc052bdedbf39 > > > > > You may checkout this tag using: > > > > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > > > > --branch commons-parent-63-RC2 commons-parent-63-RC2 > > > > > > > > > > Maven artifacts are here: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachecommons-1662/org/apache/commons/commons-parent/63/ > > > > > > > > > > These are the artifacts and their hashes: > > > > > > > > > > #Release SHA-512s > > > > > #Mon Oct 02 07:53:04 EDT 2023 > > > > > > > > > commons-parent-63-src.tar.gz=415919a83c9a84101c586e36da25aeacad9126119e5f3bee1de8db8e4dbda46c5b0a28a0c440ea64254533f31d31be5e2904838e1dd72d456e7befde7a6b2f77 > > > > > > > > > org.apache.commons_commons-parent-63.spdx.json=51ef87a005d61ad1aa1318770ad79f4decbe717d7a570266c3ad24223fe5f7e7fcaf0ef162a5e6dc232ba6f79799f484ce68345a8bf164bf52f6992bf6d5cc7c > > > > > > > > > commons-parent-63-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c > > > > > > > > > commons-parent-63-src.zip=3674e727c8a770117d40d21812d581774446d9144a9625d3b45535231ccc9ad7e923397d1e9df16133888fbcc8745c573639f89523ba3dd360d459d08069eea1 > > > > > > > > > commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2 > > > > > > > > > commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744 > > > > > > > > > > I have tested this with: > > > > > > > > > > mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site > > > > deploy > > > > > > > > > > using: > > > > > > > > > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > > > > > Maven home: /usr/local/Cellar/maven/3.9.4/libexec > > > > > Java version: 17.0.8.1, vendor: Homebrew, runtime: > > > > > /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home > > > > > Default locale: en_US, platform encoding: UTF-8 > > > > > OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac" > > > > > > > > > > Darwin 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42 > > > > > PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64 > > > > > > > > > >
[ALL] Change to GitHub Workflow message subjects
I discovered recently that GMail conversation mode ignores certain subject prefixes when deciding which emails are in the same thread. In particular, it ignores text in [brackets]; as these were used to enclose the repo name, this resulted in merging emails from different components. The email subjects have been adjusted to use (parentheses) instead of [brackets] so GMail should no longer merge mails from different components. Sebb - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [ALL] Change to GitHub Workflow message subjects
Should we use (VOTE) instead of [VOTE]? Gary On Thu, Oct 5, 2023, 10:53 AM sebb wrote: > I discovered recently that GMail conversation mode ignores certain > subject prefixes when deciding which emails are in the same thread. > > In particular, it ignores text in [brackets]; as these were used to > enclose the repo name, this resulted in merging emails from different > components. > > The email subjects have been adjusted to use (parentheses) instead of > [brackets] so GMail should no longer merge mails from different > components. > > Sebb > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [ALL] Change to GitHub Workflow message subjects
On Thu, 5 Oct 2023 at 17:25, Gary Gregory wrote: > > Should we use (VOTE) instead of [VOTE]? I doubt that is necessary. The GMail behaviour particularly affects the Workflow messages because the same workflow names are re-used, so often the only differentiator was the [component_repo] e.g. [GitHub] [commons-pool]: Workflow run "Java CI" is working again! [GitHub] [commons-lang]: Workflow run "Java CI" is working again! Vote subjects include the component name in plain text. > Gary > > > On Thu, Oct 5, 2023, 10:53 AM sebb wrote: > > > I discovered recently that GMail conversation mode ignores certain > > subject prefixes when deciding which emails are in the same thread. > > > > In particular, it ignores text in [brackets]; as these were used to > > enclose the repo name, this resulted in merging emails from different > > components. > > > > The email subjects have been adjusted to use (parentheses) instead of > > [brackets] so GMail should no longer merge mails from different > > components. > > > > Sebb > > > > - > > 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
Re: [ALL] Change to GitHub Workflow message subjects
But often [VOTE] and [RESULT] are send with the same otherwise subject (and sometimes even [DISCUSS] before the vote, on other projects) On Thu, Oct 5, 2023 at 11:43 AM sebb wrote: > On Thu, 5 Oct 2023 at 17:25, Gary Gregory wrote: > > > > Should we use (VOTE) instead of [VOTE]? > > I doubt that is necessary. > > The GMail behaviour particularly affects the Workflow messages because > the same workflow names are re-used, so often the only differentiator > was the [component_repo] > e.g. > [GitHub] [commons-pool]: Workflow run "Java CI" is working again! > [GitHub] [commons-lang]: Workflow run "Java CI" is working again! > > Vote subjects include the component name in plain text. > > > Gary > > > > > > On Thu, Oct 5, 2023, 10:53 AM sebb wrote: > > > > > I discovered recently that GMail conversation mode ignores certain > > > subject prefixes when deciding which emails are in the same thread. > > > > > > In particular, it ignores text in [brackets]; as these were used to > > > enclose the repo name, this resulted in merging emails from different > > > components. > > > > > > The email subjects have been adjusted to use (parentheses) instead of > > > [brackets] so GMail should no longer merge mails from different > > > components. > > > > > > Sebb > > > > > > - > > > 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 > >
Re: [ALL] Change to GitHub Workflow message subjects
On Thu, 5 Oct 2023 at 17:48, Mike Drob wrote: > > But often [VOTE] and [RESULT] are send with the same otherwise subject (and > sometimes even [DISCUSS] before the vote, on other projects) However in that case the merged conversations will at least relate to the same component. I have not personally found a problem with GMail behaviour for such messages. Whereas with the Workflow messages, it was very easy to miss a message about a component because it was buried in another conversation relating to a different component. But if there is agreement to change the convention (and the docs), I won't object. Sebb > On Thu, Oct 5, 2023 at 11:43 AM sebb wrote: > > > On Thu, 5 Oct 2023 at 17:25, Gary Gregory wrote: > > > > > > Should we use (VOTE) instead of [VOTE]? > > > > I doubt that is necessary. > > > > The GMail behaviour particularly affects the Workflow messages because > > the same workflow names are re-used, so often the only differentiator > > was the [component_repo] > > e.g. > > [GitHub] [commons-pool]: Workflow run "Java CI" is working again! > > [GitHub] [commons-lang]: Workflow run "Java CI" is working again! > > > > Vote subjects include the component name in plain text. > > > > > Gary > > > > > > > > > On Thu, Oct 5, 2023, 10:53 AM sebb wrote: > > > > > > > I discovered recently that GMail conversation mode ignores certain > > > > subject prefixes when deciding which emails are in the same thread. > > > > > > > > In particular, it ignores text in [brackets]; as these were used to > > > > enclose the repo name, this resulted in merging emails from different > > > > components. > > > > > > > > The email subjects have been adjusted to use (parentheses) instead of > > > > [brackets] so GMail should no longer merge mails from different > > > > components. > > > > > > > > Sebb > > > > > > > > - > > > > 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
