Hello Justin
Justin Deoliveira a écrit :
> Sounds like you are making good progress. That said I would like to see
> a formal proposal with voting before any changes come back to geotools.
> Unfortunately the forking nature of how this work has been done
> represents a lot of risk to projects that depend critically on the
> geotools referencing code.
Sure, it sound normal. But it is not a "take it or leave it" deal; the merge
with GeoTools will exists publicly on Mercurial anyway, so anyone can create a
clone and applies his own changes before an eventual commit to the SVN. The
Mercurial repository to be merged to GeoTools SVN doesn't need to be our; it
can
be your clone if the community prefer that way. And the merge can be applied on
a SVN branch before the SVN trunk.
> I also think we need it to be easy to revert back to the current
> referencing code. While I realize you have worked hard to maintain most
> of the api and backward compatibility there will undoubtedly be
> regressions. Those regressions could be "deal breakers" so depending
> projects need a way to fall back onto the old code easily.
Maybe by performing the merge on a SVN branch before the trunk? Or yet before
that, maybe by trying to checkout GeoTools from the Mercurial clone where the
merge will have been applied?
Martin
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
