P.Rizzi Ag.Mobilità Ambiente a écrit :
I filed the JIRA issues, tried to collaborate with the module mantainer, etc.
But it happens there was no real module mantainer nor anybody that seemed to
care.
Which module was it? Some modules are orphan, unfortunatly...
Maybe there is too many modules in Geotools for current amount of active
developpers. I tend to treat bug reports in the referencing module with
a high priority (especially when patches are provided), but can't handle
all of them, especially when they are related to Geotools parts where
I'm not yet involved.
All the JIRAs were simply rescheduled to a newer version after the other,
after the other...
The problem is that they are not assigned to anybody, so it is not going
to move until someone take it. We push it to the next version because
some progress hapen in some other area (including bug fixes...) and we
don't want orphan modules to block the release of those bug fixes.
Thats said, I realize that DataStore is a somewhat central piece of
Geotools...
I could have committed the fixes myself, but nobody ever said: "...OK, do
it...".
I would said "go for it" if you are volunter, but I'm not someone who is
going to be much affected by DataStore API changes (I do not use it
yet). I would like to hear what other Geotools developpers / users think?
Martin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
