This is a release candidate of GeoServer not intended for production use. This release is made in conjunction with GeoTools 16-RC1 and GeoWebCache 1.11-RC1.
Thanks to everyone who provided feedback, bug reports and fixes. Here are some of the changes included in 2.11-RC1:
Incompatibilities with GeoFence and Control-flow have been resolved
Empty WFS Transactions (which perform no changes) no indicating everything has changed
Improvements to WFS GetFeature support for 3D BBOX requests
We have one known regression with the windows service installer (memory setting is incorrect)
Please additional details see the release notes (2.11-RC1 2.11-beta )
Release Candidate Testing
The 2.11 release is expected in March, this release candidate is a “dry run” where we confirm new functionality is working as expected and double check the packaging and release process.
Please note that GeoServer 2.9 has reached its end-0f-life. If your organization has not yet upgraded please give us hand by evaluating 2.11-RC1 and providing feedback and your experiences for the development team. This is a win/win situation where your participation can both assist the GeoServer team and reduce your risk when upgrading.
Corrected default AnchorPoint for LabelPlacement
An issue with SLD 1.0 rendering has been fixed - when a LabelPlacement did not include a AnchorPoint we were using the wrong default!
BEFORE: default anchor point was X=0.5 and Y=0.5 - which is at the middle height and middle length of the label text.
AFTER: default anchor point was X=0.0 and Y=0.5 - which is at the middle height of the lefthand side of the label text.
This is a long standing issue that was only just noticed in February. If you need to “restore” the incorrect behaviour please startup with -D_org.geotools.renderer.style.legacyAnchorPoint=true _system property.
With extensive improvements to startup performance and OGC requests for large installations we are looking forward to feedback from your experience testing.
About GeoServer 2.11
GeoServer 2.11 is scheduled for March 2017 release. This puts GeoServer back on our six month “time boxed” release schedule.
OAuth2 for GeoServer (GeoSolutions)
YSLD has graduated and is now available for download as a supported extension
Vector tiles has graduate and is now available for download as an extension
The rendering engine continues to improve with underlying labels now available as a vendor option
A new “opaque container” layer group mode can be used to publish a basemap while completely restricting access to the individual layers.
Layer group security restrictions are now available
Latest in performance optimizations in GeoServer (GeoSolutions)
Improved lookup of EPSG codes allows GeoServer to automatically match EPSG codes making shapefiles easier to import into a database (or publish individually).
- OGC Filter Injection Vulnerability Statement
- GeoServer 2.22.0 Release
- GeoServer 2.21.2 Release
- Jiffle and GeoTools RCE vulnerabilities
- GeoServer 2.20.4 Released
- Spring4Shell RCE vulnerability
- GeoServer 2.20.3 Released
- GeoServer 2.19.5 Released
- GeoServer 2.19.4 Released
- Log4J2 zero day vulnerability assessment