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 RC1 is available for
review here:
https://dist.apache.org/repos/dist/dev/commons/geometry/1.0-beta1-RC1 (svn
revision 40275)
The Git tag commons-geometry-1.0-beta1-rc1 commit for this RC is
cc94f654e13954c805650d6ab9f6bee333c75a31 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-geometry.git;a=commit;h=cc94f654e13954c805650d6ab9f6bee333c75a31
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-geometry.git --branch
commons-geometry-1.0-beta1-rc1 commons-geometry-1.0-beta1-rc1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1502/org/apache/commons/
These are the artifacts and their hashes:
commons-geometry-1.0-beta1-bin.tar.gz=373ea50d5da28c3ba64dc15058d55dce333ee04a9664d5b69605977271d89d403ac854afb1f6d8108e803e8d6860aae2ae3a9f83fc153b5855b0427bff05b6f4
commons-geometry-1.0-beta1-bin.zip=329cfbd631b7f403f4329b77f564e5aca702746764c23e35756a3100a58ea6896b38b499f3a68cd1bea5d0a72fd63f157e7aeced0dc6377c77d417142b0b4355
commons-geometry-1.0-beta1-src.tar.gz=5ffda78c3a8c2e03e33929a615dcd35181809b85c7aaf1f719a4d51ab4d48f485022707327d4c26c345f902b0c563ab7e5c4d1c00c76823e7d25ba1aa6bc8a20
commons-geometry-1.0-beta1-src.zip=1e6cecf35e5e952cd267463e22a9be00ac0cb80231ee87e475d643d943b4915421f08ca6f15ece51c687c6656acabf5161294f5d3a9dc025fde2657d5f8a27f3
(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"
***
Details of changes are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/geometry/1.0-beta1-RC1/RELEASE-NOTES.txt
https://home.apache.org/~mattjuntunen/commons-geometry-1.0-beta1-rc1-site/changes-report.html
Site:
https://home.apache.org/~mattjuntunen/commons-geometry-1.0-beta1-rc1-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-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.
[ ] +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)
The 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-RC1 commons-geometry-1.0-beta1-RC1
cd commons-geometry-1.0-beta1-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.
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
