Yes particularly in the context of components like ARQ there are a lot of bug and performance fixes plus other minor enhancements that I and others have worked on.
For the record ARQ hasn't received a new release in 6 months so while there are clearly some TDB issues to be resolved it is best to get a release out the door to get the fixes to that and other components into the hands of users. More frequent releases should hopefully be a lot easier now we are a TLP and don't have quite so many hurdles to jump through to get our release done (we now only have to hold a successful release vote ourselves rather than also having to pass through the Incubator process) Rob Rob Vesse -- YarcData.com -- A Division of Cray Inc Software Engineer, Bay Area m: 925.960.3941 | o: 925.264.4729 | @: [email protected] | Skype: rvesse 6210 Stoneridge Mall Rd | Suite 120 | Pleasanton CA, 94588 On 6/13/12 3:34 PM, "Andy Seaborne" <[email protected]> wrote: >> PS: Is this concern not a good reason to delay the release, at least >> until it is understood? > >See http://s.apache.org/pt and also the fact there may well be another >release quite soon for, if nothing else, a better NodeTableTrans. > >There are many things in the release - non-TDB bug fixes and >improvements, close tracking of SPARQL 1.1, etc etc. And for TDB, >better protection of data due to fixes since 0.9.0-incubating. > >And the release doesn't say "-incubating" > >So, in the spirit of continuous improvement, I think the release should >go ahead, and I have sent the VOTE message. > >Release early, release often. > > Andy > >
