Attending- Andrea Aime
-
Torben Barsballe
-
Kevin Smith
-
Jody Garnett
Actions from prior meetings:- None
Agenda- Build server
-
Log4J
-
Release train
-
Re-organize releases and EOL table
-
Chit chat
Actions- Jody: Talk with Juan and Jeroen and see what is possible.
- All: Please review https://github.com/geotools/geotools/pull/3845
Build server
Some issues lately, got more capacity, it’s still accumulating builds in the queue pretty fast
-
Could use faster build as we it is not keeping up
-
Can we get a faster build server? faster disks? (https://www.soyoustart.com for example), for example https://www.soyoustart.com/it/ordine/soYouStart.xml?reference=2207sys062
-
I am sure we can do something, and transfer the VM over
Windows job (azure) is working, but still having trouble uploading the results so it is recognized as part of the build results (it is showing up in the right folder if you are logged in and look).
-
Juan is going to try and upload to a different location
-
Or we could poll to see the result
action: Jody to talk with Juan and Jeroen and see what is possible.
Log4J
Held up on PR reviews.
Configuration switch at runtime working!
Using Log4J internal code, but apparently stable over time.
Q: Does this support custom logging config in test cases
- It should.
Request review of:
Release train
Release candidate waiting on log4j above.
- Older GeoTools builds were not finding build.xml (think it had some logic to use ant rename.xml script).
Re-organize releases and EOL table
Don’t have a clear table that specifies end-of-life table.
https://github.com/geoserver/geoserver/wiki/Release-Schedule
- add: table here at the top?
http://geoserver.org/download/
- idea: This does not provide the date that each series was archived
Table has been added to the top of this page: https://github.com/geoserver/geoserver/wiki/Release-Schedule