Hi Nicholas, (I've CC'd the rdflib-dev mailing list as well - so that everyone is on board!)
I've had a chat with Jörn, and come up with the following road-map: RDFLib Roadmap ------------------------ I believe lots of people are already using master in “production”, so I would like to get a 5.0-beta release ASAP. We’ve already made some big changes since 4.2.2, in particular: * We’ve removed 2.6 support * We’ve changed to have one code-base for py2 and py3 In addition I would like to merge these: * Remove SPARQLWrapper dep: https://github.com/RDFLib/rdflib/pull/744 * Remove RDFa/Microdata from core RDFLib https://github.com/RDFLib/rdflib/pull/828 * Namespace inherting from unicode: https://github.com/RDFLib/rdflib/pull/597 * Improve compute_qname: https://github.com/RDFLib/rdflib/pull/649 Further down the line : * Store context graph vs. uri fix: https://github.com/RDFLib/rdflib/pull/409 * Streaming APIs: https://github.com/RDFLib/rdflib/pull/411 * split up of core vs. extra functionlity - discussion in https://github.com/RDFLib/rdflib/issues/391 Me and Jörn will try to sit together the weekend of 27th of October, pull the trigger on a bunch of these PRs and get out a 5.0.0. Then we can try to get 5.0.1 out a bit more quickly after that :D And we don't have to be shy about going to 6.X quite soon as well - if we chose to split up into more sub-modules for instance. How does that sound? Cheers, - Gunnar On Mon, 1 Oct 2018 at 09:51, Car, Nicholas (L&W, Dutton Park) <nicholas....@csiro.au> wrote: > > Hi Gunnar, > > > > I’m keen to commit some of my time and some of my team’s to sorting open > rdflib issues and actioning open PRs for a minor rdflib release perhaps by > the end of the year to assist with the code bing up-to-date. Perhaps then we > can think about what would be needed for a 5.0 release – something I think > you and other lead devs have already got plans for – perhaps by July next > year? > > > > If we do that, perhaps we could also ask around the community for help on > this which, if we can suggest a timeline, might get interest. > > > > For a v5.0, I’m particularly keen on assessing all the various rdflib > repositories and seeing if we have, within the project, really thought about > covering all the things people might want to do with RDF in Python. We now > have a SPARQL validator tool of course, the core rdflib toolkit itself, a > couple of reasoners (mostly out of date though), ORM wrappers etc. but are > there perhaps glaring holes in Python RDF support comparted to, say, Java > that we could potentially think about repos for? > > > > Cheers, > > > > Nick > > > > > > Nicholas Car > > Senior Experimental Scientist > > CSIRO Land & Water > 41 Boggo Road, Dutton Park, QLD 4102, Australia > > E nicholas....@csiro.au M 0477 560 177 P 07 3833 5632 > > > > > > > > -- http://gromgull.net -- http://github.com/RDFLib --- You received this message because you are subscribed to the Google Groups "rdflib-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to rdflib-dev+unsubscr...@googlegroups.com. To post to this group, send email to rdflib-dev@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rdflib-dev/CAGm1ODkDV_ntuZYqZb2YG412pBviLghGG7_nfqVrwGVDJnapsQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
