Proposal to release Orekit 13.1.1

Orekit development
1

Hi all,

Currently, they are 11 issues in the backlog of Orekit 13.1.1:

  • 5 documentation issues
  • 1 release process issue
  • 5 source code issues

10 of these issues are already resolved! So, what do you think of this program for a 13.1.1 release?
Do you want to add additional issues in the backlog?

This patch should wait for the Hipparchus 4.0.2 patch to benefit from this new Hipparchus version.

Best regards,
Bryan

2 Likes
2

Always the same mantra for me: Release early, release often. :star_struck:

3

It seems I am the one late here with issue 1798.

This issue is part of my day job, I’ll take care of it probably next week.

4

I’ve added an issue (#1816) on performance of STM propagation with “many” forces (10-20).
Working on it.

Edit: done

Cheers,
Romain.

5

No problem with the two opened issues. I still need to patch Hipparchus.

6

If there is still time to include another patch, I created a small fix for some exception messages: Fix exception messages to use FieldElement.getReal (!944) · Merge requests · Orekit / Orekit · GitLab

7

And this one two:

Fix #1818 (!943) · Merge requests · Orekit / Orekit · GitLab

8

Thanks to Hipparchus, there is time :slightly_smiling_face:

2 Likes
10

The issues I wanted to fix about ionosphere have been fixed.

11

I’ll probably have another fix to add. I have to check it internally before

12

Hipparchus 4.0.2 has been released and I merged everything I wanted to do!

I think that all the issues are fixed. As a result, the release process could start.

Two information:

  • We need to increase to coverage by about 1%
  • I will be off for the next 10 days, so I can’t handle the release before the 22 of September. If anybody wants the handle it, fill free

Bryan

13

Sounds good, I’ve started a branch for the coverage.

Edit: the 95% is reached

Cheers

1 Like
14

FYI I’ve started the release process

2 Likes
15

Hi folks,

I’m almost done with the release.
But I don’t think I have the rights to create a tag on the GitHub mirror.

Cheers,
Romain.

16

I don’t have the credentials to grant you these rights, because the GitHub Orekit mirror is managed directly by CS.
@sdinot could you do that?

17

I just sent you an invitation to join the team.

18

The tag is automatically created when the repository is synchronized. The only action to be performed is to create the release.

19

Thank you Sebastien, it’s all good now

1 Like
20

About the Github mirror, it seems to keep some branches that were deleted on Gitlab. For example issue-1806. Why would that be?

21

It seems that branch deletion on mirror repositories is not working. I found several topics opened on GitLab forum about this. So I have just manually deleted a large number of obsolete branches.