No problem, only a question... is uDig already jumping on trunk?
Yes. I don't have resources to watch it fall behind again; or run two branches.
Plus I have been very impressed with the increased in stability afforded by
nightly builds
and our change procedure etc...
> If history is any indication next months will be a pretty rough ride, codebase
> might break unexpectedly and take some time to get into a usable state?
Yep. If so uDig can always hang back at a milestone release. Indeed it would
be wise to issue a milestone release before launching into any major work
(like removing of rendering hints for android).
Also frankly if the OSGi work moves along; I expect uDig to be used as a sanity
check to make sure
it was done successfully. Now that work is happening on a branch for now; but
it will be useful to have
uDig on hand when it returns.
Thanks for the inquiry,
Jody
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
