[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[rdf4j-dev] Next major release
|
TLDR: I want to introduce a new branch for the upcoming 5.0.0 release so that we can start making breaking changes in order to see what code needs to be deprecated in the next minor release (4.3.0).
Hi everyone!
Belated Happy New Year!
I've started to think about how we should transition towards the next major release.
When introducing breaking changes we aim to inform developer and end users before hand by adding deprecation annotations. We are currently on version 4.2.2 and have a last minor release (4.3.0) planned before 5.0.0. So all deprecations should be in place before we release 4.3.0.
4.2.2 - Our current release
4.3.0 - Last chance to add deprecation annotations
5.0.0 - Upcoming major release
It can be challenging to be certain that all the deprecation annotations are in place before we start making our breaking changes. I propose that we create a new branch "develop-5_0_0" where we can already start making our breaking changes in order to better identify what needs to be deprecated. There will be some issues with keeping the branch in sync with develop, for instance when we add a deprecation annotation to a class on the develop branch while at the same time deleting the file from develop-5_0_0. I will do my best to keep it in sync and fix merge conflicts, but at the same time I don't want the branch to be too long lived.
Does this sound like a reasonable approach?
Cheers,
Håvard
