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 2017/11/25 23:02:10 UTC
Jena 3.6.0?
The bug in Fuseki that causes UI uploads to fail, and some other UI
issues, is a bit annoying.
Is there the energy and time to vote on a 3.6.0 release if I build one?
Please respond if you'll be able to vote in the next few weeks.
If there is - from our experience last time, we can test the latest
development builds now, before a formal VOTE which will shorten the time
in case there is any problems to address.
Andy
The build is complaining about a Shiro issue - this is harmless and a
problem somewhere in the Fuseki tests. Some state is getting initialized
twice. It does not happen when Fuseki is run nor does it cause any
tests to fail. It happens because of the 1.2.4->1.4.0 Shiro upgrade ;
it comes in at 1.2.6 -> 1.3.0. Solution: ship with 1.2.6
"""
[...] IniRealm WARN Users or Roles are already populated. Configured
Ini instance will be ignored.
"""
Andy
Re: Jena 3.6.0?
Posted by Rob Vesse <rv...@dotnetrdf.org>.
Yes, I think #315 can be merged as-is and we can improve the implementation later to make it more flexible
Rob
On 27/11/2017, 13:10, "Andy Seaborne" <an...@apache.org> wrote:
Testing the Fuseki fixes has been done - Laura Morales has used the
development build to check out the fixes and confirmed they are fixed.
The Jenkins job, other than the Shiro issue, is building cleanly. There
are no changes around OS issues except TDB2 fixes (and TDB2 is
"experimental").
More testing is always good but it takes time. The minimum is some
testing and 3 +1 votes on process and legal; after that more is better
and I'd say the criteria is "is it better than 3.5.0?", not some notion
of "perfect".
If we have this week before a release can start, some final things for
3.6.0: (this is 3.6.0 so a few actual changes can happen, not a 3.5.1)
1/ The jena-text documentation improvements
2/ Downgrade shiro to 1.2.6
3/ riot: status code on warnings (#315)
4/ Ideally, dataset assembler (#314) [might be too tight for time].
Anything else?
Rob - I can merge #315 and we can sort out the implementation stuff later.
Andy
On 25/11/17 23:45, ajs6f wrote:
> Ditto, except for me it's the 8th.
>
> ajs6f
>
>> On Nov 25, 2017, at 6:12 PM, Bruno P. Kinoshita <br...@yahoo.com.br.INVALID> wrote:
>>
>> I can run the build and verify signatures any day in the next weeks. Just not much time to properly test Fuseki and review changes until after Dec 3rd.
>> CheersBruno
>>
>> From: Andy Seaborne <an...@apache.org>
>> To: "dev@jena.apache.org" <de...@jena.apache.org>
>> Sent: Sunday, 26 November 2017 12:02 PM
>> Subject: Jena 3.6.0?
>>
>> The bug in Fuseki that causes UI uploads to fail, and some other UI
>> issues, is a bit annoying.
>>
>> Is there the energy and time to vote on a 3.6.0 release if I build one?
>> Please respond if you'll be able to vote in the next few weeks.
>>
>> If there is - from our experience last time, we can test the latest
>> development builds now, before a formal VOTE which will shorten the time
>> in case there is any problems to address.
>>
>> Andy
>>
>> The build is complaining about a Shiro issue - this is harmless and a
>> problem somewhere in the Fuseki tests. Some state is getting initialized
>> twice. It does not happen when Fuseki is run nor does it cause any
>> tests to fail. It happens because of the 1.2.4->1.4.0 Shiro upgrade ;
>> it comes in at 1.2.6 -> 1.3.0. Solution: ship with 1.2.6
>>
>> """
>> [...] IniRealm WARN Users or Roles are already populated. Configured
>> Ini instance will be ignored.
>> """
>>
>> Andy
>>
>>
>>
>
Re: Jena 3.6.0?
Posted by Andy Seaborne <an...@apache.org>.
Status of 3.6.0:
The required changes to revert PR#314 that held up progress have been
done so this is now unblocked.
The fix for jena-text has also been applied. PR#325.
There are a couple of outstanding PRs:
#327 - this adds Node_Triple and Node_Graph as hooks for
experimentation. Unsupported!
It makes it possible to do RDF* (see PR#299) in independent development
a separate module. It icludes Node_graph as well (for completeness)
This should make no difference to anything else.
#328 - some special case datasets, like a sink dataset and also an
immutable empty dataset. It also updates DatasetGraphOne to work with
transactions.
With those, I hope to find the time to do the release "soon".
(#316 - service extensibility for Fuseki2 is too radical for this release.)
Andy
Re: Jena 3.6.0?
Posted by ajs6f <aj...@apache.org>.
Right, I just wouldn't want to make 3.6.0 wait on it if the other stuff gets done.
ajs6f
> On Nov 27, 2017, at 9:51 AM, Andy Seaborne <an...@apache.org> wrote:
>
>
>
> On 27/11/17 14:30, ajs6f wrote:
>> Comments inline...
>> ajs6f
>>> On Nov 27, 2017, at 8:10 AM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>> ...
>>> 1/ The jena-text documentation improvements
>> Is this required for or by a release? Can we not do this independently?
>
> Required? No.
>
> It needs doing and the website gets updated on release.
>
> Andy
Re: Jena 3.6.0?
Posted by Andy Seaborne <an...@apache.org>.
On 27/11/17 14:30, ajs6f wrote:
> Comments inline...
>
> ajs6f
>
>> On Nov 27, 2017, at 8:10 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>> ...
>> 1/ The jena-text documentation improvements
>
> Is this required for or by a release? Can we not do this independently?
Required? No.
It needs doing and the website gets updated on release.
Andy
Re: Jena 3.6.0?
Posted by ajs6f <aj...@apache.org>.
Comments inline...
ajs6f
> On Nov 27, 2017, at 8:10 AM, Andy Seaborne <an...@apache.org> wrote:
>
> ...
> 1/ The jena-text documentation improvements
Is this required for or by a release? Can we not do this independently?
> 2/ Downgrade shiro to 1.2.6
> 3/ riot: status code on warnings (#315)
+1 to merging; I would ideally like to confirm the fix with Ian Dickinson before closing the ticket.
> 4/ Ideally, dataset assembler (#314) [might be too tight for time].
Waiting on feedback from Andy (and anyone else who might be interested).
> Anything else?
1391 is still hanging, but with a release this close I don't think I can write enough tests before then to feel comfortable sending a PR, so let's leave it be.
>
> Rob - I can merge #315 and we can sort out the implementation stuff later.
>
> Andy
>
> On 25/11/17 23:45, ajs6f wrote:
>> Ditto, except for me it's the 8th.
>> ajs6f
>>> On Nov 25, 2017, at 6:12 PM, Bruno P. Kinoshita <br...@yahoo.com.br.INVALID> wrote:
>>>
>>> I can run the build and verify signatures any day in the next weeks. Just not much time to properly test Fuseki and review changes until after Dec 3rd.
>>> CheersBruno
>>>
>>> From: Andy Seaborne <an...@apache.org>
>>> To: "dev@jena.apache.org" <de...@jena.apache.org>
>>> Sent: Sunday, 26 November 2017 12:02 PM
>>> Subject: Jena 3.6.0?
>>>
>>> The bug in Fuseki that causes UI uploads to fail, and some other UI
>>> issues, is a bit annoying.
>>>
>>> Is there the energy and time to vote on a 3.6.0 release if I build one?
>>> Please respond if you'll be able to vote in the next few weeks.
>>>
>>> If there is - from our experience last time, we can test the latest
>>> development builds now, before a formal VOTE which will shorten the time
>>> in case there is any problems to address.
>>>
>>> Andy
>>>
>>> The build is complaining about a Shiro issue - this is harmless and a
>>> problem somewhere in the Fuseki tests. Some state is getting initialized
>>> twice. It does not happen when Fuseki is run nor does it cause any
>>> tests to fail. It happens because of the 1.2.4->1.4.0 Shiro upgrade ;
>>> it comes in at 1.2.6 -> 1.3.0. Solution: ship with 1.2.6
>>>
>>> """
>>> [...] IniRealm WARN Users or Roles are already populated. Configured
>>> Ini instance will be ignored.
>>> """
>>>
>>> Andy
>>>
>>>
>>>
Re: Jena 3.6.0?
Posted by Andy Seaborne <an...@apache.org>.
Testing the Fuseki fixes has been done - Laura Morales has used the
development build to check out the fixes and confirmed they are fixed.
The Jenkins job, other than the Shiro issue, is building cleanly. There
are no changes around OS issues except TDB2 fixes (and TDB2 is
"experimental").
More testing is always good but it takes time. The minimum is some
testing and 3 +1 votes on process and legal; after that more is better
and I'd say the criteria is "is it better than 3.5.0?", not some notion
of "perfect".
If we have this week before a release can start, some final things for
3.6.0: (this is 3.6.0 so a few actual changes can happen, not a 3.5.1)
1/ The jena-text documentation improvements
2/ Downgrade shiro to 1.2.6
3/ riot: status code on warnings (#315)
4/ Ideally, dataset assembler (#314) [might be too tight for time].
Anything else?
Rob - I can merge #315 and we can sort out the implementation stuff later.
Andy
On 25/11/17 23:45, ajs6f wrote:
> Ditto, except for me it's the 8th.
>
> ajs6f
>
>> On Nov 25, 2017, at 6:12 PM, Bruno P. Kinoshita <br...@yahoo.com.br.INVALID> wrote:
>>
>> I can run the build and verify signatures any day in the next weeks. Just not much time to properly test Fuseki and review changes until after Dec 3rd.
>> CheersBruno
>>
>> From: Andy Seaborne <an...@apache.org>
>> To: "dev@jena.apache.org" <de...@jena.apache.org>
>> Sent: Sunday, 26 November 2017 12:02 PM
>> Subject: Jena 3.6.0?
>>
>> The bug in Fuseki that causes UI uploads to fail, and some other UI
>> issues, is a bit annoying.
>>
>> Is there the energy and time to vote on a 3.6.0 release if I build one?
>> Please respond if you'll be able to vote in the next few weeks.
>>
>> If there is - from our experience last time, we can test the latest
>> development builds now, before a formal VOTE which will shorten the time
>> in case there is any problems to address.
>>
>> Andy
>>
>> The build is complaining about a Shiro issue - this is harmless and a
>> problem somewhere in the Fuseki tests. Some state is getting initialized
>> twice. It does not happen when Fuseki is run nor does it cause any
>> tests to fail. It happens because of the 1.2.4->1.4.0 Shiro upgrade ;
>> it comes in at 1.2.6 -> 1.3.0. Solution: ship with 1.2.6
>>
>> """
>> [...] IniRealm WARN Users or Roles are already populated. Configured
>> Ini instance will be ignored.
>> """
>>
>> Andy
>>
>>
>>
>
Re: Jena 3.6.0?
Posted by ajs6f <aj...@apache.org>.
Ditto, except for me it's the 8th.
ajs6f
> On Nov 25, 2017, at 6:12 PM, Bruno P. Kinoshita <br...@yahoo.com.br.INVALID> wrote:
>
> I can run the build and verify signatures any day in the next weeks. Just not much time to properly test Fuseki and review changes until after Dec 3rd.
> CheersBruno
>
> From: Andy Seaborne <an...@apache.org>
> To: "dev@jena.apache.org" <de...@jena.apache.org>
> Sent: Sunday, 26 November 2017 12:02 PM
> Subject: Jena 3.6.0?
>
> The bug in Fuseki that causes UI uploads to fail, and some other UI
> issues, is a bit annoying.
>
> Is there the energy and time to vote on a 3.6.0 release if I build one?
> Please respond if you'll be able to vote in the next few weeks.
>
> If there is - from our experience last time, we can test the latest
> development builds now, before a formal VOTE which will shorten the time
> in case there is any problems to address.
>
> Andy
>
> The build is complaining about a Shiro issue - this is harmless and a
> problem somewhere in the Fuseki tests. Some state is getting initialized
> twice. It does not happen when Fuseki is run nor does it cause any
> tests to fail. It happens because of the 1.2.4->1.4.0 Shiro upgrade ;
> it comes in at 1.2.6 -> 1.3.0. Solution: ship with 1.2.6
>
> """
> [...] IniRealm WARN Users or Roles are already populated. Configured
> Ini instance will be ignored.
> """
>
> Andy
>
>
>
Re: Jena 3.6.0?
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.
I can run the build and verify signatures any day in the next weeks. Just not much time to properly test Fuseki and review changes until after Dec 3rd.
CheersBruno
From: Andy Seaborne <an...@apache.org>
To: "dev@jena.apache.org" <de...@jena.apache.org>
Sent: Sunday, 26 November 2017 12:02 PM
Subject: Jena 3.6.0?
The bug in Fuseki that causes UI uploads to fail, and some other UI
issues, is a bit annoying.
Is there the energy and time to vote on a 3.6.0 release if I build one?
Please respond if you'll be able to vote in the next few weeks.
If there is - from our experience last time, we can test the latest
development builds now, before a formal VOTE which will shorten the time
in case there is any problems to address.
Andy
The build is complaining about a Shiro issue - this is harmless and a
problem somewhere in the Fuseki tests. Some state is getting initialized
twice. It does not happen when Fuseki is run nor does it cause any
tests to fail. It happens because of the 1.2.4->1.4.0 Shiro upgrade ;
it comes in at 1.2.6 -> 1.3.0. Solution: ship with 1.2.6
"""
[...] IniRealm WARN Users or Roles are already populated. Configured
Ini instance will be ignored.
"""
Andy
Re: Jena 3.6.0?
Posted by Osma Suominen <os...@helsinki.fi>.
Andy Seaborne kirjoitti 26.11.2017 klo 01:02:
> Is there the energy and time to vote on a 3.6.0 release if I build one?
> Please respond if you'll be able to vote in the next few weeks.
I should be able to test and vote after Dec 7th or so.
-Osma
--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.suominen@helsinki.fi
http://www.nationallibrary.fi
Re: Jena 3.6.0?
Posted by Rob Vesse <rv...@dotnetrdf.org>.
This week is pretty nuts and next week does not look much better so unlikely to have any bandwidth in the immediate future
Rob
On 25/11/2017, 23:02, "Andy Seaborne" <an...@apache.org> wrote:
The bug in Fuseki that causes UI uploads to fail, and some other UI
issues, is a bit annoying.
Is there the energy and time to vote on a 3.6.0 release if I build one?
Please respond if you'll be able to vote in the next few weeks.
If there is - from our experience last time, we can test the latest
development builds now, before a formal VOTE which will shorten the time
in case there is any problems to address.
Andy
The build is complaining about a Shiro issue - this is harmless and a
problem somewhere in the Fuseki tests. Some state is getting initialized
twice. It does not happen when Fuseki is run nor does it cause any
tests to fail. It happens because of the 1.2.4->1.4.0 Shiro upgrade ;
it comes in at 1.2.6 -> 1.3.0. Solution: ship with 1.2.6
"""
[...] IniRealm WARN Users or Roles are already populated. Configured
Ini instance will be ignored.
"""
Andy