GeoNode "Rock Solid" 1.1 Task List

[Sebastian Benthall]

Hi Everyone, 

This is an update on our plan for implementing GeoNode "Rock Solid" 1.1.

Based on numerous discussions between GeoNode stakeholders, users, deployers, and developers, we have compiled a list of issues to address as we push towards this next release.

Most of these issues are ticketed on our project Trac, and are listed in the 1.1 "Rock Solid" milestone.

We will get to as many of the goals on this list as our ability and funding allows.   Your feedback is welcome as it will help us prioritize this work.

These are our currently drafted goals for this release:

=======================================

Bug Fixes

Many bugs have been reported and are currently slated for being fixed in the GeoNode 1.1 beta testing and development process.  A list of these bugs and other GeoNode 1.1 issues can be found on our Trac, here:

http://bit.ly/myGFKf

Upstream Development

As part of Rock Solid we will be investing in upstream projects.

• Building better OGC service exception handling into OpenLayers, GXP, and the Map Composer
• Bug fixes, validation, and exception handling in GeoServer's REST and Wicket configuration systems, which many GeoNode users employ to configure their instances.

Documentation and Defaults

In order to ease deployment and modification of GeoNode, we are committed to writing more documentation and updating the default settings and installers where appropriate.

In particular, we plan to cover the following better in our documentation:

• the test framework and continuous integration server
• how to have GeoNetwork backed up by a database in production
• how to configure GeoServer to prevent authentication-related timeouts
• best practices for extending GeoNode to build other applications

Automated Test Coverage

In order to prevent regressions to core and widely used functionality as the software expands, we are aiming for 80% code coverage on automated tests. These tests will include both unit tests and integration tests.

Already Completed Work

Much work has already gone into Rock Solid.  While this is a long list, here is a brief summary: automated testing framework, continuous integration server, performance improvements on metadata edits to prevent timeouts, performance improvements on security to avoid timeouts, and a patch to OWSLib to work around a GeoNetwork memory leak.

--
Sebastian Benthall
OpenGeo - http://opengeo.org