We have been working hard to prepare Apache Commons Geometry for an initial
release, so I would like to release Apache Commons Geometry (full distribution)
1.0-beta1.
Apache Commons Geometry (full distribution) 1.0-beta1 RC2 is available for
review here:
https://dist.apache.org/repos/dist/dev/commons/geometry/1.0-beta1-RC2 (svn
revision 40292)
The Git tag commons-geometry-1.0-beta1-rc2 commit for this RC is
418dbb4bb050554ad409ac3c28754822d13a9134 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-geometry.git;a=commit;h=418dbb4bb050554ad409ac3c28754822d13a9134
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-geometry.git --branch
commons-geometry-1.0-beta1-rc2 commons-geometry-1.0-beta1-rc2
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1503/org/apache/commons/
These are the artifacts and their hashes:
commons-geometry-1.0-beta1-bin.tar.gz=c095ac0c387f9a3f0724f1e913e3e0cbb5baada4543b4c70d3a9d1992a69d25a10e2dbabfba2d1bd70adf7c6cc8c65c66af98b3b82207e426805a1a6c25d1037
commons-geometry-1.0-beta1-bin.zip=08fd2a1959c712c0fc62637822ad55cf8a99283cb0230e570f192cd43e07fde7ddd864632bd744a24e5bb0393f7e13a7bba9e683ef59edee5f4747b6589b8751
commons-geometry-1.0-beta1-src.tar.gz=578135e452445d3557453dd73ac0a0e614ade9e136ea3ad08a230f6adb75d4010826619ee38217f6f3b358a42d787c8440a22affe4870d1f2ef2d6599a99dad9
commons-geometry-1.0-beta1-src.zip=f5b22e5cc50c57381f37563c1657c9e24d79ae71f9445b292496353d52a659766dfdb7ea68061b23dde9c6658db25dff91dc398c1d2bd76b81421670de6c1acc
(no need for .asc hashes!)
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_252, 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: "4.15.0-106-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 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/geometry/1.0-beta1-RC2/RELEASE-NOTES.txt
https://home.apache.org/~mattjuntunen/commons-geometry-1.0-beta1-rc2-site/changes-report.html
Site:
https://home.apache.org/~mattjuntunen/commons-geometry-1.0-beta1-rc2-site/index.html
(note some *relative* links are broken and the 1.0-beta1 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-geometry-1.0-beta1-rc2-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.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Matt Juntunen,
Release Manager (using key 7DD53AEFEDF1C3D392B51EBE346F4FCECFB70B1A)
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.
1) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-geometry.git --branch
commons-geometry-1.0-beta1-rc2 commons-geometry-1.0-beta1-rc2
cd commons-geometry-1.0-beta1-rc2
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
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
