> Regardless I think we need another release candidate, RC4. And before it > goes out I think we need to add a significant number of test cases for KML. > > What do people think?
I think that we need to get 1.7.0 out pretty soon. I think the GeoSolutions coverage stuff was ready to merge awhile ago, and we told them to wait because we were in feature freeze and 1.7.0 should get out first. I don't think we should have been tweaking the KML stuff as heavily as we have been, especially with no tests. I don't think we actually need to have all the new KML stuff in for 1.7.0. I've always thought it as 1.7.1 or 1.7.2, putting in more work to make it a lot more solid. I'd say if it's easy to roll back the latest tweaks we might consider that. So if possible I'd say back out changes, make sure KML works as well as it did for 1.6.x, and get 1.7.0 out asap, so that other features that have been held off can come in. And hopefully after that focus on KML tests and get a 1.7.1 release pretty quick. It'd be good to do quick releases so we continue to get feedback on new features. Like each of these kml improvements, like schema compliance and extrudes, should be quick little point releases with one new feature each. 1.7.0 doesn't need to be perfect, especially not with the new features, it just needs to work as well as 1.6.x Chris > > -Justin > -- Chris Holmes OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
