Re: [VOTE] Apache Jena 3.10.0 RC1
[ x ] +1 Approve the release Building passing fine with `mvn clean test install -Pdev` on: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-18T06:33:14+12:00) Maven home: /opt/apache-maven-3.5.4 Java version: 1.8.0_191, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_NZ, platform encoding: UTF-8 OS name: "linux", version: "4.15.0-43-generic", arch: "amd64", family: "unix" Also had a look at the archives in the dist area, everything looking good. + does everything work on Linux? Yes + are the GPG signatures fine? + are the checksums correct? Both above look OK. Key matching 04C95136D236A58F, no issues found with checksums. + is there a source archive? Yes, and contents look OK. + can the source archive really be built? (NB This requires a "mvn install" first time) Yes, mvn clean install -Pdev worked fine, producing a 3.10.0 release. + is there a correct LICENSE and NOTICE file in each artifact (both source and binary artifacts)? Looked at a few artefacts and everything seemed OK. + does the NOTICE file contain all necessary attributions? Looks OK. + have any licenses of dependencies changed due to upgrades? if so have LICENSE and NOTICE been upgraded appropriately? Don't think so. All good IMO. + does the tag/commit in the SCM contain reproducible sources? Yes, built from SCM tag initially. Thanks for RM'ing Bruno From: Andy Seaborne To: "dev@jena.apache.org" Sent: Monday, 31 December 2018 6:31 AM Subject: [VOTE] Apache Jena 3.10.0 RC1 Hi, Here is a vote on a release of Jena 3.10.0. This is the first proposed release candidate. The deadline for the vote is Wednesday, 2 January 2019, at 21:00 UTC Release changes: 44 JIRA: https://s.apache.org/jena-3.10.0-jira == Retirements Old modules retired and not in this release: jena-fuseki1 jena-csv See https://lists.apache.org/thread.html/edd5876b070f24091e19b5c1dd274ef46c74a0f920d419a29a59f66b@%3Cusers.jena.apache.org%3E == Changes of note: The project intends to replace jena-spatial in a future release with Greg's GeoSPARQL: https://github.com/galbiston/geosparql-jena JENA-1621 : Lucene upgrade to 7.4 May need to reload Lucene indexes. (e.g. the Lucene index was create originally with Lucene v5.x (prior Jena 3.3.0). See Lucene upgrade tool. https://lucene.apache.org/solr/guide/7_4/indexupgrader-tool.html JENA-1623 : Fuseki security - user authentication and access control. JENA-1627 : HTTPs support http://jena.staging.apache.org/documentation/fuseki2/data-access-control == Updates Only plugins. JENA-1624 surefire : 2.21.0 -> 2.22.1 (+ SUREFIRE-1588) compiler : 3.7.0 -> 3.8.0 shade: 3.1.0 -> 3.2.0 Release Vote Everyone, not just committers, is invited to test and vote. Please download and test the proposed release. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1028 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://github.com/apache/jena/commit/ab482e34 Git Commit Hash: ab482e34584350af717db1a8d698aa3949e51871 Git Commit Tag: jena-3.10.0 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 Wednesday, 2 January 2019, at 20:00 UTC If you expect to check the release but the time limit does not work for you, please email within the schedule above with an expected time and we can extend the vote period. Thanks, Andy Checking needed: + does everything work on Linux? + does everything work on MS Windows? + does everything work on OS X? + are the GPG signatures fine? + are the checksums correct? + is there a source archive? + can the source archive really be built? (NB This requires a "mvn install" first time) + 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/commit in the SCM contain reproducible sources?
Re: [DRAFT] Apache Jena - January 2019
+1 Not sure if worth, but maybe we can state that users were informed about the modules being retired (I remember seeing an e-mail some time ago in the jena-users?). Cheers Bruno From: Andy Seaborne To: "dev@jena.apache.org" Sent: Monday, 31 December 2018 4:51 AM Subject: [DRAFT] Apache Jena - January 2019 Draft board report for the January board meeting: --- ## Description: Jena is a framework for developing Semantic Web and Linked Data applications in Java. It provides implementation of W3C standards for RDF and SPARQL. ## Issues: There are no issues requiring board attention at this time. ## Activity: The project is currently voting on the 3.10.0 in line with the 3-4 month cycle as and when volunteer time is available. The git repo was migrated seamlessly to gitbox - excellent process by INFRA. The project has received a significant contribution of a GeoSPARQL ending and the team is migrating from the custom spatial query solution to the Open Geospatial Consortium standards based one. The project is also retiring some unused modules that do not receive attention and have had very little in the way of user questions over the last few years. ## Health report: The project is at normal levels of activity, with JIRA and git pull requests getting being responded to, and the users list remains active. There are also many questions asked and answered on stackoverflow where answers come from a wider community. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Chris Tomlinson on Sun Apr 29 2018 ## Committer base changes: - Currently 17 committers. - No new committers added in the last 3 months - Last committer addition was Aaron Coburn at Mon Jun 18 2018 ## Releases: - Last release was Jena 3.9.0 on Fri Sep 28 2018 ## JIRA activity: - 44 JIRA tickets created in the last 3 months - 58 JIRA tickets closed/resolved in the last 3 months
Re: [VOTE] Apache Jena 3.10.0 RC1
+1 On 30/12/2018 17:31, Andy Seaborne wrote: Hi, Here is a vote on a release of Jena 3.10.0. This is the first proposed release candidate. The deadline for the vote is Wednesday, 2 January 2019, at 21:00 UTC Release Vote Everyone, not just committers, is invited to test and vote. Please download and test the proposed release. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1028 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://github.com/apache/jena/commit/ab482e34 Git Commit Hash: ab482e34584350af717db1a8d698aa3949e51871 Git Commit Tag: jena-3.10.0 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 Wednesday, 2 January 2019, at 20:00 UTC If you expect to check the release but the time limit does not work for you, please email within the schedule above with an expected time and we can extend the vote period. Thanks, Andy Checking needed: + does everything work on Linux? + does everything work on MS Windows? + does everything work on OS X? + are the GPG signatures fine? + are the checksums correct? + is there a source archive? + can the source archive really be built? (NB This requires a "mvn install" first time) + 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/commit in the SCM contain reproducible sources?
[VOTE] Apache Jena 3.10.0 RC1
Hi, Here is a vote on a release of Jena 3.10.0. This is the first proposed release candidate. The deadline for the vote is Wednesday, 2 January 2019, at 21:00 UTC Release changes: 44 JIRA: https://s.apache.org/jena-3.10.0-jira == Retirements Old modules retired and not in this release: jena-fuseki1 jena-csv See https://lists.apache.org/thread.html/edd5876b070f24091e19b5c1dd274ef46c74a0f920d419a29a59f66b@%3Cusers.jena.apache.org%3E == Changes of note: The project intends to replace jena-spatial in a future release with Greg's GeoSPARQL: https://github.com/galbiston/geosparql-jena JENA-1621 : Lucene upgrade to 7.4 May need to reload Lucene indexes. (e.g. the Lucene index was create originally with Lucene v5.x (prior Jena 3.3.0). See Lucene upgrade tool. https://lucene.apache.org/solr/guide/7_4/indexupgrader-tool.html JENA-1623 : Fuseki security - user authentication and access control. JENA-1627 : HTTPs support http://jena.staging.apache.org/documentation/fuseki2/data-access-control == Updates Only plugins. JENA-1624 surefire : 2.21.0 -> 2.22.1 (+ SUREFIRE-1588) compiler : 3.7.0 -> 3.8.0 shade: 3.1.0 -> 3.2.0 Release Vote Everyone, not just committers, is invited to test and vote. Please download and test the proposed release. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1028 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://github.com/apache/jena/commit/ab482e34 Git Commit Hash: ab482e34584350af717db1a8d698aa3949e51871 Git Commit Tag: jena-3.10.0 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 Wednesday, 2 January 2019, at 20:00 UTC If you expect to check the release but the time limit does not work for you, please email within the schedule above with an expected time and we can extend the vote period. Thanks, Andy Checking needed: + does everything work on Linux? + does everything work on MS Windows? + does everything work on OS X? + are the GPG signatures fine? + are the checksums correct? + is there a source archive? + can the source archive really be built? (NB This requires a "mvn install" first time) + 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/commit in the SCM contain reproducible sources?
Re: [DRAFT] Apache Jena - January 2019
LGTM-- one possible typo: "standards based" => "standards-based". At least, that's how I've usually seen it. ajs6f > On Dec 30, 2018, at 10:51 AM, Andy Seaborne wrote: > > Draft board report for the January board meeting: > > --- > > > > ## Description: > > Jena is a framework for developing Semantic Web and Linked Data > applications in Java. It provides implementation of W3C standards for > RDF and SPARQL. > > ## Issues: > > There are no issues requiring board attention at this time. > > ## Activity: > > The project is currently voting on the 3.10.0 in line with the 3-4 month > cycle as and when volunteer time is available. > > The git repo was migrated seamlessly to gitbox - excellent process by INFRA. > > The project has received a significant contribution of a GeoSPARQL ending and > the team is migrating from the custom spatial query solution to the Open > Geospatial Consortium standards based one. > > The project is also retiring some unused modules that do not receive > attention and have had very little in the way of user questions over the last > few years. > > ## Health report: > > The project is at normal levels of activity, with JIRA and git pull requests > getting being responded to, and the users list remains active. There are also > many questions asked and answered on stackoverflow where answers come from a > wider community. > > ## PMC changes: > > - Currently 13 PMC members. > - No new PMC members added in the last 3 months > - Last PMC addition was Chris Tomlinson on Sun Apr 29 2018 > > ## Committer base changes: > > - Currently 17 committers. > - No new committers added in the last 3 months > - Last committer addition was Aaron Coburn at Mon Jun 18 2018 > > ## Releases: > > - Last release was Jena 3.9.0 on Fri Sep 28 2018 > > ## JIRA activity: > > - 44 JIRA tickets created in the last 3 months > - 58 JIRA tickets closed/resolved in the last 3 months >
[DRAFT] Apache Jena - January 2019
Draft board report for the January board meeting: --- ## Description: Jena is a framework for developing Semantic Web and Linked Data applications in Java. It provides implementation of W3C standards for RDF and SPARQL. ## Issues: There are no issues requiring board attention at this time. ## Activity: The project is currently voting on the 3.10.0 in line with the 3-4 month cycle as and when volunteer time is available. The git repo was migrated seamlessly to gitbox - excellent process by INFRA. The project has received a significant contribution of a GeoSPARQL ending and the team is migrating from the custom spatial query solution to the Open Geospatial Consortium standards based one. The project is also retiring some unused modules that do not receive attention and have had very little in the way of user questions over the last few years. ## Health report: The project is at normal levels of activity, with JIRA and git pull requests getting being responded to, and the users list remains active. There are also many questions asked and answered on stackoverflow where answers come from a wider community. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Chris Tomlinson on Sun Apr 29 2018 ## Committer base changes: - Currently 17 committers. - No new committers added in the last 3 months - Last committer addition was Aaron Coburn at Mon Jun 18 2018 ## Releases: - Last release was Jena 3.9.0 on Fri Sep 28 2018 ## JIRA activity: - 44 JIRA tickets created in the last 3 months - 58 JIRA tickets closed/resolved in the last 3 months
Re: Toward Jena 3.10.0
On 30/12/2018 13:40, Andy Seaborne wrote: I'll start on the 3.10.0 build - it looks like we can include jena-maven-tools as well I spoke too soon. In the complete build, jena-maven-tools still has test failures even though it passes when run on its own. because Bruno has a fix for the build for that. Bruno also wins the "oldest resolved JIRA prize this year" for JENA-57! The only task outstanding is to update the (c) date to 2019... unless there is anything else? Andy
[jira] [Commented] (JENA-204) Schemagen picking random multi-lingual rdfs:comments as output Java comments
[ https://issues.apache.org/jira/browse/JENA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730979#comment-16730979 ] ASF subversion and git services commented on JENA-204: -- Commit da1bd8f9ebb484821c6ce518f9d04a75008d09ce in jena's branch refs/heads/master from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=da1bd8f ] Merge pull request #518 from kinow/fix-schemagen-maven-plugin JENA-204: Fix schemagen maven plugin > Schemagen picking random multi-lingual rdfs:comments as output Java comments > > > Key: JENA-204 > URL: https://issues.apache.org/jira/browse/JENA-204 > Project: Apache Jena > Issue Type: Bug > Components: Cmd line tools >Affects Versions: Jena 2.7.0 > Environment: Window 7 x64 > $ java -version > java version "1.6.0_25" > Java(TM) SE Runtime Environment (build 1.6.0_25-b06) > Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode) >Reporter: Stuart Williams >Assignee: Bruno P. Kinoshita >Priority: Minor > Fix For: Jena 3.10.0 > > > Schemagen appears to propagate 'random' rdfs:comments into java comments in > the output file. The org ontology (http://www.w3.org/ns/org#) has both > English (@en) and French (@fr) rdfs:comments. The output from: > schemagen -i http://www.w3.org/ns/org# > contains a random mix of French and English comments - one per item, but not > all of one language. > This may be user error and there may be a switch that I've not found for > selecting a comment language in the face of choice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-204) Schemagen picking random multi-lingual rdfs:comments as output Java comments
[ https://issues.apache.org/jira/browse/JENA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730978#comment-16730978 ] ASF subversion and git services commented on JENA-204: -- Commit 99846a34446099012403357ccc300f384a61ce2f in jena's branch refs/heads/master from Bruno P. Kinoshita [ https://gitbox.apache.org/repos/asf?p=jena.git;h=99846a3 ] JENA-204: add lang option to schemagen via maven-tools too > Schemagen picking random multi-lingual rdfs:comments as output Java comments > > > Key: JENA-204 > URL: https://issues.apache.org/jira/browse/JENA-204 > Project: Apache Jena > Issue Type: Bug > Components: Cmd line tools >Affects Versions: Jena 2.7.0 > Environment: Window 7 x64 > $ java -version > java version "1.6.0_25" > Java(TM) SE Runtime Environment (build 1.6.0_25-b06) > Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode) >Reporter: Stuart Williams >Assignee: Bruno P. Kinoshita >Priority: Minor > Fix For: Jena 3.10.0 > > > Schemagen appears to propagate 'random' rdfs:comments into java comments in > the output file. The org ontology (http://www.w3.org/ns/org#) has both > English (@en) and French (@fr) rdfs:comments. The output from: > schemagen -i http://www.w3.org/ns/org# > contains a random mix of French and English comments - one per item, but not > all of one language. > This may be user error and there may be a switch that I've not found for > selecting a comment language in the face of choice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Toward Jena 3.10.0
I'll start on the 3.10.0 build - it looks like we can include jena-maven-tools as well because Bruno has a fix for the build for that. Bruno also wins the "oldest resolved JIRA prize this year" for JENA-57! The only task outstanding is to update the (c) date to 2019... unless there is anything else? Andy
