This is a VOTE in order to release version 12.0 of the Orekit library.
Version 12.0 is a major release.
Highlights in the 12.0 release are:
Zeis model for DSST J2-squared terms
RTCM orbit and clock corrections messages
Filtering capabilities for CCSDS parsing
Central body flatness is now taken into account for eclipse detector and solar radiation pressure
Static transform for {Field} elements
Measurements can now be evaluated without derivatives
Panel dependent coefficients in BoxAndSolarArraySpacecraft
Support for new formats: EOP C04, STK ephemeris files, Rinex 3.05 and 4.0, Rinex 2 navigation messages, CCSDS ADM V2, Sinex Differential Code Bias (DCB), and full parsing of ILRS CRD files
Prediction of Earth Orientation Parameters
Change of TimeInterpolable by TimeInterpolator
New {Field} classes: StateCovariance and ImpulseManeuver
A new ssa package containing probability of collision computation methods (Laas, Alfano, Alfriend, Patera, and Chan)
Python keywords (e.g. init) are now forbidden for method naming
A torque-free attitude mode for general (non-symmetrical) body
A new model for FDOA measurements
A new API for TLE generation including a new method based on a least squares fitting
A writer for CCSDS OCM
A writer for SP3 files
Blending algorithms for orbit and covariance interpolation
That’s an oversight. When merging your contribution (your very important contribution), I forget to update the changes.xml. I apologize for that.
I updated the vote description to include it
Thank you @hankgrabowski for the test. It is a bit difficult to reproduce since it looks to depend on the OS.
As a first investigation, could you try to change the junit version in the pom.xml file from 5.10.0 to 5.9.0 and run the failing command? You can do it with develop branch.
I would like to see if your problem is due to the Junit upgrade.
I have seen one problem in a class diagram, but it is minor so should not block the release.
If you need to do another release candidate, though, it may be worth picking up the fix (it’s commit af061980 in the develop branch).
It is up to you. These are only minor checkstyle errors. I noticed them using the Eclipse checkstyle plugin, maybe it uses a more recent checkstyle version than our pom.xml? (Eclipse version: 2023-09, Eclipse Checkstyle plugin 10.10.0.202309291129).
My current feeling is to follow the CI and Sonar: if they don’t triggered any warning or error, let the vote continue.
My only comcern is about the error highlighted by @hankgrabowski. I unfortunately can’t reproduce it since everything is ok on my laptops and the CI. It looks to be specific to Apple computer. If it shall be fixed for the release, so a RC-2 will be done including the UML fix and the Javadoc fixes
I am looking at this today. I will keep you posted. I did an OS upgrade to Sonoma yesterday so actually starting with a clean slate attempt. If that still fails I will try your JUnit suggestion.
Update: I tried JUnit 5.9.0 against the latest Azul build of OpenJDK 8, 17, and 21. All of them failed in the same way :(.
I’m going to try playing with some other settings…
