You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by aj...@apache.org on 2017/05/02 19:17:27 UTC

[VOTE] Release vote : Apache Jena 3.3.0

Hi Jena-folks,

Here is a vote on a release of Jena 3.3.0 (with Fuseki 2.6.0).

The most obvious changes in this release are some large shifts in support for full-text indexing. See below for details.

This is the first proposed candidate for this release.

== Dependency changes:

jena-text: Lucene v6.4.1

New module:
     jena-text-es
     Elasticsearch: v5.2.2 License : AL2
       https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
     [*] Full list of recursive dependencies at the end

== Updates:
     Guava (shaded) to version 21.

== Key features of the release:

* Drop text indexing support for solr4j, add support for Elastic Search
     JENA-1301 - Drop Solr
     JENA-1305 - Elastic Search support
     Accomplished thanks to contributions from Anuj Kumar!

* Add VCARD4 (JENA-1205)
    Contribution from Bart Hanssens

* RDFParser (JENA-1306)
   New low level, detailed setup of parsers for special cases.
   RDFDataMgr is still the main way to read data (it now uses RDFParser).

* RDFWriter (JENA-1323)

* Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.
   (JENA-1324)


   ~39 other JIRA tickets
   See https://s.apache.org/jena-3.3.0-jira

== Release

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-1017

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):
       http://git-wip-us.apache.org/repos/asf/jena/commit/a35bad97

Git Commit Hash:
       a35bad974eb24e4ed03af195c7adef72039cd030

Git Commit Tag:
       jena-3.3.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

       17:00 UTC-04:00 (US Eastern 5PM) on Friday 5 May 2017

If you expect to check the release but the 72 hour limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.

Thanks,

       ajs6f

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?
+ 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?


--------------------------------------------------

[*]
org.elasticsearch dependencies (recursive) other than org.apache artifacts:

org.elasticsearch:elasticsearch:jar:5.2.2
net.sf.jopt-simple:jopt-simple:jar:5.0.2
com.carrotsearch:hppc:jar:0.7.1
joda-time:joda-time:jar:2.9.5
org.yaml:snakeyaml:jar:1.15
com.tdunning:t-digest:jar:3.0
org.hdrhistogram:HdrHistogram:jar
net.java.dev.jna:jna:jar:4.2.2
io.netty:netty:jar:3.10.6.Final
com.github.spullara.mustache.java:compiler:jar:0.9.3


Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by anuj kumar <an...@gmail.com>.
+1

Waiting eagerly for the release :)

Thanks,
Anuj Kumar

On Wed, May 3, 2017 at 12:14 PM, Bruno P. Kinoshita <
brunodepaulak@yahoo.com.br.invalid> wrote:

