Chris Holmes wrote: > So at TOPP we're taking a bit of a hiatus from paid work to focus on > some core improvements on GeoServer which should hopefully make future > development even faster. We've focused a lot on user facing features > in the past couple years, neglecting some core annoyances. Yeah! > Chief among those is the core configuration classes and the outdated > struts (1) user interface technology. I believe Justin has been > making progress on the configuration stuff, and it should hopefully > get on to trunk soon. I am glad to see that work picked up again. > The UI evaluation needs to be fired up again, and I'm hoping we can > select a technology by the time of the OSGeo sprint, June 16-22, and > do most of the change over then. Meanwhile we should also keep on > making progress on 1.6.x bugs. And 1.7.x is still slow, some core > GeoTools changes are needed. Do you have a breakdown on what GeoTools changes are needed? We don't have any further changes scheduled for GeoTools trunk that I am aware of. There are some ideas (say a a better API for coverage access, a process api and such like) that are floating around but as far as I know they do not have a strict deadline or target GeoTools version. > So we should make a plan for getting this work completed. From my > perspective I'd like to see 1.7.0 in release candidate status around > the end of June. So does 1.7.0 include a new user interface or not? Trying to figure out what is where when ... I see further in the email you are trying to make that decision as well. > From the TOPP side we can put some substantial resource in to this: > Andrea, Gabriel and Justin should have a majority of their time > available, and David and Arne can pitch in when our KML project > completes. If other people are available to help out do let us know > so we can plan on that. End of June sounds fine on this end; we may end up cutting some of the unsupported modules from the GeoTools 2.5.x branch (such as process) rather than showing them to the world quite yet. > I'm going to be at conferences and vacation for much of this time, so > I'd prefer a plan that everyone feels comfortable with committing to. > If we don't think it's reasonable to get all that done and stable by > the end of June then we can come up with something less ambitious. > Perhaps just focusing on a really solid REST API along with core > config? But this is one of the few times that paid or product > priorities aren't dominating, so it's an opportunity to really tighten > up a core that will allow us to move faster in the future. Agreed. > We should also think about if we want to try to redo the UI, or if we > should just replace the backend technology and leave the html there. > We can put an interaction designer on making something that's more > intuitive, but in the interest of less moving parts it could be good > to hold off on that, and then call the results of that GeoServer 2.0. > Could perhaps move off the 1.7.x release date and just aim for a super > solid 2.0 by end of August? I am conflicted on this one; the amount of change / instability of the GeoTools level makes me want to call the next release GeoTools 3 / GeoServer 2 etc... I like the idea of a 2.0 release at the end of August. The timing looks good for the WPS work as well.
I am open to both suggestions, I can see it two ways: - technology wise a 1.7 release backed on to the new config subsystem and a GeoTools 2.5 makes a lot of sense (walk before we can run). I would like to hear back on how that work is going from Justin. - product wise it is nice to deploy all of these in an exciting GeoServer 2.0 release (with a line up of FOSS4G announcement & workshops) > In the interest of not having super long emails I'll bring this to a > close, would love to hear more people's thoughts on the next month or > two, what we should plan on and get done. And should coordinate the > rest of the plans with GeoTools, ect. Cheers, Jody ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
