Justin Deoliveira ha scritto: > My thoughts: > > Config stuff goes well, almost ready to commit, a few loose ends to tie > up... but all unit + cite tests pass.. i have hand tested most of the > UI, etc... > > End of June for release candidate of 1.7.0 should be doable... but i > fear its going to be a bit shaky for the first few release candidates. > With the new config we are undoubtedly going to have regressions. > Similar to on 1.6.x with the new dispatcher and xml parsing, etc... So > we could start moving 1.7.0 toward stable by end of june... but i think > it is going to take a few releases to work out the kinks for sure. > > As for what to cover in 1.7.0... I would vote for the following: > > * new config model (wrapped up in old model) > * address geotools performance issues > * rest api > > I lump in REST api because it gives us something visible.. and is just > downright cool :).
Hmmm. REST api is going to finally free all the people that are struggling trying to programmatically configure GeoServer, so it's cool all right. But (you expected a but, right?) how do we implement a good REST api like http://geoserver.org/display/GEOSDOC/GeoServer+Resources without a correspondent big change in the configuration and config storage subsystem? If we go for a cut down version of that proposal, it might work, but we have to be careful to make it forward compatible. There are issues to be solved there too (such as style treatment which is incompatible with the current geoserver config). > So that moves us to the sprint. It would be nice to get 1.7.0-RC1 out of > the way before the sprint... but i am not sure that will happen. At a > minimum, I would say we should get to a point where we can at least > branch 1.7.x... and move it toward release. That would leave trunk open > for the sprint. As to what to cover I would like to see the following: > > * continue with config work (porting services and > serialization/deserialization to the new model) > * new user interface > > Now I know this is a lot... and I of course don't expect us to get them > done in one week, but we could get a darn good start. And with the face > time we could make sure we are all on the same page. Yeah, doing both seems quite ambitious. It might work if we just try to do a UI technology conversion without trying to redo the UI face as well, and spend the extra time making the UI talk to the new config module directly. Of course, this would not really give GeoServer and new face, but then again, I don't think we can handle changing the config, UI technology and UI face at the same time. Moreover, giving GeoServer a new face would require some planning on what the new workflow is, and that would put extra burdern on the preparation or turn the sprint into a discussion of how the new UI should look like. > After the sprint we could continue working on the new stuff while moving > 1.7.0 along to release. I think with these proposed changes... trunk > will have to become 2.x.. Which I think makes sense because we are 1) > breaking our disk storage format and 2) giving GeoServer a new face. > > Apologies for the long email... trying to wrap this up. If people are on > board with this plan it would mean that at a minimum we have to get the > following done before the sprint: > > 1. initial config work > 2. fix geotools performance > 3. finish ui evaluation > > I think the above list is doable... 1 is close to done and i am close to > a patch for 2. The thing we are really lagging on at this point is the > UI evaluation. So far we have an old Wicket prototype and a new Cocoon prototype. I tried some other technologies, such as Struts2 + freemarker, but rapidly got out of my "comfort zone", that is, they rapidly became too annoying to use for weekend projects. Cheers Andrea ------------------------------------------------------------------------- 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