>
>
> [ X ] +1 Approve the release
>
> Build passing on Linux (Ubuntu LTS), and
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-11T05:41:47+13:00)
> Maven home: /opt/maven
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-75-generic", arch: "amd64", family:
> "unix"
>
> Thanks!!!
> Bruno
> ________________________________
> From: "ajs6f@apache.org" <aj...@apache.org>
> To: dev@jena.apache.org; users@jena.apache.org
> Sent: Wednesday, 3 May 2017 7:17 AM
> Subject: [VOTE] Release vote : Apache Jena 3.3.0
>
>
>
> Hi Jena-folks,
>
>
> Here is a vote on a release of Jena 3.3.0 (with Fuseki 2.6.0).
>
>
> The most obvious changes in this release are some large shifts in support
> for full-text indexing. See below for details.
>
>
> This is the first proposed candidate for this release.
>
>
> == Dependency changes:
>
>
> jena-text: Lucene v6.4.1
>
>
> New module:
>
>      jena-text-es
>
>      Elasticsearch: v5.2.2 License : AL2
>
>       https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
>
>      [*] Full list of recursive dependencies at the end
>
>
> == Updates:
>
>      Guava (shaded) to version 21.
>
>
> == Key features of the release:
>
>
> * Drop text indexing support for solr4j, add support for Elastic Search
>
>      JENA-1301 - Drop Solr
>
>      JENA-1305 - Elastic Search support
>
>      Accomplished thanks to contributions from Anuj Kumar!
>
>
> * Add VCARD4 (JENA-1205)
>
>     Contribution from Bart Hanssens
>
>
> * RDFParser (JENA-1306)
>
>    New low level, detailed setup of parsers for special cases.
>
>    RDFDataMgr is still the main way to read data (it now uses RDFParser).
>
>
> * RDFWriter (JENA-1323)
>
>
> * Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.
>
>    (JENA-1324)
>
>
>
>    ~39 other JIRA tickets
>
>    See https://s.apache.org/jena-3.3.0-jira
>
>
> == Release
>
>
> 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-1017
>
>
> 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):
>
>       http://git-wip-us.apache.org/repos/asf/jena/commit/a35bad97
>
>
> Git Commit Hash:
>
>        a35bad974eb24e4ed03af195c7adef72039cd030
>
>
> Git Commit Tag:
>
>        jena-3.3.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
>
>
>        17:00 UTC-04:00 (US Eastern 5PM) on Friday 5 May 2017
>
>
> If you expect to check the release but the 72 hour limit does not work
>
> for you, please email within the schedule above with an expected time
>
> and we can extend the vote period.
>
>
> Thanks,
>
>
>        ajs6f
>
>
> 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?
>
> + 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?
>
>
>
> --------------------------------------------------
>
>
> [*]
>
> org.elasticsearch dependencies (recursive) other than org.apache artifacts:
>
>
> org.elasticsearch:elasticsearch:jar:5.2.2
>
> net.sf.jopt-simple:jopt-simple:jar:5.0.2
>
> com.carrotsearch:hppc:jar:0.7.1
>
> joda-time:joda-time:jar:2.9.5
>
> org.yaml:snakeyaml:jar:1.15
>
> com.tdunning:t-digest:jar:3.0
>
> org.hdrhistogram:HdrHistogram:jar
>
> net.java.dev.jna:jna:jar:4.2.2
>
> io.netty:netty:jar:3.10.6.Final
>
> com.github.spullara.mustache.java:compiler:jar:0.9.3
>



-- 
*Anuj Kumar*

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by anuj kumar <an...@gmail.com>.
+1

Waiting eagerly for the release :)

Thanks,
Anuj Kumar

On Wed, May 3, 2017 at 12:14 PM, Bruno P. Kinoshita <
brunodepaulak@yahoo.com.br.invalid> wrote:

>
>
> [ X ] +1 Approve the release
>
> Build passing on Linux (Ubuntu LTS), and
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-11T05:41:47+13:00)
> Maven home: /opt/maven
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-75-generic", arch: "amd64", family:
> "unix"
>
> Thanks!!!
> Bruno
> ________________________________
> From: "ajs6f@apache.org" <aj...@apache.org>
> To: dev@jena.apache.org; users@jena.apache.org
> Sent: Wednesday, 3 May 2017 7:17 AM
> Subject: [VOTE] Release vote : Apache Jena 3.3.0
>
>
>
> Hi Jena-folks,
>
>
> Here is a vote on a release of Jena 3.3.0 (with Fuseki 2.6.0).
>
>
> The most obvious changes in this release are some large shifts in support
> for full-text indexing. See below for details.
>
>
> This is the first proposed candidate for this release.
>
>
> == Dependency changes:
>
>
> jena-text: Lucene v6.4.1
>
>
> New module:
>
>      jena-text-es
>
>      Elasticsearch: v5.2.2 License : AL2
>
>       https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt
>
>      [*] Full list of recursive dependencies at the end
>
>
> == Updates:
>
>      Guava (shaded) to version 21.
>
>
> == Key features of the release:
>
>
> * Drop text indexing support for solr4j, add support for Elastic Search
>
>      JENA-1301 - Drop Solr
>
>      JENA-1305 - Elastic Search support
>
>      Accomplished thanks to contributions from Anuj Kumar!
>
>
> * Add VCARD4 (JENA-1205)
>
>     Contribution from Bart Hanssens
>
>
> * RDFParser (JENA-1306)
>
>    New low level, detailed setup of parsers for special cases.
>
>    RDFDataMgr is still the main way to read data (it now uses RDFParser).
>
>
> * RDFWriter (JENA-1323)
>
>
> * Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.
>
>    (JENA-1324)
>
>
>
>    ~39 other JIRA tickets
>
>    See https://s.apache.org/jena-3.3.0-jira
>
>
> == Release
>
>
> 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-1017
>
>
> 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):
>
>       http://git-wip-us.apache.org/repos/asf/jena/commit/a35bad97
>
>
> Git Commit Hash:
>
>        a35bad974eb24e4ed03af195c7adef72039cd030
>
>
> Git Commit Tag:
>
>        jena-3.3.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
>
>
>        17:00 UTC-04:00 (US Eastern 5PM) on Friday 5 May 2017
>
>
> If you expect to check the release but the 72 hour limit does not work
>
> for you, please email within the schedule above with an expected time
>
> and we can extend the vote period.
>
>
> Thanks,
>
>
>        ajs6f
>
>
> 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?
>
> + 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?
>
>
>
> --------------------------------------------------
>
>
> [*]
>
> org.elasticsearch dependencies (recursive) other than org.apache artifacts:
>
>
> org.elasticsearch:elasticsearch:jar:5.2.2
>
> net.sf.jopt-simple:jopt-simple:jar:5.0.2
>
> com.carrotsearch:hppc:jar:0.7.1
>
> joda-time:joda-time:jar:2.9.5
>
> org.yaml:snakeyaml:jar:1.15
>
> com.tdunning:t-digest:jar:3.0
>
> org.hdrhistogram:HdrHistogram:jar
>
> net.java.dev.jna:jna:jar:4.2.2
>
> io.netty:netty:jar:3.10.6.Final
>
> com.github.spullara.mustache.java:compiler:jar:0.9.3
>



