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.j.dickin...@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
