We would like to release 1.4.0 right away, but that geotools 2.2.0 release just never comes. I think we are at the point where we might just release against an RC that worked.
-Justin Jody Garnett wrote: > I know jesse has not had a chance to respond to the 2.3 and uDig based > questions from Monday's meeting. > It seems that he is swamped and will not have a chance to play with us, > and we should make plans accordingly > (on the bright side he was asking questions about improving some of the > datastores, hopefully we can talk > to module maintainers in a bit if a plan takes shape). >> Hum, I see problems here in the possible release date. >> Forces: >> * can we release 1.4.0 without modularizing the UI? Does it make sense? >> > Yes we can, it just means we have a module system. Can we include WCS as > a community module yet? No ... > We should release 1.4.0 pronto, leaving trunk free for this work. All > it means is that the modules > people create will function, but will not be able to pass the seven > steps for GeoServer acceptance (of which > config and user interface are two). > > It makes sense, it is not complete, but it makes sense. >> * gt2 2.3.x wants to do a release soon, but it should be tested >> at least with geoserver and udig >> > uDig is out of the picture citing lack of resources and a different > direction, we may be able to > temp them with the new grid coverage work, but I would like to have a > talk about WCS Client > support with Simboss (and Richard?) first. >> * geoserver won't really test the new features in 2.3.x until the wcs >> branch hits the trunk and everybody starts fiddling with it >> > Indeed, so I would like to get 1.4.x out of the way, and move trunk to > 2.3 so we can start working > on it. >> * wcs branch won't be merged onto trunk until 1.4.0 is out (or not?) >> > Indeed. >> So it seems delaying 1.4.0 release will delay gt2 2.3.0 which in turn >> would delay even more the feature model branch merge... oh my... >> that's why I was concentrating on giving a modular face to our >> current configuration system >> > understood, so lets get GeoTools 2.2 out the door and chase it down with > GeoSever 1.4.0, I trust > uDig will continue to track this branch keeping it stable while > GeoServer kicks 2.3 around for a bit. >> A configuration system overhaul would take quite a bit of time, there's not >> even a design around, and it would delay even more all the rest. >> > Indeed, that is why it is not being considered right now? At least by me > ... lets evolve a configuration system > based on preference module (see Jesse's proposal) and if we want we can > start switching existing modules > over to it. We do not have to do anything with WCS before 1.4.0 goes > out, and it would be very nice > to have a 1.5.0 alpha with WCS out (with & GT 2.3) to demo at FOSS >> I'm concerned :-( >> > I am happy, somebody else recognizes we need to nail down our roadmap > and follow it to get through the > next little while. And heck it is thursday - what happened to the > GeoTools 2.2 release? > > Jody > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Geoserver-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > !DSPAM:1004,44db2930160371194215290! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
