Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

Is it worth following Java to year.month based versioning - so it becomes really obvious for organizations running old versions of software? (Note I cannot think how to do this with our concurrent stable + maintenance release windows) -- Jody Garnett On Thu, 12 Jul 2018 at 23:35, Andrea Aime wr

Re: [Geoserver-devel] Thinking out loud... should the next GeoServer be "GeoServer 22.0"?

I would echo this, I also like the idea of the version number reflecting the stability of the data directory structure on disk. -- Jody Garnett On Thu, 12 Jul 2018 at 10:36, Chris Snider wrote: > Just a thought; > > > > Many businesses and governments will grant a project authority to include >

[Geoserver-devel] Jenkins build is back to normal : geoserver-master #6068

See -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___

[Geoserver-devel] Build failed in Jenkins: geoserver-master #6067

See Changes: [Jody Garnett] Set the EntityResolver in the WPS Request Builder when building the -- [...truncated 7.71 MB...] at org.junit.internal.runners.stat