Dear Team,
I am reaching out to request guidance on upgrading two production GeoServer
instances, currently running versions 2.17.2 and 2.18.0, to the latest
version, 2.26.0. My goal is to ensure a secure and stable upgrade process
for both instances, particularly given the differences in their current
versions and potential patching gaps.
*Concerns and Considerations for the Upgrade:*
1.
*Patch Status of 2.17.2 and 2.18.0*:
- Could you confirm whether GeoServer 2.17.2 is considered "unpatched"
compared to later releases and clarify if any critical patches were
introduced in 2.18.0 that are absent in 2.17.2? An overview of the key
security or stability fixes included in 2.18.0 and later
versions would be
very helpful for planning this upgrade.
2.
*Compatibility and Configuration Considerations in 2.26.0*:
- Are there any known compatibility changes in version 2.26.0 that could
impact configurations created in 2.17.2 or 2.18.0? In particular, I am
interested in ensuring that the existing data directory structure,
workspace setups, styles, and datastore connections will remain
compatible
after the upgrade.
- Could you advise on any verification steps or compatibility checks
to confirm that our current settings will work seamlessly with version
2.26.0?
3.
*Upgrade Path and Best Practices*:
- Given the two production instances on different versions, would you
recommend an incremental upgrade path (e.g., 2.18.0 to 2.20.x, then to
2.26.0) or a direct upgrade to 2.26.0 for both?
- Are there specific staging or testing practices you would suggest
to minimize downtime and ensure a stable production environment
during and
after the upgrade?
4.
*Security and Performance Enhancements in 2.26.0*:
- Could you highlight any significant security improvements, performance
optimizations, or critical bug fixes in 2.26.0 compared to 2.17.2 and
2.18.0? Knowing these would help emphasize the upgrade's value to our
stakeholders.
5.
*Data Directory Separation*:
- Both GeoServer instances currently operate with separated data_dir
configurations from the main application directory. Are there
any specific
considerations for maintaining data integrity and compatibility with this
structure in 2.26.0?
I would greatly appreciate any additional insights, documentation, or
suggestions from your team to help facilitate a smooth upgrade process for
these production instances.
Thank you for your assistance and for your ongoing work on GeoServer.
*Regards,*
*Muhammad Asif **|*GIS Developer*|*
Mob: +92 300 812 91 65
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
