Hi Andy
Thanks for the hard work on Jena 3. I didn't find any blocker issue, so here my
vote
[ X ] +1 Approve the release
>+ does everything work on Linux?>+ does the tag in the SCM contain
>reproducible sources?
Build works fine from git commit in local environment:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=512m;
support was removed in 8.0
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-15T06:29:23+13:00)
Maven home: /opt/apache-maven-3.2.5
Java version: 1.8.0_45, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.16.0-38-generic", arch: "amd64", family: "unix"
...
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:25 h
[INFO] Finished at: 2015-07-26T15:48:17+12:00
[INFO] Final Memory: 91M/1227M
Deployed the generated Fuseki2 WAR (jena-fuseki-war-2.3.0) to an Apache Tomcat
7 installed via apt-get, running with Oracle Java 8 JVM, everything worked like
charm. Created a new dataset, uploaded some data, queried, got the response, no
problems :)
I had some recollection about an issue (JENA-869) about reusing the dataset
name. So I deleted the dataset, tried recreating with the same name, but got an
error message. I've commented the issue and attached a screenshot. Everything
else worked.
>+ is there a correct LICENSE and NOTICE file in each artifact
> (both source and binary artifacts)?
Since the build took a little while, I spent some time writing a script to
check the NOTICE and LICENSE files for me [1]. It checks if NOTICE and LICENSE
are present in directories with a pom.xml file, and if the NOTICE file mentions
2015. Here's the output
Reviewing files in /home/kinow/Desktop/jena. Current year is 2015
### NOTICE FILE
--> Missing notice{.txt|.md|} file for apache-jena-libs
--> Missing notice{.txt|.md|} file for apache-jena-osgi
--> Missing notice{.txt|.md|} file for jena-base
--> jena-elephas notice file is not mentioning the year 2015
--> Missing notice{.txt|.md|} file for jena-examples
--> Missing notice{.txt|.md|} file for jena-extras
--> Missing notice{.txt|.md|} file for jena-maven-tools
--> Missing notice{.txt|.md|} file for jena-shaded-guava
### LICENSE FILE
--> Missing license{.txt|.md|} file for apache-jena-libs
--> Missing license{.txt|.md|} file for apache-jena-osgi
--> Missing license{.txt|.md|} file for jena-base
--> Missing license{.txt|.md|} file for jena-examples
--> Missing license{.txt|.md|} file for jena-extras
Cheers
Bruno
[1] https://gist.github.com/kinow/90cbe1cc13343141912b
From: Andy Seaborne <[email protected]>
To: [email protected]
Sent: Sunday, July 26, 2015 8:08 AM
Subject: [VOTE] Release Jena 3.0.0 RC1
Hi,
Here is a vote on a release of Jena 3.0.0 with Fuseki 1.3.0 and Fuseki
2.3.0.
This is the first release candidate for this release.
Everyone, not just committers, is invited to test and vote.
(We do need at least 3 PMC +1's but the more it's tested, the better.)
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1009/
Proposed dist/ area:
https://dist.apache.org/repos/dist/dev/jena/
Keys:
https://svn.apache.org/repos/asf/jena/dist/KEYS
Git commit (browser URL):
https://git-wip-us.apache.org/repos/asf?p=jena.git;a=commit;h=53d59bd3179b90f41cb53969e2b64340fcb66e76
NB - Text wrapping may mangle the above URL
Git Commit Hash:
53d59bd3179b90f41cb53969e2b64340fcb66e76
Git Commit Tag:
jena-3.0.0-rc1
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This vote will be open to at least the end of
Tuesday, 28th July 2015, 23:59 UTC
(96 hours from the same hour tonight UTC).
This is a major release. If you expect to check the release but the
the 96 hour limit does not work for you, please email within the
schedule above with an expected time.
Thanks,
Andy
Checking needed:
+ does everything work on Linux?
+ does everything work on MS Windows?
+ does everything work on OS X?
+ is the GPG signature fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
+ is there a correct LICENSE and NOTICE file in each artifact
(both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag in the SCM contain reproducible sources?
