GeoServer 2.0 moves to Release Candidate status
The GeoServer Team would like to announce that GeoServer 2.0 is now out of beta and has moved into Release Candidate status.
In case you haven’t been following our previous posts, GeoServer 2.0 contains a completely redesigned user interface, using Wicket. Based on feedback from our beta testers, the move to RC1 consisted mainly of user interface improvements. One specific new feature to point out is that ArcSDE stores have a better configuration panel, one that simplifies requests to raster coverages.
With 55 issues fixed, this first Release Candidate is deemed stable by the GeoServer Team. But we need your help to verify this, so please download this new version and try it out.
N.B. If you wish to connect GeoServer 2.0 to your existing data directory (from 1.7.x), beware that GeoServer 2.0 changes the directory structure a bit, so should you wish to switch back to 1.7.x, you will need to hand edit some files.
Thanks to everyone who helped out with this release! Keep sending that feedback in. Assuming no large problems are found, we should have an official release in the next month or two.
Vulnerability
- GeoServer 2.26.1 Release
- GeoServer 2.25.4 Release
- GeoServer 2.26.0 Release
- CVE-2024-36401 Remote Code Execution (RCE) vulnerability in evaluating property name expressions
- GeoServer 2.25.2 Release
- GeoServer 2.24.4 Release
- GeoServer 2.23.6 Release
- GeoServer 2.25.1 Release
- GeoServer 2.25.0 Release
- GeoServer 2.23.5 Release