I just had the information that a customer of ours (UFZ Helmholtz) is willing to sponsor the next releases on the 4.4.x and 4.2.x branches, which means that we would be in charge of making them.
The next GN4 meeting is in two weeks (24.09), can we plan on discussing then when these releases should happen? Ideally (for us), it should happen around the end of September/beginning of October.
Hey Oliva - that is great, I think you can just start planning, if you have budget / capacity. The release process is much improved from a few years ago with a very helpful script now available.
Do you want to start an issue in the issue tracker or something to coordinate?
Thanks @Jose Garcia, Iāll wrap things up today (Friday was a public holiday in Germany).
Also please note that Iāll revert https://github.com/geonetwork/core-geonetwork/pull/9054 as it was an error from my side to upgrade GN-UI so soon; I thought I could benefit from the recent release but it hasnāt been tested enough IMO.
Hi all, the release is done and uploaded on Sourceforge. I didnāt push the artefacts on the OSGeo maven repo though (is that always done now for releases)?
Kinda struggled because I did a PR for the release but ended up squashing it so the separate commits were lost, which prevented a tag from being put⦠anyways, Iāll try do to a post mortem somewhere and update the docs to avoid this in the future.
I still have to update the website and communicate on the mailing lists thanks for your patience
This is my plan yes, but I might need a bit more time for the 4.2.14 release (a week or two at most). If anyone wants to pick it up in the meantime, be my guest thanks
Yes, pushing up the artifacts to nexus repo is required for folks (like GeoCat and Camptocamp) that use the war overlay technique (which we presented in foss4g a few years ago).
You can find a list of new functionalities and fixes for version 4.2.14 and for version v4.4.9.
If you have any improvements you want to contribute back, the best is to use git to get a local copy of the source code from the GeoNetwork GitHub repository, apply the fix and put out a pull request so your improvements can be integrated quickly. Otherwise you can also create new tickets in the GitHub issue tracker.
Thanks and congratulations to all the community members and developers that have been putting effort and energy in these releases and the documentation update.