Jody Garnett ha scritto: > How about this for a compromise... > > 1. Create unsupported/swing today - and include it in the default build. > 2. Drag in only what we need for demo/example in support of the Sphinx docs > 3. Nominate it for supported status when we are through porting the > initial welcome docs to Sphinx
So what's keeping that supposed new module from being supported is just lack of documentation? That seems quite strange to me, it's going to be quite messy once merged, there is stuff that needs to be removed, harmonized a little and so on? Also I'd prefer to try and get cleaner and cleaner with time, so just remove modules from the build unless they get into supported land. My previous mail was going straight into that direction, try to remove the three modules now building in unsupported so that we have a "clean" unsupported situation. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