-- 
*Anuj Kumar*

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.

[ X ] +1 Approve the release

Build passing on Linux (Ubuntu LTS), and

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)
Maven home: /opt/maven
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-75-generic", arch: "amd64", family: "unix"

Thanks!!!
Bruno
________________________________
From: "ajs6f@apache.org" <aj...@apache.org>
To: dev@jena.apache.org; users@jena.apache.org 
Sent: Wednesday, 3 May 2017 7:17 AM
Subject: [VOTE] Release vote : Apache Jena 3.3.0



Hi Jena-folks,


Here is a vote on a release of Jena 3.3.0 (with Fuseki 2.6.0).


The most obvious changes in this release are some large shifts in support for full-text indexing. See below for details.


This is the first proposed candidate for this release.


== Dependency changes:


jena-text: Lucene v6.4.1


New module:

     jena-text-es

     Elasticsearch: v5.2.2 License : AL2

      https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt

     [*] Full list of recursive dependencies at the end


== Updates:

     Guava (shaded) to version 21.


== Key features of the release:


* Drop text indexing support for solr4j, add support for Elastic Search

     JENA-1301 - Drop Solr

     JENA-1305 - Elastic Search support

     Accomplished thanks to contributions from Anuj Kumar!


* Add VCARD4 (JENA-1205)

    Contribution from Bart Hanssens


* RDFParser (JENA-1306)

   New low level, detailed setup of parsers for special cases.

   RDFDataMgr is still the main way to read data (it now uses RDFParser).


* RDFWriter (JENA-1323)


* Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.

   (JENA-1324)



   ~39 other JIRA tickets

   See https://s.apache.org/jena-3.3.0-jira


== Release


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-1017


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):

      http://git-wip-us.apache.org/repos/asf/jena/commit/a35bad97


Git Commit Hash:

       a35bad974eb24e4ed03af195c7adef72039cd030


Git Commit Tag:

       jena-3.3.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


       17:00 UTC-04:00 (US Eastern 5PM) on Friday 5 May 2017


If you expect to check the release but the 72 hour limit does not work

for you, please email within the schedule above with an expected time

and we can extend the vote period.


Thanks,


       ajs6f


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?

+ 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?



--------------------------------------------------


[*]

org.elasticsearch dependencies (recursive) other than org.apache artifacts:


org.elasticsearch:elasticsearch:jar:5.2.2

net.sf.jopt-simple:jopt-simple:jar:5.0.2

com.carrotsearch:hppc:jar:0.7.1

joda-time:joda-time:jar:2.9.5

org.yaml:snakeyaml:jar:1.15

com.tdunning:t-digest:jar:3.0

org.hdrhistogram:HdrHistogram:jar

net.java.dev.jna:jna:jar:4.2.2

io.netty:netty:jar:3.10.6.Final

com.github.spullara.mustache.java:compiler:jar:0.9.3

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.

[ X ] +1 Approve the release

Build passing on Linux (Ubuntu LTS), and

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)
Maven home: /opt/maven
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-75-generic", arch: "amd64", family: "unix"

