You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2015/07/25 22:08:35 UTC
[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?
[VOTE] [RESULT] Release Jena 3.0.0 RC1
Posted by Andy Seaborne <an...@apache.org>.
The VOTE passes with 4 +1 from Bruno, Rob, Stephen and Andy, no 0 and no -1.
I'll start the release process. From experience, a few people find a
release quite quickly, so I'll ANN it on users soon.
Andy
On 25/07/15 21:08, Andy Seaborne wrote:
> 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
Re: [VOTE] Release Jena 3.0.0 RC1
Posted by Stephen Allen <sa...@apache.org>.
+1
Built and tested on Windows 10.
On Saturday, July 25, 2015, Andy Seaborne <an...@apache.org> wrote:
> 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?
>
Re: [VOTE] Release Jena 3.0.0 RC1
Posted by "Bruno P. Kinoshita" <ki...@apache.org>.
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 <an...@apache.org>
To: dev@jena.apache.org
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?
Re: [VOTE] Release Jena 3.0.0 RC1
Posted by Rob Vesse <rv...@dotnetrdf.org>.
+1
Some minor non-blocking issues which I have noted at the end
+ does everything work on Linux?
Checked tdbloader2 on a Linux 2.6 kernel to verify that fixes to JENA-977
script refactoring were working correctly
+ does everything work on MS Windows?
Not tested
+ does everything work on OS X?
Yes
Paid particular attention to testing tdbloader2
+ is the GPG signature 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?
No and N/A
+ does the tag in the SCM contain reproducible sources?
Yes
----
Non-blocking issues:
- The jena-examples module was not updated to Jena 3 package names
properly and can't be built from the binary archive. A
- tdbloader2index fails unexpectedly if it can't figure out the sort temp
directory I.e. if run in an environment where TMPDIR is not set and no
-T/--temporary-directory provided in the sort arguments. This should be a
rare corner case and is easily worked around by setting TMPDIR to some path
Both of these have already been fixed on master
Rob
On 25/07/2015 21:08, "Andy Seaborne" <an...@apache.org> wrote:
>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=53d59bd3179b
>90f41cb53969e2b64340fcb66e76
>
> 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?
Re: [VOTE] Release Jena 3.0.0 RC1
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
>
> This vote will be open to at least the end of
>
> Tuesday, 28th July 2015, 23:59 UTC
Re: [] Release Jena 3.0.0 RC1
Posted by Andy Seaborne <an...@apache.org>.
On 26/07/15 12:02, Claude Warren wrote:
> I assume the javadocs are not updated on the staging site until release is
> performed? Otherwise I am missing where the Permissions documentation is
> created (rather than the old security name)
See https://cwiki.apache.org/confluence/display/JENA/Release+Process
Updating the javadoc isn't trivial in terms of time taken (lots of bytes
to xfer) but it is a mechanical task. If anything structural has
changed, then the site content, not just the javadoc tree needs updating.
The link on the frontpage to "security" javadoc isn't part of the java
doc. Could you fix that please?
Also - javadoc/security/... then I guess its done when the javadoc is
rebuilt but I for one didn't know about that.
I thought I had a shell script to sort out the javadoc which I can't
find ATM (but then I'm not on my usual machine)
Andy
from the middle of the Exmoor National Park (UK)
PS If you could do JENA-993 - you have JIRA rights.
>
> On Sat, Jul 25, 2015 at 10:00 PM, Andy Seaborne <an...@apache.org> wrote:
>
>> On 25/07/15 21:34, Claude Warren wrote:
>>
>>> Is there a staging documentation to go with this release?
>>>
>>
>> jena.staging.apache.org
>>
>>
>>
>>>
>>> On Sat, Jul 25, 2015 at 9:12 PM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>> On 25/07/15 21:08, Andy Seaborne wrote:
>>>>
>>>> Proposed dist/ area:
>>>>
>>>>> https://dist.apache.org/repos/dist/dev/jena/
>>>>>
>>>>>
>>>> There is a slight variation to the release process here. Instead of a
>>>> copy of the proposed dist/ area in people.apache.org, this RC used the
>>>> development svn area on dist.apache.org
>>>>
>>>> Like all projects, we have two areas dev/jena and release/jena. The
>>>> latter
>>>> is copied to www.apache.org/dist/jena.
>>>>
>>>> The advantage is that svn mv can be used to go from vote bytes to release
>>>> bytes.
>>>>
>>>> (Our release documentation hasn't not been updated yet to mention this)
>>>>
>>>> Andy
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
Re: [] Release Jena 3.0.0 RC1
Posted by Claude Warren <cl...@xenei.com>.
Yes it should. and thx
On Wed, Jul 29, 2015 at 9:40 AM, Andy Seaborne <an...@apache.org> wrote:
> The dropdown on the front page for javadoc still says "Security" - should
> that be "Permissions"? (Assuming "yes" and I will change it).
>
> Andy
>
> On 26/07/15 12:02, Claude Warren wrote:
>
>> I assume the javadocs are not updated on the staging site until release is
>> performed? Otherwise I am missing where the Permissions documentation is
>> created (rather than the old security name)
>>
>> On Sat, Jul 25, 2015 at 10:00 PM, Andy Seaborne <an...@apache.org> wrote:
>>
>> On 25/07/15 21:34, Claude Warren wrote:
>>>
>>> Is there a staging documentation to go with this release?
>>>>
>>>>
>>> jena.staging.apache.org
>>>
>>>
>>>
>>>
>>>> On Sat, Jul 25, 2015 at 9:12 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>> On 25/07/15 21:08, Andy Seaborne wrote:
>>>>
>>>>>
>>>>> Proposed dist/ area:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/jena/
>>>>>>
>>>>>>
>>>>>> There is a slight variation to the release process here. Instead of
>>>>> a
>>>>> copy of the proposed dist/ area in people.apache.org, this RC used the
>>>>> development svn area on dist.apache.org
>>>>>
>>>>> Like all projects, we have two areas dev/jena and release/jena. The
>>>>> latter
>>>>> is copied to www.apache.org/dist/jena.
>>>>>
>>>>> The advantage is that svn mv can be used to go from vote bytes to
>>>>> release
>>>>> bytes.
>>>>>
>>>>> (Our release documentation hasn't not been updated yet to mention this)
>>>>>
>>>>> Andy
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: [] Release Jena 3.0.0 RC1
Posted by Andy Seaborne <an...@apache.org>.
The dropdown on the front page for javadoc still says "Security" -
should that be "Permissions"? (Assuming "yes" and I will change it).
Andy
On 26/07/15 12:02, Claude Warren wrote:
> I assume the javadocs are not updated on the staging site until release is
> performed? Otherwise I am missing where the Permissions documentation is
> created (rather than the old security name)
>
> On Sat, Jul 25, 2015 at 10:00 PM, Andy Seaborne <an...@apache.org> wrote:
>
>> On 25/07/15 21:34, Claude Warren wrote:
>>
>>> Is there a staging documentation to go with this release?
>>>
>>
>> jena.staging.apache.org
>>
>>
>>
>>>
>>> On Sat, Jul 25, 2015 at 9:12 PM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>> On 25/07/15 21:08, Andy Seaborne wrote:
>>>>
>>>> Proposed dist/ area:
>>>>
>>>>> https://dist.apache.org/repos/dist/dev/jena/
>>>>>
>>>>>
>>>> There is a slight variation to the release process here. Instead of a
>>>> copy of the proposed dist/ area in people.apache.org, this RC used the
>>>> development svn area on dist.apache.org
>>>>
>>>> Like all projects, we have two areas dev/jena and release/jena. The
>>>> latter
>>>> is copied to www.apache.org/dist/jena.
>>>>
>>>> The advantage is that svn mv can be used to go from vote bytes to release
>>>> bytes.
>>>>
>>>> (Our release documentation hasn't not been updated yet to mention this)
>>>>
>>>> Andy
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
Re: [] Release Jena 3.0.0 RC1
Posted by Claude Warren <cl...@xenei.com>.
I assume the javadocs are not updated on the staging site until release is
performed? Otherwise I am missing where the Permissions documentation is
created (rather than the old security name)
On Sat, Jul 25, 2015 at 10:00 PM, Andy Seaborne <an...@apache.org> wrote:
> On 25/07/15 21:34, Claude Warren wrote:
>
>> Is there a staging documentation to go with this release?
>>
>
> jena.staging.apache.org
>
>
>
>>
>> On Sat, Jul 25, 2015 at 9:12 PM, Andy Seaborne <an...@apache.org> wrote:
>>
>> On 25/07/15 21:08, Andy Seaborne wrote:
>>>
>>> Proposed dist/ area:
>>>
>>>> https://dist.apache.org/repos/dist/dev/jena/
>>>>
>>>>
>>> There is a slight variation to the release process here. Instead of a
>>> copy of the proposed dist/ area in people.apache.org, this RC used the
>>> development svn area on dist.apache.org
>>>
>>> Like all projects, we have two areas dev/jena and release/jena. The
>>> latter
>>> is copied to www.apache.org/dist/jena.
>>>
>>> The advantage is that svn mv can be used to go from vote bytes to release
>>> bytes.
>>>
>>> (Our release documentation hasn't not been updated yet to mention this)
>>>
>>> Andy
>>>
>>>
>>>
>>
>>
>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: [] Release Jena 3.0.0 RC1
Posted by Andy Seaborne <an...@apache.org>.
On 25/07/15 21:34, Claude Warren wrote:
> Is there a staging documentation to go with this release?
jena.staging.apache.org
>
>
> On Sat, Jul 25, 2015 at 9:12 PM, Andy Seaborne <an...@apache.org> wrote:
>
>> On 25/07/15 21:08, Andy Seaborne wrote:
>>
>> Proposed dist/ area:
>>> https://dist.apache.org/repos/dist/dev/jena/
>>>
>>
>> There is a slight variation to the release process here. Instead of a
>> copy of the proposed dist/ area in people.apache.org, this RC used the
>> development svn area on dist.apache.org
>>
>> Like all projects, we have two areas dev/jena and release/jena. The latter
>> is copied to www.apache.org/dist/jena.
>>
>> The advantage is that svn mv can be used to go from vote bytes to release
>> bytes.
>>
>> (Our release documentation hasn't not been updated yet to mention this)
>>
>> Andy
>>
>>
>
>
Re: [] Release Jena 3.0.0 RC1
Posted by Claude Warren <cl...@xenei.com>.
Is there a staging documentation to go with this release?
On Sat, Jul 25, 2015 at 9:12 PM, Andy Seaborne <an...@apache.org> wrote:
> On 25/07/15 21:08, Andy Seaborne wrote:
>
> Proposed dist/ area:
>> https://dist.apache.org/repos/dist/dev/jena/
>>
>
> There is a slight variation to the release process here. Instead of a
> copy of the proposed dist/ area in people.apache.org, this RC used the
> development svn area on dist.apache.org
>
> Like all projects, we have two areas dev/jena and release/jena. The latter
> is copied to www.apache.org/dist/jena.
>
> The advantage is that svn mv can be used to go from vote bytes to release
> bytes.
>
> (Our release documentation hasn't not been updated yet to mention this)
>
> Andy
>
>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: [] Release Jena 3.0.0 RC1
Posted by Andy Seaborne <an...@apache.org>.
On 25/07/15 21:08, Andy Seaborne wrote:
> Proposed dist/ area:
> https://dist.apache.org/repos/dist/dev/jena/
There is a slight variation to the release process here. Instead of a
copy of the proposed dist/ area in people.apache.org, this RC used the
development svn area on dist.apache.org
Like all projects, we have two areas dev/jena and release/jena. The
latter is copied to www.apache.org/dist/jena.
The advantage is that svn mv can be used to go from vote bytes to
release bytes.
(Our release documentation hasn't not been updated yet to mention this)
Andy