> > 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. I agree here but the trouble is how to determine if it does indeed work as well. Hand testing is good but hardly comprehensive and thorough. So I propose the following:
1. fix the reflector bug which is currently the only known regression 2. roll back all other kml work 3. write a few sanity check tests 4. release 1.7.0-RC4 next week 5. *completely* freeze 1.7.x on anything that is not a bug fix 6. if all goes well release 1.7.0 the following week -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------- 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
