Hi, after the not very successful calls for help [1][2], I'd like to get the attention of the project towards finally getting 3.4.0 released. This involves the whole community, also those users who want to help in addressing any of the open issues.
Actually our backlog in Jira is not that large for this milestone, see [3]. I'll go though the individual issues: * MARMOTTA-534: Long-term issue nobody wanted to spend time. So I already started to work on this issue. I already solve the backend problem. Now I'mm trying to get ti solve int he fronted, too. I expect to submit a PR later this week. * MARMOTTA-635: We' re not going to upgrade to either Sesame 2.8.x or 2.9.x. We have a GSoC student (Gustavo Mora) who is targeting RDF4J instead [4], see MARMOTTA-659. * MARMOTTA-428: we have a PR by Aaron Coburn [5], pending to be reviewed by Rupert (our OSGi expert). I can't really say much about the patch, but so far LGTM. So if I don' t hear anything from Rupert in the next week, probably I' m going to merge the PR. * MARMOTTA-623: this issue is cause by thr MARMOTTA-584 topic branch (GeoSPARQL), that we already agreed that is not going to be released with 3.4.0 given the unsolved incompatibilities with some our databases. * MARMOTTA-624: I never got it reproduced in my testing environment. So, if I don' t find a quick solution, I'm more of the opinion of shifting this to 3.5.x. * MARMOTTA-576 and MARMOTTA-577 are something the Release Manager need to take care on release preparation. And that should be ;-) These weeks I can commit more time that usual. But I' d need someone to help with some of those issues described above. Thanks. Cheers, [1] https://s.apache.org/d5Ob [2] https://s.apache.org/4aw5 [3] https://s.apache.org/marmotta-3.4.0-open-issues [4] https://s.apache.org/kz75 [5] https://github.com/apache/marmotta/pull/22
