It has been a long time coming but it is finally here. GeoServer 2.0 has been officially released and is available for download. The 2.0 release marks a major milestone for the GeoServer project. A special thanks to all the developers who worked hard for this release, all the users who contributed bug reports, and for those who provided feedback by testing out the 2.0 release candidates.

So what is new in 2.0? The first new feature that people will notice is a completely new web administration interface. Based on the Wicket framework the new user interface provides a much more integrated and streamlined application for configuring GeoServer. Wicket makes developing ajax enabled applications trivial by doing all the hard work for you.

One of the powerful features of Wicket for the developer is extensibility. Wicket allows one to plug-in components dynamically. This means that developers can now easily write plug-ins and extensions for the GeoServer UI. And some have already done so. Francesco Izzi and the developers from the geoSDI project have contributed a plug-in for configuring the GeoServer security sub system. Special thanks for the great contribution.

The 2.0 release also hails the home coming of the “complex features” branch and true support for application schemas. Led by Ben Caradoc-Davies and Rini Angreani, developers from CSIRO have made this functionality available in the core of GeoServer. Special thanks to them and to AuScope for funding the work. Check out the documentation for more information about getting started with application schemas.

New features has not been the only focus of 2.0. Much work has also gone into scalability and performance in order to ensure that GeoServer continues to improve not only in terms of new features, but also that it continues to get faster.

Much of this work came in preparation for the WMS Shootout at FOSS4G in Sydney this year. Great thanks goes out to Andrea Aime for not only representing GeoServer in this benchmarking exercise, but also for the countless number of hours he has poured into improving GeoServer performance and robustness.

As with any release many minor features and bug fixes have gone into 2.0. Be sure to check out the GeoServer Past Present Future talk given at FOSS4G that provides an overview of what else has gone on this year in preparation for 2.0.

Download 2.0 now and try it out. Please help us to continue to improve GeoServer by reporting any issues you encounter on the mailing list and bug tracker.

The GeoServer team is pleased to announce the release of (hopefully) the final release candidate of version 2.0: GeoServer 2.0-RC2!

The main focus of this release was getting every little detail in order for 2.0.0.  There were a number of critical issues discovered that have been fixed, and much work was done on the documentation.  But the community did slide in one major new feature, a new plugin called ‘Web security GUI’, that enables GUI based editing of GeoServer’s security configuration.  It hopefully will eventually move to the core, but for now is a great example of the advantages of the new Wicket UI technology - one of the major features of the 2.0 release.  The security GUI plugin can be added without having to change the core files at all, and is an example of how others can build extensions to the core GeoServer services and UI.

The other major feature of 2.0 is the app-schema work, and there have been a number of bug fixes for this release candidate.  More importantly, there’s now a lot of great documentation by the CSIRO team on how to get set up with feature chaining, and data access integration, as well as a great tutorial.

This release also marks the branching of 2.0.x to make way for some great new improvements on trunk.  The GeoSolutions team is working on bringing Hibernate in to the GeoServer catalog, so it can be backed by a database for even greater scalability and robustness.  And Justin Deoliveira is doing work to have one GeoServer configuration handle a number of different services and security permissions at once.  These will be the highlights of the 2.1.x release, and please get in touch if you can help with funding or development time.  Also being discussed is WFS 2.0, GML 3.2 and WMS 1.3, all of which could move forward with more support.

Thanks to everyone who made the 2.0-RC2 release possible.  And please download it and let us know what you think.  If there are no major problems this release will become 2.0.0.

With the rush for FOSS4G in full swing and most efforts pushing towards a final release of 2.0, we’re happy to announce that the GeoServer stable series (1.7.x) is still receiving the love it deserves.  Today we see the release of GeoServer 1.7.7 into the wild.  Though there is a relatively short list of bug fixes, a few of the rare but critical leaks have been plugged, and various improvements have been made to the REST configuration API, imagemosaic plugins, and the shapefile output format.

We encourage you to point your browser to the download site and give it a try, and as always, we are keen to hear any feedback you my have.

I am pleased to announce that we are organizing a “Birds of a Feather” session (what’s that?) at the FOSS4G 2009 Conference in Sydney, Australia. This session is to gather together everyone who is interested in discussing the past, present, and (bright) future of GeoServer.

The session will be held on Thursday 22nd October, late afternoon (specific time TBD). If you are attending FOSS4G 2009 (and you very much should), feel free to stop by in order to say hi and chat a bit with us.

See you there!

The GeoServer community is happy to announce the formation of an official Testing Team.

The Testing Team is a set of users and developers that will install and run impending GeoServer releases prior to their official distribution. The purpose is to provide real-world testing, something that developers alone can not provide.

Approximately once a month, a development freeze will be called and the Testing Team will install and run the most recent nightly build. Each tester in the team will use GeoServer in his or her unique environment and will check that important features are working as expected, and that regressions (features that used to work but now do not) have not appeared, with developers standing by to fix any regressions that may be uncovered. For example, someone will test that uDig still works against the GeoServer releases, someone else will test against ArcSDE, some will test for performance, and so on.

Are you interested? **Everybody can participate in the testing process. No development skills are required. ** All you have to do is to read the Official Testing Team proposal, drop in on the GeoServer developer mailing list (yes, even if you’re not a developer), introduce yourself and your desire to participate.

We want you to know that as development on GeoServer continues, we are trying to make sure that we are fulfilling the needs of the community. We want to make upgrading a seamless, hassle-free experience, and we feel that creating a team of testers is the best way to ensure this. The more people who join our team, the better GeoServer will become.

Let’s improve GeoServer together! Join us!