cheng/libtiff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HTML: update for GitLab issues

Browse Source
This commit is contained in:
Even Rouault 2019-10-01 21:27:46 +02:00
parent 19f6b70d63
commit fb5fbc320b
No known key found for this signature in database
GPG Key ID: 33EBBFC47B3DD87D
3 changed files with 15 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -32,8 +32,11 @@ Source code repository
Bug database
------------
[Bugzilla](http://bugzilla.maptools.org/buglist.cgi?product=libtiff)
[GitLab issues](https://gitlab.com/libtiff/libtiff/issues)
Previously, the project used
[Bugzilla](http://bugzilla.maptools.org/buglist.cgi?product=libtiff). This
is no longer in use, and all remaining issues have been migrated to GitLab.
Use and Copyright
-----------------

19
html/bugs.html
View File

@ -14,19 +14,20 @@ This software is free. Please let us know when you find a problem or
fix a bug.
<P>
Thanks to <A HREF=http://www.maptools.org/>MapTools.org</a>, libtiff now uses
bugzilla to track bugs. All bugs filed in the older bugzilla at
The project is using <a href="https://gitlab.com/libtiff/libtiff/issues">
GitLab issues</a> since October 2019.
Previously, the project used MapTools.org
bugzilla to track bugs: remaining tickets in that bugzilla instance have been
migrated to GitLab issues. All bugs filed in a older bugzilla at
bugzilla.remotesensing.org (pre April 2008) have unfortunately been lost.
<P>
If you think you've discovered a bug, please first check to see if it is
already known by looking at the list of already reported bugs. You can do so
by visiting the buglist at
<A HREF=http://bugzilla.maptools.org/buglist.cgi?product=libtiff>http://bugzilla.maptools.org/buglist.cgi?product=libtiff</A>. Also verify that
already known by looking at the list of already reported bugs. Also verify that
the problem is still reproducible with the current development software
from CVS.
<P>
If you'd like to enter a new bug, you can do so at
<A HREF=http://bugzilla.maptools.org/enter_bug.cgi?product=libtiff>http://bugzilla.maptools.org/enter_bug.cgi?product=libtiff</A>.
<A HREF=https://gitlab.com/libtiff/libtiff/issues/new>https://gitlab.com/libtiff/libtiff/issues/new</A>.
<P>
If you'd like to inform us about some kind of security issue that should not
be disclosed for a period of time, then you can contact maintainers directly.
@ -37,12 +38,12 @@ Bob Friesenhahn
<P>
Of course, reporting bugs is no substitute for discussion. The
<a href="mailto:tiff@lists.maptools.org">tiff@lists.maptools.org</a> mailing
<a href="mailto:tiff@lists.osgeo.org">tiff@lists.osgeo.org</a> mailing
list is for users of this software, and discussion TIFF issues in general.
It is managed with the Mailman software, and the web interface for subscribing
and managing your access to the list is at:<p>
<a href="http://lists.maptools.org/mailman/listinfo/tiff">http://lists.maptools.org/mailman/listinfo/tiff</a><P>
<a href="http://lists.osgeo.org/mailman/listinfo/tiff">http://lists.osgeo.org/mailman/listinfo/tiff</a><P>
Posts to the list are only accepted from members of the list in order
to limit the amount of spam propagated.<p>
@ -56,6 +57,6 @@ Systems</a>. <p>
<HR>
Last updated: $Date: 2016-04-08 02:34:03 $
Last updated: 2019-10-01
</BODY>
</HTML>

2
html/index.html
View File

@ -100,7 +100,7 @@
<li><a href="contrib.html">Contributed software</a></li>
<li><a href="document.html">TIFF documentation</a></li>
<li><a href="build.html">Building the software distribution</a></li>
<li><a href="bugs.html">Bugs, Bugzilla, and the TIFF mailing list</a></li>
<li><a href="bugs.html">Bugs, GitLab issues, and the TIFF mailing list</a></li>
<li><a href="images.html">Test images</a></li>
<li><a href="misc.html">Acknowledgements and copyright issues</a></li>
<li><a href="man/index.html">Man Pages</a></li>