Justin Deoliveira ha scritto: > David Winslow wrote: >> Here's the bug: >> http://jira.codehaus.org/browse/GEOS-2281 > Ok, its not scheduled against a version... >> What I did was exactly what I said I would do; > The last message I got from you stated that you would "revert on 1.7.x", > which i assumed to mean no commits would be taking place. When in > reality you just replaced a commit to one core class with a commit to > another. I apologize for missing this in your original mail. > > roll back the >> .available() fix (which had been committed on 1.7.x already) and modify >> the request logging filter to avoid triggering the problem. This bug is >> pretty minor (it only shows up when POST body logging is enabled, so >> there's an easy workaround) so waiting for 1.7.1 is fine. > In all honesty I would prefer kicking the bug back. Our "informal" > freeze breaking policy has been only to commit changes for serious > regressions and bugs, like the recent issue with leaking postgis > connections. > > Perhaps this bug is serious enough? Not sure. Andrea, what do you think?
No need to touch 1.7.x right now, the bug occurs only on trunk afaik Cheers Andrea -- Andrea Aime 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
