Jody,

I think it's well understood that having most of the good coverage 
support/work on 2.3.x is unideal right now, but I'm surprised that 
you're just coming across this issue for the first time right now.

As I understand it Simone and Alessio targeted 2.3.x back when 2.4.x was 
still a gleam in the PMC's eyes.  There was a 1.4.x_merge_wcs geoserver 
branch which became GS 1.5.x which has always targeted 2.3.x.  I have to 
admit I wasn't paying full attention to the gt branches right then, but 
I think 1.4.x peeled off (leaving gs-trunk/1.5.x as a WCS version) right 
about the time that 2.3.x peeled off of gt-trunk (leaving gt-trunk/2.4.x 
as a not-targeted-by-any-geoserver version).

In any case, I'm sure everyone would love it if the 2.3.x coverage work 
moved forward to trunk, but since most of the coverage work is motivated 
by having raster data available through geoserver, we're stuck at 2.3.x 
till gs-trunk-on-trunk comes around and is stable enough to deploy.

All of which is to state my opinion on two things:

1)  Having all the GCE work targeting 2.3.x is unideal, but the only 
currently workable solution for those interested in actually serving 
raster data through geoserver.
2)  Moving the GCE work to gt-trunk is necessary, but blocks on a 
*usable* gs-trunk-on-trunk and the time to port the GCE work to 2.4.x.

--saul

Jody Garnett wrote:
> The goal here is to make sure trunk is stable (and suitable); if there 
> is a tone of changes and improvements lurking on 2.3.x then we have a 
> different set of troubles ...
> Cheers,
> Jody


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to