-
-
Notifications
You must be signed in to change notification settings - Fork 489
Bolsena 2019
Link to the event: Bolsena_Code_Sprint_2019
- GeoNetwork 3.8.0
- OSGeo budget
- New committers ? Antonio ?
- Java 8 and Java 11 LTS discussion along with Java 11 code sprint results
- GeoNetwork 4.0.0 based on Elasticsearch
- ISO19115-3.2018 as a default schema ? in version X ?
- GDPR
-
Monday
- Improvements for metadata workflow
- Elastic Search prototyping: Francois, Florent, Jose
- GeoTools 21.x upgrade: Juan Luis, Jody Garnett
- Afternoon: Kickoff meeting
-
Tuesday
- Elastic Search prototyping: Francois, Florent, Jose
- Afternoon Coffee Chat: Xerces Technical Debt
-
Wednesday
- Elastic Search prototyping: Francois, Florent, Jose
- Afternoon Coffee Chat: Technical Debt RDF4J upgrade
-
Thursday
- Elastic Search prototyping: Francois, Florent, Jose
-
Friday
- Elastic Search prototyping: Francois, Florent, Jose
- Release GeoNetwork Release 3.8-RC: Paul, Antonio
- Afternoon Coffee Chat: Technical Debt NGeo Upgrade to OpenLayers 5 or 6?
-
Technical Debt Accounting - write page on wiki
- Write up Xerces "fork" (old version required to use Java in XSLT transforms)
- RDF4J Upgrade for Java 11
- NGeo Angular wrapper on OpenLayers 3 upgrade
-
Upgrade to GeoTools 21.x. - see search and replace list stage 3 from java 11 sprint results.
-
It looks like this also includes upgrade to JTS 1.16.x
-
This is best done as a team activity as it pretty much ensures merge conflicts.
-
Tentative update to GT20 https://github.com/geonetwork/core-geonetwork/pull/3198
-
Use WFS-NG instead of WFS datastore in EsWFSFeatureIndexer ?
-
Update: Have asked the GeoTools 21.2 release be delayed until next week so we can be sure of a smooth upgrade. So initial update can be to GeoTools 21.1 release, if we have any problems we can fix/test against 21-SNAPSHOT, and then make the 21.2 release with included fix.
-
-
Elasticsearch migration
-
Github hooks for better code (eg. indent not following .editorconfig conventions) https://gist.github.com/davetron5000/37350
If you have some comments, start a discussion, raise an issue or use one of our other communication channels to talk to us.