[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rdf4j-dev] 3.1.1 patch release today, next minor/major release scheduling
|
Minor update on this: the deployment setup in Jenkins mostly worked, except that the release-sdk job didn't properly trigger the release-ossrh job. It looks as if it doesn't pass along the version tag parameter. So I started that job manually.
Hi folks,
I'll be rolling out a 3.1.1 patch release today - there's been a couple of useful bug fixes, and I need an excuse to take the new Jenkins deployment setup for a spin on a proper release.
Regarding release planning, we should start thinking about when we want to do releases 3.2.0
3.2.0 is our next minor release. Current issues scheduled for that release are shown here:
https://github.com/eclipse/rdf4j/milestone/42 . There is not really a theme to this release, but there's several SHACL-related improvements there, as well as an RDFa parser as a feature, and a few enhancements to the FedX integration. Bart, Havard, and Andreas, could I ask each of you to comment on your personal timelines regarding these items, what you think you are interested in working on in the near future? What, from your perspective, is a reasonable date for this release (or at least a first milestone)? I typically try to work on an 8-10 week cycle for minor releases, so that would put us mid-April, but it depends on committer availability of course.
Now, a big issue (literally) is issue #1484: RDF* and SPARQL* support. It's currently marked as backward incompatible, and planned against the next major release (4.0.0). However, from what I've seen of the contributions by Pavel and Damyan sofar, it might be possible to roll this feature out as part of a minor release instead. I haven't ran personal tests myself yet, but I am tempted to make an effort to get it in a state where we can include it in a 3.2.0 release.
Thoughts?
Jeen
PS if there are issues on either the 3.2.0 or the 4.0.0 milestone that you think are no longer as pressing, don't hesitate to remove them from the milestone - I'd rather have some issues in the backlog without a milestone, than having to keep moving them to the next release every time.