Thanks!!!
Bruno
________________________________
From: "ajs6f@apache.org" <aj...@apache.org>
To: dev@jena.apache.org; users@jena.apache.org 
Sent: Wednesday, 3 May 2017 7:17 AM
Subject: [VOTE] Release vote : Apache Jena 3.3.0



Hi Jena-folks,


Here is a vote on a release of Jena 3.3.0 (with Fuseki 2.6.0).


The most obvious changes in this release are some large shifts in support for full-text indexing. See below for details.


This is the first proposed candidate for this release.


== Dependency changes:


jena-text: Lucene v6.4.1


New module:

     jena-text-es

     Elasticsearch: v5.2.2 License : AL2

      https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt

     [*] Full list of recursive dependencies at the end


== Updates:

     Guava (shaded) to version 21.


== Key features of the release:


* Drop text indexing support for solr4j, add support for Elastic Search

     JENA-1301 - Drop Solr

     JENA-1305 - Elastic Search support

     Accomplished thanks to contributions from Anuj Kumar!


* Add VCARD4 (JENA-1205)

    Contribution from Bart Hanssens


* RDFParser (JENA-1306)

   New low level, detailed setup of parsers for special cases.

   RDFDataMgr is still the main way to read data (it now uses RDFParser).


* RDFWriter (JENA-1323)


* Bad URIs in RDF/XML are now warnings (model.read) inline with RDF 1.1.

   (JENA-1324)



   ~39 other JIRA tickets

   See https://s.apache.org/jena-3.3.0-jira


== Release


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-1017


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):

      http://git-wip-us.apache.org/repos/asf/jena/commit/a35bad97


Git Commit Hash:

       a35bad974eb24e4ed03af195c7adef72039cd030


Git Commit Tag:

       jena-3.3.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


       17:00 UTC-04:00 (US Eastern 5PM) on Friday 5 May 2017


If you expect to check the release but the 72 hour limit does not work

for you, please email within the schedule above with an expected time

and we can extend the vote period.


Thanks,


       ajs6f


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?

+ 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?



--------------------------------------------------


[*]

org.elasticsearch dependencies (recursive) other than org.apache artifacts:


org.elasticsearch:elasticsearch:jar:5.2.2

net.sf.jopt-simple:jopt-simple:jar:5.0.2

com.carrotsearch:hppc:jar:0.7.1

joda-time:joda-time:jar:2.9.5

org.yaml:snakeyaml:jar:1.15

com.tdunning:t-digest:jar:3.0

org.hdrhistogram:HdrHistogram:jar

net.java.dev.jna:jna:jar:4.2.2

io.netty:netty:jar:3.10.6.Final

com.github.spullara.mustache.java:compiler:jar:0.9.3

[RESULT] [VOTE] Release vote : Apache Jena 3.3.0

Posted by aj...@apache.org.

---
A. Soroka

sorokaaj@gmail.com wrote on 5/7/17 3:04 PM:
> Okay, folks, we have 3 binding +1 votes and no binding -1 votes and 2 non-binding +1 votes. Thanks very much to everyone who tested!
>
> I will be continuing the release process, so we will soon have Jena 3.3.0.
>
> ---
> A. Soroka
>
> Dick Murray wrote on 5/4/17 6:10 AM:
>> +1
>>
>> mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.
>>
>> I've merged this with my fork and deployed to some of our test servers
>> (Fedora 25) which are under load but can be failed out if something goes
>> wrong...
>>
>> Dick.
>>

[RESULT] [VOTE] Release vote : Apache Jena 3.3.0

Posted by aj...@apache.org.

---
A. Soroka

sorokaaj@gmail.com wrote on 5/7/17 3:04 PM:
> Okay, folks, we have 3 binding +1 votes and no binding -1 votes and 2 non-binding +1 votes. Thanks very much to everyone who tested!
>
> I will be continuing the release process, so we will soon have Jena 3.3.0.
>
> ---
> A. Soroka
>
> Dick Murray wrote on 5/4/17 6:10 AM:
>> +1
>>
>> mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.
>>
>> I've merged this with my fork and deployed to some of our test servers
>> (Fedora 25) which are under load but can be failed out if something goes
>> wrong...
>>
>> Dick.
>>

Re: Release prob-- building Javadocs

Posted by aj...@apache.org.
Okay, at this point I am getting messages from buildbot I don't understand at all:

