[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rdf4j-dev] timeline for 3.5.0 release
|
Unless there are any objections, I'll do a 3.5.0 Milestone build this week (Thursday at the latest). There's enough merged and/or as-good-as merged stuff to warrant a milestone, and I'd like to able to test a few things in our (metaphacts) platform without having to rely on snapshots.
Havard, I think you were also considering doing a patch release this weekend. I wasn't planning on doing a 3.4.4 patch release myself but if you want pick this up, that'd be great. If you do, can you make sure to include the outstanding PR for GH-2604 (the RDF* transaction bug)?
It's currently waiting for final approval, if the build succeeds I'm happy for it to be merged (I'll merge it myself tomorrow). But I would appreciate it being included in a 3.4.4 patch release if we do one.
Cheers,
Jeen
On Fri, Oct 23, 2020, at 14:56, Jeen Broekstra wrote:
No worries Havard, as said there's no pressure on this from my end, in your own time.
Also, fwiw: there's always the option of doing a 3.5 release without the AST changes, and then just reschedule that for a 3.6 release in another few weeks. So either way we're not blocked here.
Cheers,
Jeen
On Fri, Oct 23, 2020, at 14:11, Håvard Ottestad wrote:
Hi,
In light of my previous email, off mailing-list, I’m not sure when I’ll manage to finish the new AST. That being said there is really only one thing missing and that is the support for advanced targeting with target shapes.
Could you guys give me a couple of weeks to see how things shape up? I have every intention to finish the new AST sooner rather than later!
Cheers,
Håvard
On 23 Oct 2020, at 01:15, Jeen Broekstra <jeen@xxxxxxxxxxxx> wrote:
I thought it might be good to start thinking about a timeline for a 3.5.0 release, and what should go into that release.
If we look at
the project board we can see that there are quite a few issues done, but some really big features planned for 3.5.0 (including the SHACL AST rewrite, the Elasticsearch upgrade, and the Rio character encoding fix) are not quite finished.
The Elasticsearch upgrade (#2392) is currently marked as blocked. I believe though that all CQs have been approved so the only thing stopping us from merging is, I think, some documentation on how to migrate an existing index. Bart, is that your understanding as well? I know you are currently focused on other responsibilities, do you think you will have some availability later on to help carry this over the line?
Regarding the SHACL AST rewrite, there is a massive "work in progress" pull request up. Havard, what is currently your personal timeine for getting this in a release-ready state? Can you give a ballpark estimate (no pressure, it's just so we all know what to expect)?
The Rio character encoding issue is something that has been lingering in "blocked" for a while now, I will try and put some effort into gettting that over the line this weekend. I also want to spend a little time on the recent contributions from Allesandro (and some of the followup issues flowing from that), so we have all that ready to go in a next release.
Cheers,
Jeen
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________
rdf4j-dev mailing list
_______________________________________________
rdf4j-dev mailing list
