> Jody, I see you are making pull requests which involve changes to the
> referencing module
> and merge them before getting any feedback from the maintainer (ah hem, me).
>
> Would it be possible to work on a branch so that you can reach your
> deliverable, and
> allow some time for the reviews of the modules you're not maintainer of?
>
I have a branch going on, but am doing this changes hand in glove with uDig
master. On the "bright" side I have chased
the remaining issues over into the deegree project, and thus have bought "more
time" before this pull request is needed
contract wise.
I was however hoping to issue a uDig 1.3.3-SNAPSHOT allowing ows9 participants
to test the correct functionality.
> I'll have a look at the changes you made this weekend (and may have to modify
> changes, hopefully not to revert any...)
>
Fair enough, mostly trying to get the toString methods to report back what is
going on.
I am away next week and will not be in the geotools meeting; feel free to roast
me for accepting my own pull requests.
Jody
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
