You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Ian Dickinson <i....@gmail.com> on 2015/03/03 22:07:10 UTC
Fuseki2 UI development
Hi folks,
Firstly an apology for dropping off the radar for a while. I've been
very busy with work, so haven't been attending to dev@ emails for a
while.
Anyway, I'm picking up the reins again on the Fuseki2 UI work. I
notice that there are a number of bug reports outstanding, thanks for
those whoever contributed to them. There are also some unfinished
threads on the originally planned Fuseki2 UI capabilities (some of
which will need back-end support via the server protocol). Finally
there have been some changes that have been introduced by some of the
patches that have gone through while my attention has been elsewhere,
some of which have negatively impacted existing capabilities.
Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up
to where I'd like it to be, including closing out the new bugreps.
One of the reasons for bringing this to the list is with respect to
the forthcoming release. I can't get the outstanding work done in a
timeframe that will do anything other than delay this release. Given
my other work commitments, it's going to be O(weeks) before the work
queue that I can see on Fuseki2 is under control. We have a choice
about what to do about that. One option would be to include the
current UI as-is, but label it more clearly as an alpha release.
Another would be to decouple the new UI from this release, but aim for
another release in O(months) when Fuseki2 is up to a good standard.
There may be other options between those extremes.
Opinions?
Ian
RE: Fuseki2 UI development
Posted by Will <wi...@hotmail.com>.
+1 for that as an approach
> Date: Wed, 4 Mar 2015 10:21:47 +0000
> Subject: Re: Fuseki2 UI development
> From: rvesse@dotnetrdf.org
> To: dev@jena.apache.org
>
> I would be happy having Fuseki 2 included in 2.13.0 as an Alpha/Beta
> release
>
> I am tended to go with the "release early, release often" approach. We
> know Fuseki 2 is going to be a big change for people and that it isn't all
> going to work yet but that shouldn't stop us putting it in the hands of
> people and getting real world feedback
>
> Rob
>
> On 03/03/2015 21:07, "Ian Dickinson" <i....@gmail.com> wrote:
>
> >Hi folks,
> >Firstly an apology for dropping off the radar for a while. I've been
> >very busy with work, so haven't been attending to dev@ emails for a
> >while.
> >
> >Anyway, I'm picking up the reins again on the Fuseki2 UI work. I
> >notice that there are a number of bug reports outstanding, thanks for
> >those whoever contributed to them. There are also some unfinished
> >threads on the originally planned Fuseki2 UI capabilities (some of
> >which will need back-end support via the server protocol). Finally
> >there have been some changes that have been introduced by some of the
> >patches that have gone through while my attention has been elsewhere,
> >some of which have negatively impacted existing capabilities.
> >
> >Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up
> >to where I'd like it to be, including closing out the new bugreps.
> >
> >One of the reasons for bringing this to the list is with respect to
> >the forthcoming release. I can't get the outstanding work done in a
> >timeframe that will do anything other than delay this release. Given
> >my other work commitments, it's going to be O(weeks) before the work
> >queue that I can see on Fuseki2 is under control. We have a choice
> >about what to do about that. One option would be to include the
> >current UI as-is, but label it more clearly as an alpha release.
> >Another would be to decouple the new UI from this release, but aim for
> >another release in O(months) when Fuseki2 is up to a good standard.
> >There may be other options between those extremes.
> >
> >Opinions?
> >
> >Ian
>
>
>
>
Re: Fuseki2 UI development
Posted by Rob Vesse <rv...@dotnetrdf.org>.
I would be happy having Fuseki 2 included in 2.13.0 as an Alpha/Beta
release
I am tended to go with the "release early, release often" approach. We
know Fuseki 2 is going to be a big change for people and that it isn't all
going to work yet but that shouldn't stop us putting it in the hands of
people and getting real world feedback
Rob
On 03/03/2015 21:07, "Ian Dickinson" <i....@gmail.com> wrote:
>Hi folks,
>Firstly an apology for dropping off the radar for a while. I've been
>very busy with work, so haven't been attending to dev@ emails for a
>while.
>
>Anyway, I'm picking up the reins again on the Fuseki2 UI work. I
>notice that there are a number of bug reports outstanding, thanks for
>those whoever contributed to them. There are also some unfinished
>threads on the originally planned Fuseki2 UI capabilities (some of
>which will need back-end support via the server protocol). Finally
>there have been some changes that have been introduced by some of the
>patches that have gone through while my attention has been elsewhere,
>some of which have negatively impacted existing capabilities.
>
>Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up
>to where I'd like it to be, including closing out the new bugreps.
>
>One of the reasons for bringing this to the list is with respect to
>the forthcoming release. I can't get the outstanding work done in a
>timeframe that will do anything other than delay this release. Given
>my other work commitments, it's going to be O(weeks) before the work
>queue that I can see on Fuseki2 is under control. We have a choice
>about what to do about that. One option would be to include the
>current UI as-is, but label it more clearly as an alpha release.
>Another would be to decouple the new UI from this release, but aim for
>another release in O(months) when Fuseki2 is up to a good standard.
>There may be other options between those extremes.
>
>Opinions?
>
>Ian
Re: Fuseki2 UI development
Posted by Ian Dickinson <i....@gmail.com>.
On Thu, Mar 5, 2015 at 1:26 PM, Andy Seaborne <an...@apache.org> wrote:
> Works for me on a clean database, then loaded with some data with tdbloader:
>
> Use Fusek2i development:
I just tried again, with a clean rebuild of the TDB image. The good
news: the transaction problem has gone away of its own accord. The bad
news: the transaction problem has gone away of its own accord. In
particular, it's a bit concerning because, once it has been
initialised by tdbloader2, that particular store is only used in
read-only mode by one process.
But, nothing else to do atm other than note that it happened.
Ian
Re: Fuseki2 UI development
Posted by Andy Seaborne <an...@apache.org>.
>> I have just checked and "it works for me" except that they get placed in the
>> wrong directory. No UI issue. Recorded as JENA-894.
>
> Hmm. I get the following on the Fuseki console:
>
> 2015-03-05 11:14:02] Admin INFO [8] POST http://localhost:3030/$/backup/ds
> [2015-03-05 11:14:02] Admin INFO [8] Backup dataset /ds
> [2015-03-05 11:14:02] Server INFO Task : 1 : backup
> [2015-03-05 11:14:02] Server INFO [Task 1] starts : backup
> [2015-03-05 11:14:02] Admin INFO [8] 200 OK (41 ms)
> [2015-03-05 11:14:02] Backup INFO [8] >>>> Start backup /ds ->
> backups/ds_2015-03-05_11-14-02
> [2015-03-05 11:14:02] Server INFO [9] GET http://localhost:3030/$/tasks/1
> [2015-03-05 11:14:02] Server INFO [9] Task 1
> [2015-03-05 11:14:02] Server INFO [9] 200 OK (2 ms)
> [2015-03-05 11:14:02] Backup INFO [8] **** Exception in backup
> com.hp.hpl.jena.tdb.transaction.TDBTransactionException: Not in a transaction
> at com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:106)
> at com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:1)
> at com.hp.hpl.jena.sparql.core.DatasetGraphTrackActive.getDefaultGraph(DatasetGraphTrackActive.java:91)
> at org.apache.jena.riot.system.RiotLib.prefixMap(RiotLib.java:257)
> at org.apache.jena.riot.RDFDataMgr.write$(RDFDataMgr.java:1331)
> at org.apache.jena.riot.RDFDataMgr.write(RDFDataMgr.java:1205)
> at org.apache.jena.riot.RDFDataMgr.write(RDFDataMgr.java:1195)
> at org.apache.jena.fuseki.mgt.Backup.backup(Backup.java:82)
> at org.apache.jena.fuseki.mgt.ActionBackup$BackupTask.run(ActionBackup.java:76)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at org.apache.jena.fuseki.async.AsyncTask.call(AsyncTask.java:94)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> [2015-03-05 11:14:02] Server INFO [Task 1] finishes : backup
> [2015-03-05 11:14:02] Server INFO [10] GET http://localhost:3030/$/tasks/1
> [2015-03-05 11:14:02] Server INFO [10] Task 1
> [2015-03-05 11:14:02] Server INFO [10] 200 OK (2 ms)
>
>
> Any suggestions on diagnostics to probe why my setup might be
> different to yours? I started fuseki with
>
> --loc=/var/lib/tdb/ea/rbwd /ds
Works for me on a clean database, then loaded with some data with tdbloader:
Use Fusek2i development:
(with timestamps removed):
Server INFO Running in read-only mode for /ds
Server INFO Fuseki 2.0.0-SNAPSHOT ${maven.build.timestamp}
Config INFO FUSEKI_HOME=/home/afs/Jena/jena-fuseki2/jena-fuseki-core
Config INFO FUSEKI_BASE=/home/afs/tmp/run
Servlet INFO Initializing Shiro environment
Config INFO Shiro file: file:///home/afs/tmp/run/shiro.ini
Config INFO Template file: templates/config-tdb-dir
Config INFO TDB dataset: directory=DB
Builder INFO Service: TDB /ds
Config INFO Register: /ds
Server INFO Started 2015/03/05 13:21:16 GMT on port 3030
Admin INFO [1] GET http://localhost:3030/$/server
Admin INFO [1] 200 OK (7 ms)
Admin INFO [2] POST http://localhost:3030/$/backup/ds
Admin INFO [2] Backup dataset /ds
Server INFO Task : 1 : backup
Server INFO [Task 1] starts : backup
Backup INFO [2] >>>> Start backup /ds ->
/home/afs/tmp/run/backups/ds_2015-03-05_13-21-25
Admin INFO [2] 200 OK (3 ms)
Server INFO [3] GET http://localhost:3030/$/tasks/1
Backup INFO [2] <<<< Finish backup /ds ->
/home/afs/tmp/run/backups/ds_2015-03-05_13-21-25
Server INFO [3] Task 1
Server INFO [3] 200 OK (6 ms)
Server INFO [Task 1] finishes : backup
>
>
>>> How long do I have before we freeze the release?
>>
>>
>> -5 days :-)
>
> OK. /me needs to pay more attention!
>
> Ian
>
Re: Fuseki2 UI development
Posted by Ian Dickinson <i....@gmail.com>.
Hi Andy,
On Thu, Mar 5, 2015 at 10:54 AM, Andy Seaborne <an...@apache.org> wrote:
>> Some of the currently non-working features were previously working.
>
>
> What specifically? On the query page or elsewhere?
>
> There are different changes from different origins - I'm trying to pin down
> which we're talking about in case it's a systematic, and single root, issue.
I think the Yasqe update complicates the UX of the query page (esp pivot
tables, but there's a separate discussion on that). Yasqe also removed
codemirror,
which took out the validation pages, which were then removed as broken links.
Some other minor things, but tbh some of those might have been lingering issues
from the previous round of work.
>> It also looks like backup is currently not working due to a
>> transaction problem. I'll need to confirm that, will add a Jira if
>> necessary.
>
>
> I have just checked and "it works for me" except that they get placed in the
> wrong directory. No UI issue. Recorded as JENA-894.
Hmm. I get the following on the Fuseki console:
2015-03-05 11:14:02] Admin INFO [8] POST http://localhost:3030/$/backup/ds
[2015-03-05 11:14:02] Admin INFO [8] Backup dataset /ds
[2015-03-05 11:14:02] Server INFO Task : 1 : backup
[2015-03-05 11:14:02] Server INFO [Task 1] starts : backup
[2015-03-05 11:14:02] Admin INFO [8] 200 OK (41 ms)
[2015-03-05 11:14:02] Backup INFO [8] >>>> Start backup /ds ->
backups/ds_2015-03-05_11-14-02
[2015-03-05 11:14:02] Server INFO [9] GET http://localhost:3030/$/tasks/1
[2015-03-05 11:14:02] Server INFO [9] Task 1
[2015-03-05 11:14:02] Server INFO [9] 200 OK (2 ms)
[2015-03-05 11:14:02] Backup INFO [8] **** Exception in backup
com.hp.hpl.jena.tdb.transaction.TDBTransactionException: Not in a transaction
at com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:106)
at com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:1)
at com.hp.hpl.jena.sparql.core.DatasetGraphTrackActive.getDefaultGraph(DatasetGraphTrackActive.java:91)
at org.apache.jena.riot.system.RiotLib.prefixMap(RiotLib.java:257)
at org.apache.jena.riot.RDFDataMgr.write$(RDFDataMgr.java:1331)
at org.apache.jena.riot.RDFDataMgr.write(RDFDataMgr.java:1205)
at org.apache.jena.riot.RDFDataMgr.write(RDFDataMgr.java:1195)
at org.apache.jena.fuseki.mgt.Backup.backup(Backup.java:82)
at org.apache.jena.fuseki.mgt.ActionBackup$BackupTask.run(ActionBackup.java:76)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at org.apache.jena.fuseki.async.AsyncTask.call(AsyncTask.java:94)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2015-03-05 11:14:02] Server INFO [Task 1] finishes : backup
[2015-03-05 11:14:02] Server INFO [10] GET http://localhost:3030/$/tasks/1
[2015-03-05 11:14:02] Server INFO [10] Task 1
[2015-03-05 11:14:02] Server INFO [10] 200 OK (2 ms)
Any suggestions on diagnostics to probe why my setup might be
different to yours? I started fuseki with
--loc=/var/lib/tdb/ea/rbwd /ds
>> How long do I have before we freeze the release?
>
>
> -5 days :-)
OK. /me needs to pay more attention!
Ian
Re: Fuseki2 UI development
Posted by Andy Seaborne <an...@apache.org>.
On 05/03/15 01:58, Ian Dickinson wrote:
> On Wed, Mar 4, 2015 at 10:00 AM, Andy Seaborne <an...@apache.org> wrote:
>> The release has other significant new work in Elepahs and it has the OSGi
>> packaging.
> OK.
>
>> There have been two kinds of patches:
>> 1/ Reworking the query page
>> 2/ Commenting out non-working features like "active" and "remove"
> Some of the currently non-working features were previously working.
What specifically? On the query page or elsewhere?
There are different changes from different origins - I'm trying to pin
down which we're talking about in case it's a systematic, and single
root, issue.
> But that's ok, I have fixes in train.
>
> It also looks like backup is currently not working due to a
> transaction problem. I'll need to confirm that, will add a Jira if
> necessary.
I have just checked and "it works for me" except that they get placed in
the wrong directory. No UI issue. Recorded as JENA-894.
>> Several people on users@ have been using it and the feedback has been
>> positive, at least I though it was.
> Sorry, I'm partly caught up on dev@, not even attempted users@ yet :(
>
>> The test question I have is:
>>
>> "Is it better than the Fuseki1 UI?"
>>
>> I think it is - the capability of being about to create databases and load
>> data via the UI in a running server makes the "fire up and do stuff" task
>> much nicer.
> OK.
>
>> Is it finished? No. Is it ever finished? This version does not have to be
>> a complete version. "Release early, release often", get feed back, engage
>> users and contributors.
> OK.
>
> How long do I have before we freeze the release?
-5 days :-)
We're only here because when I tried to build a release, I came across a
problem with the release plugin. Had that not arisen, the vote would
have been started and finished by now.
> I have a client
> deadline tomorrow (which is why it's 2am and I'm still at my desk, le
> sigh) and I'm at JQueryUK on Friday. So realistically it's going to be
> Saturday before I can knock off any more of the outstanding bugs and
> push my current set of changes. It would be nice to investigate the
> backup issue, because that's one of the more useful new features of
> F2.
I can do the backup issue. The UI worked for me.
This release isn't a "now or never" matter - we can crank a new release
quite soon afterwards quite easily. I'll offer to RM any bug fix
release that is needed.
Andy
(I'll send separate email to draw together the various release process
strands)
>
> Ian
>
Re: Fuseki2 UI development
Posted by Ian Dickinson <i....@gmail.com>.
On Wed, Mar 4, 2015 at 10:00 AM, Andy Seaborne <an...@apache.org> wrote:
> The release has other significant new work in Elepahs and it has the OSGi
> packaging.
OK.
> There have been two kinds of patches:
> 1/ Reworking the query page
> 2/ Commenting out non-working features like "active" and "remove"
Some of the currently non-working features were previously working.
But that's ok, I have fixes in train.
It also looks like backup is currently not working due to a
transaction problem. I'll need to confirm that, will add a Jira if
necessary.
> Several people on users@ have been using it and the feedback has been
> positive, at least I though it was.
Sorry, I'm partly caught up on dev@, not even attempted users@ yet :(
> The test question I have is:
>
> "Is it better than the Fuseki1 UI?"
>
> I think it is - the capability of being about to create databases and load
> data via the UI in a running server makes the "fire up and do stuff" task
> much nicer.
OK.
> Is it finished? No. Is it ever finished? This version does not have to be
> a complete version. "Release early, release often", get feed back, engage
> users and contributors.
OK.
How long do I have before we freeze the release? I have a client
deadline tomorrow (which is why it's 2am and I'm still at my desk, le
sigh) and I'm at JQueryUK on Friday. So realistically it's going to be
Saturday before I can knock off any more of the outstanding bugs and
push my current set of changes. It would be nice to investigate the
backup issue, because that's one of the more useful new features of
F2.
Ian
Re: Fuseki2 UI development
Posted by Andy Seaborne <an...@apache.org>.
Hi Ian,
The release has other significant new work in Elepahs and it has the
OSGi packaging.
Can you say more about the issues you see in the interface? Not being
much of a UI person, I would better understand your points if you could
be more specific. I put through the patches and didn't see that existing
capabilities have been affected and that wasn't my intention.
There have been two kinds of patches:
1/ Reworking the query page
2/ Commenting out non-working features like "active" and "remove"
Several people on users@ have been using it and the feedback has been
positive, at least I though it was.
The test question I have is:
"Is it better than the Fuseki1 UI?"
I think it is - the capability of being about to create databases and
load data via the UI in a running server makes the "fire up and do
stuff" task much nicer.
Is it finished? No. Is it ever finished? This version does not have to
be a complete version. "Release early, release often", get feed back,
engage users and contributors.
Andy
On 03/03/15 21:07, Ian Dickinson wrote:
> Hi folks,
> Firstly an apology for dropping off the radar for a while. I've been
> very busy with work, so haven't been attending to dev@ emails for a
> while.
>
> Anyway, I'm picking up the reins again on the Fuseki2 UI work. I
> notice that there are a number of bug reports outstanding, thanks for
> those whoever contributed to them. There are also some unfinished
> threads on the originally planned Fuseki2 UI capabilities (some of
> which will need back-end support via the server protocol). Finally
> there have been some changes that have been introduced by some of the
> patches that have gone through while my attention has been elsewhere,
> some of which have negatively impacted existing capabilities.
>
> Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up
> to where I'd like it to be, including closing out the new bugreps.
>
> One of the reasons for bringing this to the list is with respect to
> the forthcoming release. I can't get the outstanding work done in a
> timeframe that will do anything other than delay this release. Given
> my other work commitments, it's going to be O(weeks) before the work
> queue that I can see on Fuseki2 is under control. We have a choice
> about what to do about that. One option would be to include the
> current UI as-is, but label it more clearly as an alpha release.
> Another would be to decouple the new UI from this release, but aim for
> another release in O(months) when Fuseki2 is up to a good standard.
> There may be other options between those extremes.
>
> Opinions?
>
> Ian
>
Re: Fuseki2 UI development
Posted by Andy Seaborne <an...@apache.org>.
> perhaps some note about that and a note that you
> can still configure Fuseki the 'classic' way with assembler files to
> customize. (Where? In the UI itself?)
No worry here - that's in the documentation:
http://jena.staging.apache.org/documentation/fuseki2/fuseki-run.html
Andy
On 04/03/15 09:54, Stian Soiland-Reyes wrote:
> I thought we were in agreement that Fuseki 2.0.0 should go out
> together with Jena 2.13.0 in whatever shape it is now, as it is very
> much in a usable state, even if there are many features we would love
> to have in the UI. Release Early, Release Often mantra. :)
>
>
> I think we don't need to label the whole download as alpha,
> server-wise Fuseki 2 is as good as (or better) than Fuseki 1. Only the
> new UI is 'alpha' - perhaps some note about that and a note that you
> can still configure Fuseki the 'classic' way with assembler files to
> customize. (Where? In the UI itself?)
>
>
> I pushed for this release to disable some of the buttons that didn't
> do anything or didn't quite work - obviously they should go back in
> when they do :)
>
> I would be willing to help out on getting those things working again
> (e.g. the Remove button is quite essential) - but would love some kind
> of overview architecture description of the javascript code base as I
> still don't quite understand how the frameworks really work there..
> (Too long in Java land)
>
>
>
> On 3 March 2015 at 21:07, Ian Dickinson <i....@gmail.com> wrote:
>> Hi folks,
>> Firstly an apology for dropping off the radar for a while. I've been
>> very busy with work, so haven't been attending to dev@ emails for a
>> while.
>>
>> Anyway, I'm picking up the reins again on the Fuseki2 UI work. I
>> notice that there are a number of bug reports outstanding, thanks for
>> those whoever contributed to them. There are also some unfinished
>> threads on the originally planned Fuseki2 UI capabilities (some of
>> which will need back-end support via the server protocol). Finally
>> there have been some changes that have been introduced by some of the
>> patches that have gone through while my attention has been elsewhere,
>> some of which have negatively impacted existing capabilities.
>>
>> Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up
>> to where I'd like it to be, including closing out the new bugreps.
>>
>> One of the reasons for bringing this to the list is with respect to
>> the forthcoming release. I can't get the outstanding work done in a
>> timeframe that will do anything other than delay this release. Given
>> my other work commitments, it's going to be O(weeks) before the work
>> queue that I can see on Fuseki2 is under control. We have a choice
>> about what to do about that. One option would be to include the
>> current UI as-is, but label it more clearly as an alpha release.
>> Another would be to decouple the new UI from this release, but aim for
>> another release in O(months) when Fuseki2 is up to a good standard.
>> There may be other options between those extremes.
>>
>> Opinions?
>>
>> Ian
>
>
>
Re: Fuseki2 UI development
Posted by Stian Soiland-Reyes <st...@apache.org>.
I thought we were in agreement that Fuseki 2.0.0 should go out
together with Jena 2.13.0 in whatever shape it is now, as it is very
much in a usable state, even if there are many features we would love
to have in the UI. Release Early, Release Often mantra. :)
I think we don't need to label the whole download as alpha,
server-wise Fuseki 2 is as good as (or better) than Fuseki 1. Only the
new UI is 'alpha' - perhaps some note about that and a note that you
can still configure Fuseki the 'classic' way with assembler files to
customize. (Where? In the UI itself?)
I pushed for this release to disable some of the buttons that didn't
do anything or didn't quite work - obviously they should go back in
when they do :)
I would be willing to help out on getting those things working again
(e.g. the Remove button is quite essential) - but would love some kind
of overview architecture description of the javascript code base as I
still don't quite understand how the frameworks really work there..
(Too long in Java land)
On 3 March 2015 at 21:07, Ian Dickinson <i....@gmail.com> wrote:
> Hi folks,
> Firstly an apology for dropping off the radar for a while. I've been
> very busy with work, so haven't been attending to dev@ emails for a
> while.
>
> Anyway, I'm picking up the reins again on the Fuseki2 UI work. I
> notice that there are a number of bug reports outstanding, thanks for
> those whoever contributed to them. There are also some unfinished
> threads on the originally planned Fuseki2 UI capabilities (some of
> which will need back-end support via the server protocol). Finally
> there have been some changes that have been introduced by some of the
> patches that have gone through while my attention has been elsewhere,
> some of which have negatively impacted existing capabilities.
>
> Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up
> to where I'd like it to be, including closing out the new bugreps.
>
> One of the reasons for bringing this to the list is with respect to
> the forthcoming release. I can't get the outstanding work done in a
> timeframe that will do anything other than delay this release. Given
> my other work commitments, it's going to be O(weeks) before the work
> queue that I can see on Fuseki2 is under control. We have a choice
> about what to do about that. One option would be to include the
> current UI as-is, but label it more clearly as an alpha release.
> Another would be to decouple the new UI from this release, but aim for
> another release in O(months) when Fuseki2 is up to a good standard.
> There may be other options between those extremes.
>
> Opinions?
>
> Ian
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/0000-0001-9842-9718