JENA-162 is closable IMO - Trunk has allowed queries with FROM/FROM NAMED for some time and leaves the interpretation of that dataset up to the underlying query engine which I think is a reasonable implementation
if no-one objects I will close this out soon JENA-201 should not be a blocker for this release, it is definitely a nice to have longer term but short term I'd prefer to have a new Fuseki release sooner rather than later. Rob On Mar 12, 2012, at 4:37 AM, Andy Seaborne wrote: > On 12/03/12 10:07, Alexander Dutton wrote: >> Hi Paolo, >> >> On 12/03/12 09:37, Paolo Castagna wrote: >>> https://issues.apache.org/jira/browse/JENA-218 (major) (... a patch >>> from Alexander might come for this) >> >> I'm happy to push this further up my todo list if people feel it would >> be a useful thing to include in the release. It would make our lives >> easier here were it to be in the release, but if there's not that much >> demand for it then it needn't block. Also, I don't remember any concious >> decision to mark it as major, so I probably forgot to set that field >> appropriately. >> >>> Is any of this a blocker for a first release? >> >> ^^ > > This would be a good feature to have; IMHO, no, it's not a blocker. > > This isn't enterprise product release cycles with promised functionality on a > once-in-X-years release basic. It's more continuous. > > I was going to build the release this week (subject to finding time). > > It will help to have a versioned version. > >> >>> JENA-201, even if flagged as minor, I think it's quite important if >>> we want to successfully allow Fuseki to be deployed and used in >>> 'enterprisy' environments. >> >> Another thing that might be useful for 'enterprisy' environments would >> be Debian and/or RPM packaging, though these probably want to wait until >> after the release. (I've had a look at the Debian side, but I'm no >> expert, and dealing with non-tarball upstreams (as things are at the >> moment) is messy). > > Also good to have. > >> >> All the best, >> >> Alex > > Andy