https://ci.apache.org/builders/jena-site-staging/builds/201/steps/compile/logs/stdio

I'm really hesitant to publish the site under these circumstances, but is that the best alternative?

---
A. Soroka

Andy Seaborne wrote on 5/8/17 12:06 PM:
> Not sure.  I don't use CMS for publishing.
>
> I publish by logging into "minotaur.apache.org" and running "publish.sh", then not view the log where possible.
>
>     Andy
>
> On 08/05/17 16:16, sorokaaj@gmail.com wrote:
>> Hm. After running into the problem mentioned at
>>
>> https://cwiki.apache.org/confluence/display/JENA/Release+Process#ReleaseProcess-PublishingtheJavadoc
>>
>>
>> under "If you delete the old documentation and add the new documentation
>> in the same commit..." I did `svn mv javadoc temp ; svn commit -m
>> "Temporarily move javadoc"` as suggested there (I had to do this for the
>> last release, as well). But unexpectedly, the new build that was thereby
>> kicked off (https://ci.apache.org/builders/jena-site-staging/builds/200)
>> failed as well with
>>
>> svn: E185004: Commit failed (details follow):
>> svn: E185004: Unexpected end of svndiff input
>> program finished with exit code 1
>>
>> in the shell phase, which I haven't seen before. I'm not sure how to fix
>> this. Can I just kick off another buildbot build and hope for success
>> this time? (And if so, how would I do that?)
>>
>> ---
>> A. Soroka
>>
>>

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by so...@gmail.com.
Okay, folks, we have 3 binding +1 votes and no binding -1 votes and 2 non-binding +1 votes. Thanks very much to everyone who tested!

I will be continuing the release process, so we will soon have Jena 3.3.0.

---
A. Soroka

Dick Murray wrote on 5/4/17 6:10 AM:
> +1
>
> mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.
>
> I've merged this with my fork and deployed to some of our test servers
> (Fedora 25) which are under load but can be failed out if something goes
> wrong...
>
> Dick.
>

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by aj...@apache.org.
+1 from builds on Mac OS X 10.10.5 using Java build 1.8.0_40-ea-b22.

---
A. Soroka

Dick Murray wrote on 5/4/17 6:10 AM:
> +1
>
> mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.
>
> I've merged this with my fork and deployed to some of our test servers
> (Fedora 25) which are under load but can be failed out if something goes
> wrong...
>
> Dick.
>

Re: Jena/Fuseki nightly builds

Posted by so...@gmail.com.
It's fine to skip tests if all you are interested in is just getting some artifacts. If you do have the time, it is good practice to run them (with -Pdev 
enabled, they don't add that much time to build). It's not at all common, but sometimes we do get to catch subtle bugs because someone happened to run the tests 
in an odd environment or with unusual resourcing.

---
A. Soroka

Andy Seaborne wrote on 5/7/17 5:39 PM:
> "install" puts the the artifacts into the local maven directory space.
>
> They are are produced by "install" so if you dig them out of "target/" they are the same.
>
> "-Pdev" is faster and it only makes up to Fuseki.
>
> "-Pbootstrap" makes from a completely clean setup up to Fuseki - i.e pre-requites and -Pdev in case you are offline.
>
>     Andy
>
>
> On 07/05/17 19:09, Laura Morales wrote:
>>> You can build from the git repo locally (which is what the development
>> builds are).
>>
>> The BUILD.md says to use `mvn clean install` [1], but I tried `mvn package -DskipTests` instead. I don't know much about Java toolings, so I hope this is also
>> fine for compiling Jena/Fuseki :)  The binaries seems to work fine.
>>
>>
>> [1] https://git-wip-us.apache.org/repos/asf?p=jena.git;a=blob;f=BUILD.md;h=0f0adbfd4a52a38481ea73db30cd27a71d6c9051;hb=HEAD
>>

Re: Jena/Fuseki nightly builds

Posted by Andy Seaborne <an...@apache.org>.
"install" puts the the artifacts into the local maven directory space.

They are are produced by "install" so if you dig them out of "target/" 
they are the same.

"-Pdev" is faster and it only makes up to Fuseki.

"-Pbootstrap" makes from a completely clean setup up to Fuseki - i.e 
pre-requites and -Pdev in case you are offline.

     Andy


On 07/05/17 19:09, Laura Morales wrote:
>> You can build from the git repo locally (which is what the development
> builds are).
>
> The BUILD.md says to use `mvn clean install` [1], but I tried `mvn package -DskipTests` instead. I don't know much about Java toolings, so I hope this is also fine for compiling Jena/Fuseki :)  The binaries seems to work fine.
>
>
> [1] https://git-wip-us.apache.org/repos/asf?p=jena.git;a=blob;f=BUILD.md;h=0f0adbfd4a52a38481ea73db30cd27a71d6c9051;hb=HEAD
>

Re: Jena/Fuseki nightly builds

Posted by Laura Morales <la...@mail.com>.
> You can build from the git repo locally (which is what the development
builds are).

The BUILD.md says to use `mvn clean install` [1], but I tried `mvn package -DskipTests` instead. I don't know much about Java toolings, so I hope this is also fine for compiling Jena/Fuseki :)  The binaries seems to work fine.


[1] https://git-wip-us.apache.org/repos/asf?p=jena.git;a=blob;f=BUILD.md;h=0f0adbfd4a52a38481ea73db30cd27a71d6c9051;hb=HEAD

Re: Jena/Fuseki nightly builds

Posted by Andy Seaborne <an...@apache.org>.
Yes.

See
   http://jena.apache.org/getting_involved/index.html
for details

Note: these are not official project releases.

You can build from the git repo locally (which is what the development 
builds are).


     Andy

On 05/05/17 16:44, Laura Morales wrote:
> Are there nightly builds of Jena/Fuseki?
>
>
>
>> Sent: Thursday, May 04, 2017 at 12:10 PM
>> From: "Dick Murray" <da...@gmail.com>
>> To: users@jena.apache.org
>> Subject: Re: [VOTE] Release vote : Apache Jena 3.3.0
>> +1
>>
>> mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.
>>
>> I've merged this with my fork and deployed to some of our test servers
>> (Fedora 25) which are under load but can be failed out if something goes
>> wrong...
>>
>> Dick.

Jena/Fuseki nightly builds

Posted by Laura Morales <la...@mail.com>.
Are there nightly builds of Jena/Fuseki?
 
 

> Sent: Thursday, May 04, 2017 at 12:10 PM
> From: "Dick Murray" <da...@gmail.com>
> To: users@jena.apache.org
> Subject: Re: [VOTE] Release vote : Apache Jena 3.3.0
> +1
> 
> mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.
> 
> I've merged this with my fork and deployed to some of our test servers
> (Fedora 25) which are under load but can be failed out if something goes
> wrong...
> 
> Dick.

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by so...@gmail.com.
+1 from builds using Mac OS X 10.10.5, Java build 1.8.0_40-ea-b22

---
A. Soroka

Dick Murray wrote on 5/4/17 6:10 AM:
> +1
>
> mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.
>
> I've merged this with my fork and deployed to some of our test servers
> (Fedora 25) which are under load but can be failed out if something goes
> wrong...
>
> Dick.
>

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by Dick Murray <da...@gmail.com>.
+1

mvn install passed on Ubuntu 17.04 and CentOS 7 and Fedora 25.

I've merged this with my fork and deployed to some of our test servers
(Fedora 25) which are under load but can be failed out if something goes
wrong...

Dick.

Re: [VOTE] Release vote : Apache Jena 3.3.0

Posted by Andy Seaborne <an...@apache.org>.
> Please vote to approve this release:
>
>       [ ] +1 Approve the release
>       [ ]  0 Don't care
>       [ ] -1 Don't release, because ...

+1

Great job!

> This vote will be open to at least
>
>       17:00 UTC-04:00 (US Eastern 5PM) on Friday 5 May 2017
>



> Checking needed:
>
> + does everything work on Linux?

Source builds and passes tests

> + does everything work on MS Windows?
> + does everything work on OS X?
> + are the GPG signatures fine?

Yes

> + are the checksums correct?

Yes

> + is there a source archive?

Yes

> + can the source archive really be built?

Yes

> + is there a correct LICENSE and NOTICE file in each artifact
>         (both source and binary artifacts)?

Yes

> + does the NOTICE file contain all necessary attributions?

Yes

> + have any licenses of dependencies changed due to upgrades?
>          if so have LICENSE and NOTICE been upgraded appropriately?

Yes

jena-text-es looks good.

> + does the tag/commit in the SCM contain reproducible sources?

Yes, version number is correct