After a nice showing at the FOSS4G Tokyo and Osaka conferences we decided the time had come for a new GeoServer language users mailing list. Taking advantage of the fact that GeoServer just got accepted to OSGeo incubation the new list is on the OSGeo infrastructure, at http://lists.osgeo.org/mailman/listinfo/geoserver-jp The mailing list is a resource for those who would like assistance in all things GeoServer, but prefer to discuss in Japanese. This marks the sixth language mailing list for GeoServer. We’re hoping soon the community gets a translation of the new UI, and some Japanese docs as well.
It’s official! We are pleased to announce that GeoServer has been accepted into incubation at the Open Source Geospatial Foundation (OSGeo). Putting GeoServer under the same roof as all the best geospatial projects in the open source world is a great advance for the project. While GeoServer is not yet an official OSGeo project, just getting accepted in to the incubation process is a firm indicator that we are on the right track. The process makes sure that we meet all of OSGeo’s standards for a diverse community, a robust governance structure, and clean code that others can rely upon. We believe GeoServer has all of these, but additional validation from a third party like OSGeo signals to the world that it is so. Thanks to the incubation committee and the board for approving our application, and to Richard Gould for serving as our mentor. And of course to the whole GeoServer community for taking us here.
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.
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.