Hi. Le dim. 11 juil. 2021 à 23:19, Matt Juntunen <matt.a.juntu...@gmail.com> a écrit : > > We have completed initial development work on Apache Commons Numbers, so I > would like to release Apache Commons Numbers (full distribution) 1.0. > > Apache Commons Numbers (full distribution) 1.0 RC1 is available for review > here: > https://dist.apache.org/repos/dist/dev/commons/numbers/1.0-RC1 (svn > revision 48777) > > The Git tag commons-numbers-1.0-rc1 commit for this RC is > 89a9c3817222a6c67d7a231b19f6c5c7fc995208 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-numbers.git;a=commit;h=89a9c3817222a6c67d7a231b19f6c5c7fc995208 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-numbers.git > --branch commons-numbers-1.0-rc1 commons-numbers-1.0-rc1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1556/ > > These are the artifacts and their hashes: > > commons-numbers-1.0-bin.tar.gz=5e61ee22980a7534fb87793bb16eac371d7aea703552f2c8f14f049ae9646f97db8ae7e0e021c6ef4b4f1c78b529e33995fd4893030280437baf3081d429957a > commons-numbers-1.0-bin.zip=4805949e5fab3c016d35be692b79a587b60e35a5809cc5be0817bce224a9462a5891400085040803183c54f2ff71ebdb385bf5119c5148b801333168aec14444 > commons-numbers-1.0-src.tar.gz=08656e681624e2bf2434714f6060e6b02de673089cc3711a01dfc3f0640791feb689206f68dc323a7bd14cb7760770567edc36bcdbea38b7eb31407521de6316 > commons-numbers-1.0-src.zip=5e80cfe64207c5ce990e2bee3e6a7ab7d22260f9e8f28b936197276c02bcba0e771b23f3f06bdcb4984adee69b748c4ebd3cddea40530b9cf8def64b6d4c91f7
Checksums are OK. [For ease of use it would be nice to have those lines properly formatted for the "sha512sum" tool: (1) checksum, (2) one space character, (3) file name.] > > I have tested this with ***'mvn clean install site'*** using: > *** > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; > 2018-02-24T14:49:05-05:00) > Maven home: /home/matt/tools/maven/apache-maven-3.5.3 > Java version: 1.8.0_292, vendor: Private Build > Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-77-generic", arch: "amd64", family: "unix" > > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; > 2018-02-24T14:49:05-05:00) > Maven home: /home/matt/tools/maven/apache-maven-3.5.3 > Java version: 11.0.2, vendor: Oracle Corporation > Java home: /home/matt/lang/java/jdk-11.0.2 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-77-generic", arch: "amd64", family: "unix" > > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: > C:\Users\matt\tools\apache-maven-3.6.3-bin\apache-maven-3.6.3\bin\.. > Java version: 1.8.0_242, vendor: AdoptOpenJDK, runtime: C:\Program > Files\AdoptOpenJDK\jdk-8.0.242.08-hotspot\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" > *** > > Details of changes since 1.0-beta1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.0-RC1/RELEASE-NOTES.txt > > Site: > https://home.apache.org/~mattjuntunen/commons-numbers-1.0-RC1-site/ > (note some *relative* links are broken and the 1.0 directories are not > yet created - these will be OK once the site is deployed.) > > CLIRR Report: > N/A > > JApiCmp Report: > N/A > > RAT Report: > > https://home.apache.org/~mattjuntunen/commons-numbers-1.0-RC1-site/rat-report.html > > KEYS: > https://www.apache.org/dist/commons/KEYS > > Please review the release candidate and vote. > This vote will close no sooner that 72 hours from now. > [X] +1 Release these artifacts Builds fine using ---CUT--- $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ mvn --version Apache Maven 3.6.0 Maven home: /usr/share/maven Java version: 1.8.0_292, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.19.0-16-amd64", arch: "amd64", family: "unix" ---CUT--- > [...] > > Validating a release candidate > ============================== > > These guidelines are NOT complete. Are they automatically generated? Some additional customization would be welcome so that reviewers are not annoyed with recurrent problems (see below). > > Requirements: Git, Java, Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1) Clone and checkout the RC tag > > git clone https://gitbox.apache.org/repos/asf/commons-numbers.git --branch > commons-numbers-1.0-rc1 commons-numbers-1.0-rc1 For clarity and ease of use, command lines should be on a single line. We used to mention that the signature should be checked: ---CUT--- $ git tag -v commons-numbers-1.0-rc1 object 89a9c3817222a6c67d7a231b19f6c5c7fc995208 type commit tag commons-numbers-1.0-rc1 tagger Matt Juntunen <mattjuntu...@apache.org> 1626025042 -0400 RC1 gpg: Signature made Sun 11 Jul 2021 07:37:22 PM CEST gpg: using RSA key 7DD53AEFEDF1C3D392B51EBE346F4FCECFB70B1A gpg: Good signature from "Matt Juntunen (ASF Code Signing Key) <mattjuntu...@apache.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 7DD5 3AEF EDF1 C3D3 92B5 1EBE 346F 4FCE CFB7 0B1A ---CUT--- > cd commons-numbers-1.0-rc1 > > 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. Not required for a major release. > > 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. Ditto. > > 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 > Linux: uname -a > > 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 > > 6) Build the site for a multi-module project > > mvn site > mvn site:stage > Check the site reports in: > - Windows: target\site\index.html > - Linux: target/site/index.html 1. A directory "site-content" must be created within each module's directory, to avoid useless downloads of SVN files. 2. The JAVA_HOME environment variable must be set (otherwise the "javadoc" command will fail). For Linux, an working example command would be: ---CUT--- $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ mvn site site:stage ---CUT--- Regards, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
