+1 to a release, and I would be happy to RM, provided Andy or someone else who has driven the course would be available to advise a bit. I'm going to go study the release procedures page now.
I think I missed something: why wouldn't this be 3.2.0? --- A. Soroka > On Jan 23, 2017, at 8:24 AM, Andy Seaborne <[email protected]> wrote: > > Osma - please merge JENA-1277 then. > > For the lucene upgrade, do users need to reload data? Or do they need to do > that to gain a benefit? If either of those, it feels rather close to a > release. > > "Jena 3.3.0" is my instinctive preference but I'll leave the decision to > those that know more. > > Andy > > On 23/01/17 10:20, Osma Suominen wrote: >> Hi Andy, >> >> I was hoping to get the Lucene upgrade into 3.2.0, but it's still >> stalled. There's no point in delaying the release because of that, though. >> >> JENA-1277 has not yet been merged, but I can do that if we decide to do >> a release. I was originally planning on doing the Lucene upgrade first, >> before merging JENA-1277, but they could be done in any order. >> >> -Osma >> >> >> 22.01.2017, 22:24, Andy Seaborne kirjoitti: >>> It's a little after 3 months since Jena 3.1.1 >>> >>> We have this time: >>> >>> RDF Connection >>> JENA-1267 >>> >>> Serializable for Quad/triple/Node >>> JENA-1233 >>> >>> JsonLDReader: possibility to override the @context >>> JENA-1279 >>> And jsonld-java upgarde to version 0.9.0 >>> >>> jena-spatial - no longer sorts result. >>> Big performance improvement. >>> JENA-1277 >>> >>> What else? >>> >>> What would the next release be? >>> >>> If we are moving jena-text/spatial on in the Lucene version, should we >>> call the next release 3.3.0? >>> >>> All JIRA marked as fixed in 3.2.0: >>> https://s.apache.org/uhcd >>> >>> Andy >>> >>> Adam - are you still interested in being the RM? (If you don't think you >>> have time, that's fine.) >>> >> >>
