Roger,
https://libtiff.gitlab.io/libtiff/bugs.html: "All bugs filed in a older
bugzilla at bugzilla.remotesensing.org (pre April 2008) have
unfortunately been lost."
I'm not sure you should spend up much time trying to replace links from
the remotesensing bugzilla to gitlab ones. Such use is probably
extremely marginal, and people in strong need for that can do the manual
effort to do the mapping by searching in gitlab issues
Even
Le 03/06/2022 à 12:44, [email protected] a écrit :
Hi,
While going through the old documentation, I noticed that in the older
release notes there are many references to the RemoteSensing.org
Bugzilla instance. Example:
http://bugzilla.remotesensing.org/show_bug.cgi?id=1025. Unfortunately,
this domain is no longer in use. There appears to be a switchover to
the current MapTools Bugzilla around the 3.0.0beta-3.0.0final
timeframe. After that all references are e.g.
http://bugzilla.maptools.org/show_bug.cgi?id=2005
With the MapTools bug having been imported into GitLab issues, we do
have a means of replacing/supplementing all of the MapTools links with
GitLab issue links. However, for the older RemoteSensing links, I’m
not sure what we can do. Was the RemoteSensing Bugzilla imported into
the MapTools Bugzilla? If so, do we have any mapping of old-to-new
ticket numbers which we can then look up on GitLab issues? With all
of the links being simple numbers, it’s not clear we can unambiguously
identify which ticket is which in either MapTools bugzilla or GitLab
issues. Do we have a dump of the RemoteSensing Bugzilla or any other
mapping which we could use to identify which ticket is which?
Thanks,
Roger
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff
