Rob Atkinson ha scritto: > Andrea Aime wrote: ... >> Agreed, I don't like half backed changes me neither... yet this raises >> a concern. Who is in charge for the changes? Asking a single person to >> do that would mean he has to understand more or less the whole code >> base. Putting the burden on each module mantainer is a secure recipe >> for not getting things done I fear, thought. Maybe adding a blocker >> issue on the modules to update to the new API could be a way? (and >> who's gonna open 50 issues against all modules?) >> > I reckon we get the JDBCmodule updated ( or a replacement) then try to > get some key modules updated.
I would like so. Resources? Aka, who's gonna do that? > By the sund of it we need to leave deprecated methods at least one more > cycle, and our priortiy has to be to propagate through key datastores > and geoserver and uDig code bases. Then module maintainers have a "I > dont want my module to fall off next release" motivation, but it cant > happen without a few working. Yeah, that would be a good driver. Back in the unsupported land you deprecation ridden module!!!! > Is Geoserver OWS4 working against new APIs? Yes it is, but afaik changes are occurring on a "as needed" basis. Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
