My +1 Gary
On Fri, Jan 31, 2025 at 10:38 AM Gary Gregory <garydgreg...@gmail.com> wrote: > > [The main change since RC1 is the fix for OSGi] > > We have fixed a few bugs and added enhancements since Apache Commons > Logging 1.3.4 was released, so I would like to release Apache Commons > Logging 1.3.5. > > Apache Commons Logging 1.3.5 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC2 > (svn revision 74565) > > The Git tag commons-logging-1.3.5-RC2 commit for this RC is > 698cda4096ef648f3d4ee520d86b79b44aba86fe which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=698cda4096ef648f3d4ee520d86b79b44aba86fe > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-logging.git > --branch commons-logging-1.3.5-RC2 commons-logging-1.3.5-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1812/commons-logging/commons-logging/1.3.5/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri Jan 31 15:27:11 UTC 2025 > commons-logging-1.3.5-adapters.jar=4984fa483a1668151f511756c2ddbeb231ce774697c3f4d23cc026ddb195dd02ae59022024294c19001955ad40eac1e10a7d312c0dec94b814d72b8d51f4e099 > commons-logging-1.3.5-api.jar=3ea2433e80f5cce8197a8738d426a26717784798fcd4861aa7ce5aacec33174aa95551fc1ae102072f210676604325d653acd46e5462482092cc617b77b5a726 > commons-logging-1.3.5-bin.tar.gz=123daec9c4d195bff7c47b356f21396848c7c5bde4d8a486e2ef026e95a3c719cbcc7d296a70c9608cdad47ce761f9314ac9be7a9f89f386bac8550121afc847 > commons-logging-1.3.5-bin.zip=bf762ba13b6f330f419641a6a070d6a13d2e885ed976d7aa9d15908cc1f5afb89481b49443f91ebf7895eefd21e049168c22f1785a80a4034bf1d8d70bcd8583 > commons-logging-1.3.5-bom.json=31ff594ce4ed5b9c4fbc98f96076ef1b98072a16b6c5b1e66e63255625fc1a8c2957d51c537e1a9689be82665d93f24b62b57ef55b75c43199e5267d3a645ffa > commons-logging-1.3.5-bom.xml=50ce73fb60a71e94f6a38244b9b0c246d10aa86ee070d757113359b935fdbd21398e261945018bb2d70201be87d27bf4ad6c87e0c6d12fc42e745a0ba69a9d1e > commons-logging-1.3.5-javadoc.jar=0f47538dd7b4eacbe08bb807377a7a933f78a9ee5222d88fb78157169d0d26a39243490c87955911597aa05f8bfca5224c5b35ea326859e7a640aec5ab50bd72 > commons-logging-1.3.5-sources.jar=fc216d742be309233f49a1d42345fe7817ba205e32401b86ae62afe989a68d998e79d5fe5eff307eebbc3f9bbc19621961f02beb6d763385b51bdaec1d8d1dc6 > commons-logging-1.3.5-src.tar.gz=07463385a3d997413fd7cb996d7266d0325e0829d88ee1d844ee13cdee702da5ec5817ccdd2b4bbccc3c9f6defd0f08f0397e6218bbd658b3e8336e9f146c0c3 > commons-logging-1.3.5-src.zip=f64312cae8d6d727538414ead6e3ffffe9339d9dcc126bfa1df29a672324847f2e826d7794e15fdac9ba93d881e1641ac40a27835e74cdd7c1f744bd770c71d3 > commons-logging-1.3.5-test-sources.jar=e011173916488ee838b7f5fdaa19b72a8bb9e3d223ee95eb252728193b6baca7498361d659506fa10388c6db3304447691174b8341db143553337e24c0023de0 > commons-logging-1.3.5-tests.jar=22eb9ab80dc3095ebddea65423bfab6db81fc7b919c384b63fca0440c0746e3563235c75bddf5dab7922eb5a27d5e864872d4b2064a3f5a482081c262664ace8 > commons-logging_commons-logging-1.3.5.spdx.json=edf3ef1deebc3ea168a6e2e1886bf5e64473c6516f50042a2d9671d3508777e2f810df8bf11b9fe3cf7f352cf7739510f0ae29efd8fa36f3b43b9b171da3295d > > > > I have tested this with 'mvn' and 'mvn clean install site' using: > *** > Use the output from "mvn -version" for each combination you tested. > Windows: ver > Linux: uname -a > *** > > Details of changes since 1.3.4 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC2/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC2/site/index.html > (note some *relative* links are broken and the 1.3.5 directories > are not yet created - these will be OK once the site is deployed.) > > *** JApiCmp Report (compared to 1.3.4): > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC2/site/japicmp.html > > *** > Note that the above report notes several errors. > These are considered OK for the reasons stated below. > These exceptions are also noted in the Changes and Release Notes. > > Errors reported: > - methods added to interface: OK because that does not affect > binary compatibility. > - etc. > *** > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-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, > > 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/logging/1.3.5-RC2/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-logging.git > --branch commons-logging-1.3.5-RC2 commons-logging-1.3.5-RC2 > cd commons-logging-1.3.5-RC2 > > 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
