I figure we went through this on the email list when Andrea brought it up. For me it come down to a decision on how long the 2.0 branch was going to last (ie how long until the wicket ui is ready? and can we keep the wicket ui as the *only* scope for 2.0?). If this is something that is wrapping up in September then I would vote to keep geoserver 2.0.x branch on 2.5.x for a few more weeks.
If it is going to take longer than that then I would really like the help on the 2.6.x branch of GeoTools. It looks like most of the planned changes for 2.6.x (ie Symbology Encoding) are going elsewhere (or at least on a timeframe I cannot predict). That leaves you with uDig driving development on 2.6.x and we are only planning on fixes - and have no new functionality planned at this time. Jody ------------------------------------------------------------------------- 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
