Releasing patch 12.1.3

Orekit development
1

Dear all,

In preparation for a potential 12.1.3 patch, I’ve created a dedicated branch patch-12.1.3.

So if you want to fix a 12.1.3 issue could you please provide the fix on this branch so the release process can be fast and smooth for the releaser?
Also, please start your fix from branch release-12.1 so that we’re sure nothing from develop is accidentally added to the patch.

@luc, I’ve seen that you’ve patched two issues already! :+1:
Could you please cherry-pick your commits and add them to the dedicated branch?
(and also check that nothing from v12.2 sneaked there, but the changes are small so I don’t think there will be any issue here)

Cheers,
Maxime

2 Likes
2

I have cherry-picked the commits and cleaned up changes.xml.

3 Likes
3

Hello,

I think we are ready for the release of patch 12.1.3
12 issues closed, that’s a nice late summer patch.

What do you think?

Maxime

5 Likes
4

I’ll take your reactions as a yes :slight_smile:
I’m on it then

2 Likes
5

Hello,

After several attempts, it appears I cannot deploy anymore on https://oss.sonatype.org/.
I did the token creation procedure in June but it looks like it doesn’t work.
I’ve tried many combinations to no avail.
Furthermore, I cannot login to oss.sonatype.org from browser anymore. I’ve sent an email to ask for support.
Anyway, in the meantime, can someone with proper access rights (@luc, @Bryan ?) deploy and release the artifacts?
These are the steps 11 and 16 of the release guide.
I will be able to take care of the rest.

Thanks,
Maxime

6

Hi @MaximeJ

I’m unfortunately in holidays, far from my computer. Therefore, I can’t help you now… :confused:

Bryan

7

No problem @bcazabonne.

@luc thanks for helping me unlock my Sonatype account :heart:, I’ll go on with the release

1 Like