[VOTE] (RC1a) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
Hi, Here is a vote on the release of Jena 2.13.0. This is the second vote call on the first release candidate. This call adds the checksums for the dist/ items omitted in the first VOTE call. Everyone, not just committers, is invited to test and vote. We need at least a majority and 3 +1's from the PMC but the more it's tested, the better. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1008/ Proposed dist/ area: http://people.apache.org/~andy/jena-2.13.0-rc1 Keys: https://svn.apache.org/repos/asf/jena/dist/KEYS MD5 and SHA1 checksums below. Git commit (web browser URL): https://git-wip-us.apache.org/repos/asf?p=jena.git;a=commit;h=ecaa41eefdcb79f16bd4b9525b89309f8282ca47 NB - Text wrapping may mangle the above URL Git Commit Hash: ecaa41eefdcb79f16bd4b9525b89309f8282ca47 Git Commit Tag: jena-2.13.0-rc1 New since last release: Elephas Fuseki2 OSGi 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 Thursday, 12th March 2014, 23:59 UTC (72 hours from the same hour tonight UTC). This is a major release. If you expect to check the release but the the 72 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? release checksums: source/jena-2.13.0-source-release.zip.sha1 9b51356e847f1f40368704470aced6a61da6d6e5 source/jena-2.13.0-source-release.zip.md5 1dbc545225588c3fe6bf43b62f8def5b binaries checksums: binaries/apache-jena-2.13.0.tar.gz.sha1 f11a0531e61575f56f11bc8a7c56605fdb618786 binaries/apache-jena-2.13.0.zip.sha1 fad0683eb2cbcef1337f07494dcbde51d1776f1b binaries/apache-jena-fuseki-2.0.0.tar.gz.sha1 57e5fbde8802bc328ed3213af414bb459a047c22 binaries/apache-jena-fuseki-2.0.0.zip.sha1 9e871762ebfc903e218a0098d43fbe9b46c49212 binaries/jena-fuseki1-1.1.2-distribution.tar.gz.sha1 e22d7dfe6b427de267642fe7dc2141ab662db24b binaries/jena-fuseki1-1.1.2-distribution.zip.sha1 845d2b1fe5573a173460f230127fe13b3c057e17 binaries/apache-jena-2.13.0.tar.gz.md5 92f5cedc7b1e3d04946c24365871a362 binaries/apache-jena-2.13.0.zip.md5 016fad436b0b07796e003797cd1906b7 binaries/apache-jena-fuseki-2.0.0.tar.gz.md5 a51e7df978e5e7e989be31e05c7fe1d4 binaries/apache-jena-fuseki-2.0.0.zip.md5 b8facd59d4f51d299a62c653f46f1967 binaries/jena-fuseki1-1.1.2-distribution.tar.gz.md5 29c20a1ca615258cb2e615f1c2ff367a binaries/jena-fuseki1-1.1.2-distribution.zip.md5 d44c4bf801e705aba800a4ba7c01dc6e
Re: [VOTE] [CANCEL] (RC1) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
VOTE cancelled due to lack of checksums.
Re: [VOTE] (RC1) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
+ are the checksums correct? Bother. I'll cancel the vote and restart it. The checksums should be included, well, at least the source-release one. Andy You didn't say what is the hash of the source-release.zip, so I have assumed the below: sha1: 9b51356e847f1f40368704470aced6a61da6d6e5 jena-2.13.0-source-release.zip f11a0531e61575f56f11bc8a7c56605fdb618786 apache-jena-2.13.0.tar.gz fad0683eb2cbcef1337f07494dcbde51d1776f1b apache-jena-2.13.0.zip 57e5fbde8802bc328ed3213af414bb459a047c22 apache-jena-fuseki-2.0.0.tar.gz 9e871762ebfc903e218a0098d43fbe9b46c49212 apache-jena-fuseki-2.0.0.zip e22d7dfe6b427de267642fe7dc2141ab662db24b jena-fuseki1-1.1.2-distribution.tar.gz 845d2b1fe5573a173460f230127fe13b3c057e17 jena-fuseki1-1.1.2-distribution.zip md5: 1dbc545225588c3fe6bf43b62f8def5b jena-2.13.0-source-release.zip 92f5cedc7b1e3d04946c24365871a362 apache-jena-2.13.0.tar.gz 016fad436b0b07796e003797cd1906b7 apache-jena-2.13.0.zip a51e7df978e5e7e989be31e05c7fe1d4 apache-jena-fuseki-2.0.0.tar.gz b8facd59d4f51d299a62c653f46f1967 apache-jena-fuseki-2.0.0.zip 29c20a1ca615258cb2e615f1c2ff367a jena-fuseki1-1.1.2-distribution.tar.gz d44c4bf801e705aba800a4ba7c01dc6e jena-fuseki1-1.1.2-distribution.zip
Re: [VOTE] (RC1a) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... +1 Andy
Re: [VOTE] (RC1) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
On 09/03/15 10:39, Stian Soiland-Reyes wrote: -1: Release notes not updated. Everything else fine. Thank you for the checking. WARNING: Release notes are missing for 2.13.0 source/jena-2.13.0/jena-core/ReleaseNotes.txt binaries/apache-jena-2.13.0/ReleaseNotes-Jena.txt does NOT mention 2.12.1 or 2.13.0 Could you explain why that is a -1, not 0 or even a conditional +1? Release notes are useful to some people but it does not affect the question of whether the release process has been executed correctly. See 81 items: http://s.apache.org/jena-2.13.0-jira (Because of the bulk update of JIRA recently, I had to approximate by limiting the creation date - 81 is an underestimate but close.) We have two significant new modules. People are using them from development. Creating this release has been a significant amount of work with several last minute things delaying the release. Would having an action plan to deal with the issue be sufficient for you? Proposal: If they are not going to be maintained, and we have JIRA which we do use, I propose we retire all the ReleaseNotes*. They are not universal across the modules anyway. I hope that with that proposal and the VOTE with hashes, you can vote +1 on the next VOTE. + does everything work on Linux? Tested on Ubuntu 14.10 x64 with stain@biggie-utopic:/tmp/jena/people.apache.org/~andy/jena-2.13.0-rc1/source$ java -version java version 1.7.0_75 OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~utopic1) OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode) Not sure which 'everything' to test.. so I tested Fuseki 2 binary distribution. The source-release and the build. AKA can it run the test suites. Everything is is a convenience. There is no ASF requirement for code to work perfectly - we, here at Jena, do run the tests in the release process and I'd almost certainly pull a release I was doing if it didn't pass tests but I can imagine a situation where an urgent, specific matter needs addressing in a release. We, project style, make sure that master green lines. It's not the only possible style of project. Defining prescriptively the acceptable levels is impossible, especially as the scale of the project grows. Anyone can do a release at any time (Apache culture) so in any project, a release can conceivable have things that work and things that don't. Someone may want a release to get specific bug fixes out. It is a little harder, but not impossible, for a non-commiter to do a release. The PMC's role is to verify the process has been executed correctly. Andy
Re: [VOTE] (RC1) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
On 9 Mar 2015 12:10, Andy Seaborne Could you explain why that is a -1, not 0 or even a conditional +1? Release notes are useful to some people but it does not affect the question of whether the release process has been executed correctly. I was not sure of the practise here, and would have called it +0, but didn't as you labelled that as Don't care. I care! :-) I thus did -1 to flag this for other voters, knowing that this would not necessarily block the release if there were no other -1s chiming in. You would need to make a new RC+VOTE if you want to fix it in the distribution. If the majority think its OK to go out with outdated release notes that is fine with me, so as such you can think of it as a conditional +1. I found the release execution to otherwise be correct, but you said it was a major release and then I would expect any included release notes to reflect that. We have two significant new modules. People are using them from development. Creating this release has been a significant amount of work with several last minute things delaying the release. Would having an action plan to deal with the issue be sufficient for you? I will be happy with this if the others are OK with the outdated release notes in the downloads. Proposal: If they are not going to be maintained, and we have JIRA which we do use, I propose we retire all the ReleaseNotes*. They are not universal across the modules anyway. +1, for the future just include link to the fixed URL of changes within the download, avoiding duplication and manual updating. Not sure which 'everything' to test.. so I tested Fuseki 2 binary distribution. The source-release and the build. AKA can it run the test suites. Everything is is a convenience. As this is the first Fuseki 2 release (which also has a UI I believe is not tested by the build) I tested it explicitly. Agree that manual testing of everything would not generally be feasible beyond the build tests :-)
Re: [VOTE] (RC1a) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
+1 ..conditional on future retirement of ReleaseNotes https://issues.apache.org/jira/browse/JENA-896 This vote supersedes http://mail-archives.apache.org/mod_mbox/jena-dev/201503.mbox/%3CCAMBJEmWfFmVmr6o9d-nogSWK50YcdFO741g4ngvKiNDYenoDTg%40mail.gmail.com%3E On 9 March 2015 at 13:43, Andy Seaborne a...@apache.org wrote: Hi, Here is a vote on the release of Jena 2.13.0. This is the second vote call on the first release candidate. This call adds the checksums for the dist/ items omitted in the first VOTE call. Everyone, not just committers, is invited to test and vote. We need at least a majority and 3 +1's from the PMC but the more it's tested, the better. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1008/ Proposed dist/ area: http://people.apache.org/~andy/jena-2.13.0-rc1 Keys: https://svn.apache.org/repos/asf/jena/dist/KEYS MD5 and SHA1 checksums below. Git commit (web browser URL): https://git-wip-us.apache.org/repos/asf?p=jena.git;a=commit;h=ecaa41eefdcb79f16bd4b9525b89309f8282ca47 NB - Text wrapping may mangle the above URL Git Commit Hash: ecaa41eefdcb79f16bd4b9525b89309f8282ca47 Git Commit Tag: jena-2.13.0-rc1 New since last release: Elephas Fuseki2 OSGi 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 Thursday, 12th March 2014, 23:59 UTC (72 hours from the same hour tonight UTC). This is a major release. If you expect to check the release but the the 72 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? release checksums: source/jena-2.13.0-source-release.zip.sha1 9b51356e847f1f40368704470aced6a61da6d6e5 source/jena-2.13.0-source-release.zip.md5 1dbc545225588c3fe6bf43b62f8def5b binaries checksums: binaries/apache-jena-2.13.0.tar.gz.sha1 f11a0531e61575f56f11bc8a7c56605fdb618786 binaries/apache-jena-2.13.0.zip.sha1 fad0683eb2cbcef1337f07494dcbde51d1776f1b binaries/apache-jena-fuseki-2.0.0.tar.gz.sha1 57e5fbde8802bc328ed3213af414bb459a047c22 binaries/apache-jena-fuseki-2.0.0.zip.sha1 9e871762ebfc903e218a0098d43fbe9b46c49212 binaries/jena-fuseki1-1.1.2-distribution.tar.gz.sha1 e22d7dfe6b427de267642fe7dc2141ab662db24b binaries/jena-fuseki1-1.1.2-distribution.zip.sha1 845d2b1fe5573a173460f230127fe13b3c057e17 binaries/apache-jena-2.13.0.tar.gz.md5 92f5cedc7b1e3d04946c24365871a362 binaries/apache-jena-2.13.0.zip.md5 016fad436b0b07796e003797cd1906b7 binaries/apache-jena-fuseki-2.0.0.tar.gz.md5 a51e7df978e5e7e989be31e05c7fe1d4 binaries/apache-jena-fuseki-2.0.0.zip.md5 b8facd59d4f51d299a62c653f46f1967 binaries/jena-fuseki1-1.1.2-distribution.tar.gz.md5 29c20a1ca615258cb2e615f1c2ff367a binaries/jena-fuseki1-1.1.2-distribution.zip.md5 d44c4bf801e705aba800a4ba7c01dc6e -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/-0001-9842-9718
[jira] [Created] (JENA-896) Remove ReleaseNotes.txt from releases
Stian Soiland-Reyes created JENA-896: Summary: Remove ReleaseNotes.txt from releases Key: JENA-896 URL: https://issues.apache.org/jira/browse/JENA-896 Project: Apache Jena Issue Type: Task Components: Documentation, Web site Affects Versions: Jena 2.13.0 Reporter: Stian Soiland-Reyes The [release notes of 2.13.0 RC1|https://github.com/apache/jena/blob/ecaa41eefdcb79f16bd4b9525b89309f8282ca47/jena-core/ReleaseNotes.txt] were not updated to mention 2.13.0 It was [suggested for future releases|http://mail-archives.apache.org/mod_mbox/jena-dev/201503.mbox/%3C54FD8D9D.8020206%40apache.org%3E] to remove these ReleaseNotes from the releases as they require manual updating - and instead include a fixed URL to page(s) that describes the change log. This may be an auto-generated page in Jira or a page on the website, with links to Jira. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] (RC1a) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
Now also tested on Windows 8.0 x64 with java 8u40 and Maven 3.2.5 Fuseki 2 binary works well with TDB, load, query, backup and restore, data survives restart after ctrl-c. http://localhost:3030/manage.html#new-dataset does not work in Internet Explorer 10 unless you click the Enable intranet setting popup (!). Jena source builds fine with mvn clean install -DskipTests If I try again without -DskipTests it bails out at this point: ... ... » Unexpected exception, expectedjava.sql.SQLFeatureNotSupportedException b ... » Unexpected exception, expectedjava.sql.SQLFeatureNotSupportedException b ... » Unexpected exception, expectedjava.sql.SQLFeatureNotSupportedException b ... TestTdbDiskResultSetsAbstractResultSetTests.results_construct_bytes_01:1076- AbstractTdbResultSetTests.createResults:85-AbstractTdbResultSetTests.createResu lts:90-prepareDataset:65 » File TestTdbDiskResultSetsAbstractResultSetTests.results_construct_bytes_02:1103- AbstractTdbResultSetTests.createResults:85-AbstractTdbResultSetTests.createResu lts:90-prepareDataset:65 » File ... [INFO] Apache Jena - JDBC In-Memory Driver SUCCESS [ 23.711 s] [INFO] Apache Jena - JDBC TDB Driver .. FAILURE [ 30.050 s] [INFO] Apache Jena - JDBC Driver Bundle ... SKIPPED [INFO] Apache Jena - Maven Plugins, including schemagen ... SKIPPED ... [INFO] Apache Jena SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] After wondering why nothing else worked after this, it seems to be because I ran out of disk space on the poor C:! I deleted the jena-2.13.0 source code folder, and now had 23 GB free. How many GB do I need to compile Jena with tests on Windows? I assume this has to do with the folder workaround of https://issues.apache.org/jira/browse/JENA-115 (and JENA-804 ?) as jena-tdb/target consumed about 18 GBs. I also had 25 GB in %TEMP% - this seems to fill up on C: even if I build jena-jdbc on D: with 34 GB free -- the problem is that neither the test nor mvn clean tidies this up. Raised as https://issues.apache.org/jira/browse/JENA-897 This is not a regression from 2.12.1, which has the same problem (and also fails in JDBC TDB Driver), so no change of my +1 vote.
[jira] [Created] (JENA-897) jena-jdbc-tdb tests use %TEMP% instead of target/
Stian Soiland-Reyes created JENA-897: Summary: jena-jdbc-tdb tests use %TEMP% instead of target/ Key: JENA-897 URL: https://issues.apache.org/jira/browse/JENA-897 Project: Apache Jena Issue Type: Bug Components: JDBC Affects Versions: Jena 2.12.1, Jena 2.13.0 Environment: Windowx x64, C: with 34 GB free Reporter: Stian Soiland-Reyes Priority: Critical Fix For: Jena 2.13.1 .. and thus mvn clean install on Windows will easily consume 37 GB on C: and run out of disk space - even if Jena is built on a larger partition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JENA-897) jena-jdbc-tdb tests use %TEMP% instead of target/
[ https://issues.apache.org/jira/browse/JENA-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Soiland-Reyes updated JENA-897: - Environment: Windowx 8.0 x64, C: with 34 GB free (was: Windowx x64, C: with 34 GB free) jena-jdbc-tdb tests use %TEMP% instead of target/ - Key: JENA-897 URL: https://issues.apache.org/jira/browse/JENA-897 Project: Apache Jena Issue Type: Bug Components: JDBC Affects Versions: Jena 2.12.1, Jena 2.13.0 Environment: Windowx 8.0 x64, C: with 34 GB free Reporter: Stian Soiland-Reyes Priority: Critical Fix For: Jena 2.13.1 .. and thus mvn clean install on Windows will easily consume 37 GB on C: and run out of disk space - even if Jena is built on a larger partition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] (RC1) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
-1: Release notes not updated. Everything else fine. WARNING: Release notes are missing for 2.13.0 source/jena-2.13.0/jena-core/ReleaseNotes.txt binaries/apache-jena-2.13.0/ReleaseNotes-Jena.txt does NOT mention 2.12.1 or 2.13.0 + are the checksums correct? You didn't say what is the hash of the source-release.zip, so I have assumed the below: sha1: 9b51356e847f1f40368704470aced6a61da6d6e5 jena-2.13.0-source-release.zip f11a0531e61575f56f11bc8a7c56605fdb618786 apache-jena-2.13.0.tar.gz fad0683eb2cbcef1337f07494dcbde51d1776f1b apache-jena-2.13.0.zip 57e5fbde8802bc328ed3213af414bb459a047c22 apache-jena-fuseki-2.0.0.tar.gz 9e871762ebfc903e218a0098d43fbe9b46c49212 apache-jena-fuseki-2.0.0.zip e22d7dfe6b427de267642fe7dc2141ab662db24b jena-fuseki1-1.1.2-distribution.tar.gz 845d2b1fe5573a173460f230127fe13b3c057e17 jena-fuseki1-1.1.2-distribution.zip md5: 1dbc545225588c3fe6bf43b62f8def5b jena-2.13.0-source-release.zip 92f5cedc7b1e3d04946c24365871a362 apache-jena-2.13.0.tar.gz 016fad436b0b07796e003797cd1906b7 apache-jena-2.13.0.zip a51e7df978e5e7e989be31e05c7fe1d4 apache-jena-fuseki-2.0.0.tar.gz b8facd59d4f51d299a62c653f46f1967 apache-jena-fuseki-2.0.0.zip 29c20a1ca615258cb2e615f1c2ff367a jena-fuseki1-1.1.2-distribution.tar.gz d44c4bf801e705aba800a4ba7c01dc6e jena-fuseki1-1.1.2-distribution.zip + is there a source archive? Yes! + does everything work on Linux? Tested on Ubuntu 14.10 x64 with stain@biggie-utopic:/tmp/jena/people.apache.org/~andy/jena-2.13.0-rc1/source$ java -version java version 1.7.0_75 OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~utopic1) OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode) Not sure which 'everything' to test.. so I tested Fuseki 2 binary distribution. zip and tar.gz matches in content. ./fuseki-server starts and works - writing to ./run Tested in the UI to create new dataset, uploading of two *.ttl.gz and trying the two default queries. Backup works - also restore into a new dataset with the expected number of triples. I also tested using Jena from Apache Taverna Language by modifying our parent to use 2.13.0 and the repository - all our tests pass OK + does everything work on MS Windows? Not tested + does everything work on OS X? Not tested + is the GPG signature fine? gpg: Signature made Sun 08 Mar 2015 10:27:38 GMT using RSA key ID 9CC7ECFE gpg: Good signature from Andy Seaborne (Code signing key) a...@apache.org 9CC7ECFE is in KEYS Signature verified for: jena-2.13.0-source-release.zip.asc apache-jena-2.13.0.tar.gz.asc apache-jena-2.13.0.zip.asc apache-jena-fuseki-2.0.0.tar.gz.asc apache-jena-fuseki-2.0.0.zip.asc jena-fuseki1-1.1.2-distribution.tar.gz.asc jena-fuseki1-1.1.2-distribution.zip.asc All *.asc in the Maven repository verify as well. + can the source archive really be built? Yes, but it does take a while to run all the Elephas I/O tests.. :) Tested with Docker image maven:3-jdk-7 bf326e841380 (with an empty .m2/repository) root@294bc7afa18a:/# java -version java version 1.7.0_75 OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-2) OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode) root@294bc7afa18a:/# mvn -version Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T17:29:23+00:00) Maven home: /usr/share/maven Java version: 1.7.0_75, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: linux, version: 3.16.0-31-generic, arch: amd64, family: unix .. [INFO] Apache Jena - JDBC TDB Driver .. SUCCESS [02:07 min] .. [INFO] Apache Jena - Elephas - I/O SUCCESS [16:29 min] .. [INFO] Total time: 28:15 min The build produces JARs which filenames (e.g. jena-jdbc-driver-mem-1.1.2.jar) match each of the JAR filenames in https://repository.apache.org/content/repositories/orgapachejena-1008/ (I did not check -javadoc -tests and -sources) + is there a correct LICENSE and NOTICE file in each artifact (both source and binary artifacts)? I am unable to say they are correct, but comprehensive LICENSE and NOTICE files are present in: source/jena-2.13.0-source-release.zip binaries/apache-jena-fuseki-2.0.0.zip binaries/jena-fuseki1-1.1.2-distribution.zip binaries/apache-jena-2.13.0.zip + does the NOTICE file contain all necessary attributions? Not checked. + have any licenses of dependencies changed due to upgrades? if so have LICENSE and NOTICE been upgraded appropriately? Not checked. + does the tag in the SCM contain reproducible sources? Yes. ecaa41eefdcb79f16bd4b9525b89309f8282ca47 matches tag jena-2.13.0-rc1 and (almost) all files in the content of the source distribution matches the git repository stain@biggie-utopic:/tmp/jena$ diff -ur jena-git jena-src Only in jena-src: DEPENDENCIES Only in jena-git: .gitignore Only in jena-git/jena-arq: .gitattributes Only in jena-git/jena-arq/Grammar: .gitignore
Re: GSoC 2015 - who's considering mentoring?
Looking through the proposed projects (label: gsoc2015) : https://issues.apache.org/jira/browse/JENA-664?jql=project%20%3D%20JENA%20AND%20labels%20%3D%20gsoc2015 I could perhaps mentor JENA-647 SPARQL template queries On 7 March 2015 at 18:05, Andy Seaborne a...@apache.org wrote: GSoC 2015 is kicking off. Who is planning on mentoring this year (if the right project comes along)? Andy -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/-0001-9842-9718
Re: [VOTE] (RC1a) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0
+1 not binding. Build works fine for the zipped archive and for the git commit in the following environment, running `mvn clean install`. Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T15:29:23-02:00) Maven home: /opt/apache-maven-3.2.5 Java version: 1.8.0_40, 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-31-generic, arch: amd64, family: unix ThanksBurno From: Andy Seaborne a...@apache.org To: dev@jena.apache.org Sent: Monday, March 9, 2015 10:43 AM Subject: [VOTE] (RC1a) Release Jena 2.13.0, with Fuseki 1.1.2 and Fuseki 2.0.0 Hi, Here is a vote on the release of Jena 2.13.0. This is the second vote call on the first release candidate. This call adds the checksums for the dist/ items omitted in the first VOTE call. Everyone, not just committers, is invited to test and vote. We need at least a majority and 3 +1's from the PMC but the more it's tested, the better. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1008/ Proposed dist/ area: http://people.apache.org/~andy/jena-2.13.0-rc1 Keys: https://svn.apache.org/repos/asf/jena/dist/KEYS MD5 and SHA1 checksums below. Git commit (web browser URL): https://git-wip-us.apache.org/repos/asf?p=jena.git;a=commit;h=ecaa41eefdcb79f16bd4b9525b89309f8282ca47 NB - Text wrapping may mangle the above URL Git Commit Hash: ecaa41eefdcb79f16bd4b9525b89309f8282ca47 Git Commit Tag: jena-2.13.0-rc1 New since last release: Elephas Fuseki2 OSGi 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 Thursday, 12th March 2014, 23:59 UTC (72 hours from the same hour tonight UTC). This is a major release. If you expect to check the release but the the 72 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? release checksums: source/jena-2.13.0-source-release.zip.sha1 9b51356e847f1f40368704470aced6a61da6d6e5 source/jena-2.13.0-source-release.zip.md5 1dbc545225588c3fe6bf43b62f8def5b binaries checksums: binaries/apache-jena-2.13.0.tar.gz.sha1 f11a0531e61575f56f11bc8a7c56605fdb618786 binaries/apache-jena-2.13.0.zip.sha1 fad0683eb2cbcef1337f07494dcbde51d1776f1b binaries/apache-jena-fuseki-2.0.0.tar.gz.sha1 57e5fbde8802bc328ed3213af414bb459a047c22 binaries/apache-jena-fuseki-2.0.0.zip.sha1 9e871762ebfc903e218a0098d43fbe9b46c49212 binaries/jena-fuseki1-1.1.2-distribution.tar.gz.sha1 e22d7dfe6b427de267642fe7dc2141ab662db24b binaries/jena-fuseki1-1.1.2-distribution.zip.sha1 845d2b1fe5573a173460f230127fe13b3c057e17 binaries/apache-jena-2.13.0.tar.gz.md5 92f5cedc7b1e3d04946c24365871a362 binaries/apache-jena-2.13.0.zip.md5 016fad436b0b07796e003797cd1906b7 binaries/apache-jena-fuseki-2.0.0.tar.gz.md5 a51e7df978e5e7e989be31e05c7fe1d4 binaries/apache-jena-fuseki-2.0.0.zip.md5 b8facd59d4f51d299a62c653f46f1967 binaries/jena-fuseki1-1.1.2-distribution.tar.gz.md5 29c20a1ca615258cb2e615f1c2ff367a binaries/jena-fuseki1-1.1.2-distribution.zip.md5 d44c4bf801e705aba800a4ba7c01dc6e
How does Jena-ARQ execute the queries containing ORDER BY + LIMIT clause
Hi, I saw the following issue posted on Jena website (which has been recently resolved): Avoid a total sort for ORDER BY + LIMIT queries (https://issues.apache.org/jira/browse/JENA-89). I am very interested in understanding as to how does Jena-ARQ avoids total sort for ORDER BY + LIMIT queries. In the post it is mentioned that Jena-ARQ uses priority queue for avoiding a final sort, however it is also mentioned that ARQ's algebra package contains already a OpTopN [3] operator. The OpExecutor [4] will need to use a new QueryIterTopN instead of QueryIterSort + QueryIterSlice. It is not clear now does the priority queue benefit from OpTopN operator and QueryIterTopN as the links [3] and [4] mentioned on the website does not work, so I am not able to understand their operation and as to how do they help in avoiding a total sort. Can someone please explain how does Jena-ARQ execute the queries containing ORDER BY + LIMIT clause. With Warm Regards, Rose
[jira] [Commented] (JENA-897) jena-jdbc-tdb tests use %TEMP% instead of target/
[ https://issues.apache.org/jira/browse/JENA-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14354030#comment-14354030 ] ASF GitHub Bot commented on JENA-897: - GitHub user stain opened a pull request: https://github.com/apache/jena/pull/41 JENA-897 Override java.io.tmpdir to write to target/ .. instead of /tmp or %TEMP% Fixes JENA-897 (although it still needs 35 GB of disk space on Windows) You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-897-jdbc-tmp Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/41.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #41 commit 494d9471147fb8299813e068cf7f95d3e3d0e156 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-10T01:07:17Z JENA-897 Override java.io.tmpdir to write to target/ .. instead of /tmp or %TEMP% jena-jdbc-tdb tests use %TEMP% instead of target/ - Key: JENA-897 URL: https://issues.apache.org/jira/browse/JENA-897 Project: Apache Jena Issue Type: Bug Components: JDBC Affects Versions: Jena 2.12.1, Jena 2.13.0 Environment: Windowx 8.0 x64, C: with 34 GB free Reporter: Stian Soiland-Reyes Priority: Critical Fix For: Jena 2.13.1 .. and thus mvn clean install on Windows will easily consume 37 GB on C: and run out of disk space - even if Jena is built on a larger partition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] jena pull request: JENA-897 Override java.io.tmpdir to write to ta...
GitHub user stain opened a pull request: https://github.com/apache/jena/pull/41 JENA-897 Override java.io.tmpdir to write to target/ .. instead of /tmp or %TEMP% Fixes JENA-897 (although it still needs 35 GB of disk space on Windows) You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/jena JENA-897-jdbc-tmp Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/41.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #41 commit 494d9471147fb8299813e068cf7f95d3e3d0e156 Author: Stian Soiland-Reyes st...@apache.org Date: 2015-03-10T01:07:17Z JENA-897 Override java.io.tmpdir to write to target/ .. instead of /tmp or %TEMP% --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: GSoC 2015 - who's considering mentoring?
Possibly, I keep wanting to do this each year but circumstances keep getting in my way. The summer months are unfortunately likely to be crunch time in my group at Cray so it would have to be really the right project for me to be able to find time to mentor it Rob On 07/03/2015 18:05, Andy Seaborne a...@apache.org wrote: GSoC 2015 is kicking off. Who is planning on mentoring this year (if the right project comes along)? Andy
