David Blasby wrote:
> I've been thinking about IP issues the last few days, and did a very
> review of parts of geoserver. I found a few issues - I'm sure there are
Thanks for taking these issues seriously Dave, looking at what you have
so far leaves me a be daunted on the geotools front.
> I'm making a jira task with this in it and marking it as "blocking" until
> the issues have been addressed. I'll also put this in the wiki so people
> can add/subtract/update:
wow so that is where you have been hiding :-) I am sure this
is exactly the kind of list we need out of the geotools IP check.
> There's been a few possible cases of Geotools accidently including code
> from sun's included-with-the-sdk source - and I'm sure other issues will
> be found. These have, apparently, been fixed. I dont know what the
> implication are for re-distributing the old copies inside geoserver.
The only trouble is the arcsde support in old geoserver releases, I know the
apache project was very keen on just stopping the distribution channel the
moment a problem was found.
We could cut off downloads of all old versions of geotools, geoserver
> Redistributing old copies
> As above, I dont know what to do about re-distributing old copies of
> geoserver that might have IP issues.
To be strict - cut off the downloads at SF, to not be strict fix the
as soon as possible and ensure that there is a new version that is issue
- cut off all downloads while the new version is preped
- issue a patch release for old version (well stable branches would be fine)
- and then turn the pipe back on.
> I dont mean to cause anyone panic, and I dont think going through all the
> above is a lot of work. But, it needs to be done.
I thought the same about geotools, but asking for volunteers is tough,
this is time for those on the PMC to earn their danger pay or something.