We’re committed to keeping your services secure, stable, and fully supported. A big part of that involves staying ahead of the curve with underlying technology. We’ve recently completed a significant round of upgrades, moving all our managed GeoServer instances to version 2.28.2.

Efficiency through preparation

Our team, led by Elena Robu and Tom Chadwin, set a goal to complete these upgrades by the end of April. By refining our internal processes and developing a more time-efficient workflow, we’re pleased to share that we hit this milestone early. The final instances were successfully updated on 15 April.

This improved process didn’t just help us beat the clock; it also made the transition safer and less disruptive for our customers. By upgrading live instances in place, we ensured our team was on hand to provide immediate assistance if needed, though the minimal downtime meant most users didn’t notice a thing.

Why version 2.28.2?

The move to GeoServer 2.28.2 was driven by our commitment to security and compliance. With GeoServer v3 now released for early adopters, it’s crucial for our customers to have the latest long-term stable version to allow GeoServer v3 to bed in before we roll it out.

This upgrade also included a move to Java 17. This modern foundation provides better performance, strengthens the security of your environment and prepares the ground for GeoServer v3. You can view the full technical details in the GeoServer 2.28.2 changelog.

What this means for you

The best part of this upgrade is that our team handled the heavy lifting. Each customer was kept updated via their individual support tickets, and we’ve already confirmed success across the board.

We’re always looking for ways to make our maintenance work more efficient. This successful rollout is a great example of how a bit of extra preparation behind the scenes leads to a better, more secure experience for everyone. Our thanks go to our team, especially Elena and Tom, for their efforts!