In my mind, although 3.0 was a major release, the actual backward incompatible changes are few, and for most users, upgrading should be very easy. This to me makes the need for continued support of 2.x less. So my current thinking is that we will stop proactively doing 2.5 patch releases, and only do them upon special request, and only if the bug fix in question is very serious in terms of either security or potential data loss.
It does mean we will need to keep the other repos around a bit longer "just in case", though I may have a look at integrating everything into the mono-repo specifically for the 2.5 branch. Not too keen to spend too much time on that though.
Cheers,
Jeen
Hi,
Beta release for 3.1.0 would indeed be useful.
Would the 3.1.0 also mark the end of 2.x ? Or would (very serious) issues still qualify for e.g. a 2.5.6 ?
Best regards
Bart
From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx>
On Behalf Of Jeen Broekstra
Sent: dinsdag 22 oktober 2019 11:34
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: [rdf4j-dev] release schedules: 3.0.2 and 3.1.0
For the
3.0.2 patch release we have a couple of bug fixes lined up. Havard, I believe you wanted to give the release script a spin? This might be an ideal opportunity. As far as I'm concerned you can do a patch release whenever you're ready.
The next minor release, 3.1.0, will require a bit more planning. This will be the first release with FedX included. That immediately means that we are blocked from doing an actual
release until the legal team complete their review (see
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20667 for current status). It is hard to judge when they will give the green light but previous experience learns that for these kinds of large contributions, it may take a few weeks.
Pending that approval, however, we are able to do milestone builds for 3.1.0 if we want - and that might actually be really useful as a sort of "beta-release" approach for integrated FedX. Given that there's still quite a few planned improvements
in progress for this release, I'm thinking we need to give ourselves some time and aim for mid-November at the earliest for a first milestone.
PS added difficulty: I will be on holiday the first two weeks of November.
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev