From: Rob V. <rv...@do...> - 2013-03-11 20:37:53
|
I wanted to get the release out for the end of the month so you have a couple of weeks Rob On 3/11/13 1:33 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob, > >Sure, I'd like to contribute the Configuration API changes. I had some >other tasks during the weekend but this won't take too long. What's my >deadline for this? :) > >Tom > >On Mon, Mar 11, 2013 at 8:51 PM, Rob Vesse <rv...@do...> wrote: >> Hey All >> >> Here is the current status on 1.0.0 as I see it, if anyone has anything >>else >> they want to get into 1.0.0 now would be a good time to speak up >> >> In terms of new features there are a couple of minor ones: >> >> AllegroGraphConnector now supports native SPARQL Update (tested against >> AllegroGraph 4.x on EC2) >> ITokenisingParser interface for token based parsers allows configuring >>the >> TokenQueueMode after a parser is instantiated >> TreeIndexedTripleCollection now has the option of completely >>configurable >> indices >> >> Plus there is the usual swathe of bug fixes, the only one that may be >> affecting people is that I found a bug where GROUP BY could give >>completely >> incorrect results for some kinds of query, mainly interactions with >>other >> clauses like VALUES and GRAPH. >> >> I ran a full regression suite at the end of last week including all the >> supported 3rd party stores I have access to installations of >>(everything but >> 4store right now). Apart from Dydra which appears to be completely >>broken >> (on their end and because of which I have marked DydraConnector as >>obsolete) >> everything is working fine. >> >> Documentation wise I've ported most stuff over to the BitBucket wiki >>which >> is a much nicer platform to work with and as part of that I've >> updated/rewritten/expanded various aspects. >> >> Thanks to Tom for already trawling through it and correcting a few >>typos and >> errors on my part. I have a couple more things to add/update there but >>I >> think I am mostly done. If you have time to review and point out any >> glaring omissions in the documentation or even better to add >>documentation >> yourself that would be great. >> >> Remaining work wise I have some clean up and fixes for the Toolkit to >>get in >> but otherwise I think I am done for 1.0.0. Tom do you want to sneak in >>that >> Configuration API suggestion since that seems fairly minor and very >>useful? >> >> Rob >> >> >>------------------------------------------------------------------------- >>----- >> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester >> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the >> endpoint security space. For insight on selecting the right partner to >> tackle endpoint security challenges, access the full report. >> http://p.sf.net/sfu/symantec-dev2dev >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester >Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the >endpoint security space. For insight on selecting the right partner to >tackle endpoint security challenges, access the full report. >http://p.sf.net/sfu/symantec-dev2dev >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |