Hi folks,
I would like us to have sort of a plan for the next non patch release. Shall we say that we’re targeting a major one, before the end of the year 2025?
I see that @luc you started a 14.0 milestone and a branch I think actually.
Cheers,
Romain
Yes, I started a rinex-clock-revamp branch because it introduces API incompatibilities.
I would love to have develop target 14.0 and be able to merge this branch there. Maintaining both a develop and a rinex-clock-revamp (or a develop-14) branch at the same time would be a pain. I had to do that for develop-13 for a long time and it was a nightmare.
Hello,
Good idea, late 2025 seems like a nice target. We are almost there anyway 
. We could also use this opportunity to restart the debate on the JDK version ? I don’t remember us settling on a final decision ?
Cheers,
Vincent
It’s my intention to trigger a vote with the PMC this summer if nobody else does. Originally I thought the consensus was to have 14.0 under Long Term Support in Java 1.8 with 15.X in parallel in 1.21.
However recently it was also discussed to have 13.1 as the LTV and directly 14.0 in java 21. What do you guys think is best? @Orekit-PMC
Romain.
The sooner the better, I’‘m fine with having Orekit 14.0 in java 21.
However, we have to be careful in the amount of API breaks in this version in case we also include this Java upgrade in the release. Supporting both a Java upgrade and a lot of API breaks could discourage some users.
My opinion is somewhat illegitimate in this matter, but thinking back on the discussions and frustrations expressed, I agree with Bryan.
Cool then @luc you can merge your breaking changes on develop now I guess.
Anyhow I’m in the process of merging @Ryan’s changes due to Hipparchus so we’re about to depend on the snapshot.
The rinex-clock-revamp branch has been merged into develop.
So now develop targets 14.0 as the next release.