GeoNetwork next releases: 4.4.10 and 4.2.15

GeoNetwork GeoNetwork Developer
1

Dear all,

I am planning on publishing both releases this Thursday (16th of Apr).

There are still a couple of PRs to merge on my side:

Cheers,

Olivia

2

I think it would be good also to include:

Regards,

Jose GarcĂ­a

3

All three are now approved, feel free to merge once QA is green! Thanks

PS: friendly reminder that this one can also go in once rebased: https://github.com/geonetwork/core-geonetwork/pull/9066

4

Thanks @jahow

Added these PR to update transifex translations:

5

Hi @josegar74,

I approved the PR for 4.4.x but the one for 4.2.x contains surprising changes (deletion of keys and reverting some values to English), could you please confirm that this is intentional?

Thanks!

6

Hi @jahow

That is intentional, the problem is that the Transifex translations only are updated with main branch, so if removed or added new keys, doesn’t apply to 4.2.x branch and requires manual integration.

Regards

7

Right, but we can’t just merge that can we? This is going to cause regressions on the 4.2.x branch

8

Hi @jahow

It should not cause regressions. I have done the following steps:

  1. Download the translations from transifex, this step:
  2. Updates translations common translations from 4.2.x and 4.4.x –> This is ok
  3. Add new ones from 4.4.x that are not required in 4.2.x
  4. Removes translations from 4.2.x that doesn’t exist anymore in 4.4.x

For step 3, I have kept in the different translation files, the entries that are defined in the English version, using a Python script. So all translation files should have the same keys as the English ones.

For step 4, I have readded the missing translations from 4.2.x.

Regards

9

Got it, thanks for the clarification! I feel like in the future we could just bring in all the translations from 4.4.x without worrying too much about which is used or not.

10

Hi @jahow

Yes, we can do that. That will avoid the work for step 3, but we will have to do the work for step 4 anyway.

Regards.

11

@jahow It would be good to mention in the announcement of the releases to apply this change manually to fix the metadata full view map background image.

I guess most users doesn’t use that view, but just in case.

Thanks.

1 Like