Jody Garnett ha scritto: > In general I like to keep new features for trunk; however back > porting existing work if needed seems fine - and the UOM work has > been out for a bit now and released to the public already. > > The main module effected is of course rendering; so if you are happy > with the risk as the module maintainer of rendering I would say go > for it.
Since I'm proposing the thing I'm also ok with taking some risk. It is a trade off: - you get new functionality sooner - but the patch is out there for whoever wants to fully evaluate it - we know it does not break the build - someone already tried it out a bit On the other side the patch has not been used in production that I know of, so it's not as mature as the rest of code in 2.6.x > Is there a need to release geotools at the end of this work? We did > just complete a round of releases; however we could issue one for > June or July. No release is required, a nightly build will do, though I hope that with CITE tests being automated GS can go back on a bit more frequent release cycle. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
