Commit 19c1ea58 authored by Nick Wellnhofer's avatar Nick Wellnhofer

Change bug tracker URL

parent e8381180
......@@ -10,7 +10,7 @@ Otherwise, only Bjorn Reese (breese@users.sourceforge.net),
<igor@zlatkovic.com> and me (veillard@redhat.com)
should commit there. John Fleck also have commit rights for the doc
subdir. Send a mail and if it's a bug issue, provide a test case and
register it at bugzilla.gnome.org in the libxslt module.
register it at https://gitlab.gnome.org/GNOME/libxslt/issues .
I check both my mail and the bug database on a very regular basis.
if you don't get an answer within a week (which is highly unprobable)
then commit your changes. This simply mean that I am on holliday or
......
......@@ -161,7 +161,7 @@
<li><a href="http://www.zlatkovic.com/projects/libxml/">Windows binaries</a></li>
<li><a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
<li><a href="http://www.explain.com.au/oss/libxml2xslt.html">MacOsX binaries</a></li>
<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxslt">Bug Tracker</a></li>
<li><a href="https://gitlab.gnome.org/GNOME/libxslt/issues">Bug Tracker</a></li>
<li><a href="http://codespeak.net/lxml/">lxml Python bindings</a></li>
<li><a href="http://cpan.uwinnipeg.ca/dist/XML-LibXSLT">Perl XSLT bindings</a></li>
<li><a href="http://www.zend.com/php5/articles/php5-xmlphp.php#Heading17">XSLT with PHP</a></li>
......
......@@ -99,10 +99,10 @@ useful resources:</p>
<p>Well, bugs or missing features are always possible, and I will make a
point of fixing them in a timely fashion. The best way to report a bug is to
use the <a
href="http://bugzilla.gnome.org/enter_bug.cgi?product=libxslt">GNOME bug
href="https://gitlab.gnome.org/GNOME/libxslt/issues">GNOME bug
tracking database</a> (make sure to use the "libxslt" module name). Before
filing a bug, check the <a
href="http://bugzilla.gnome.org/buglist.cgi?product=libxslt">list of existing
href="https://gitlab.gnome.org/GNOME/libxslt/issues">list of existing
libxslt bugs</a> to make sure it hasn't already been filed. I look at reports
there regularly and it's good to have a reminder when a bug is still open. Be
sure to specify that the bug is for the package libxslt.</p>
......@@ -151,7 +151,7 @@ posting</span>:</p>
<li>check the <a href="http://mail.gnome.org/archives/xslt/">list
archives</a> to see if the problem was reported already, in this case
there is probably a fix available, similarly check the <a
href="http://bugzilla.gnome.org/buglist.cgi?product=libxslt">registered
href="https://gitlab.gnome.org/GNOME/libxslt/issues">registered
open bugs</a></li>
<li>make sure you can reproduce the bug with xsltproc, a very useful thing
to do is run the transformation with -v argument and redirect the
......@@ -170,7 +170,7 @@ answer a given question, ask on the list.</p>
<p>To <span style="color: #E50000">be really clear about support</span>:</p>
<ul>
<li>Support or help <span style="color: #E50000">request MUST be sent to
the list or on bugzilla</span> in case of problems, so that the Question
the list or the bug tracker</span> in case of problems, so that the Question
and Answers can be shared publicly. Failing to do so carries the implicit
message "I want free support but I don't want to share the benefits with
others" and is not welcome. I will automatically Carbon-Copy the
......@@ -201,7 +201,7 @@ it's a good starting point.</p>
<p>You can help the project in various ways, the best thing to do first is to
subscribe to the mailing-list as explained before, check the <a
href="http://mail.gnome.org/archives/xslt/">archives </a>and the <a
href="http://bugzilla.gnome.org/buglist.cgi?product=libxslt">GNOME bug
href="https://gitlab.gnome.org/GNOME/libxslt/issues">GNOME bug
database:</a>:</p>
<ol>
<li>provide patches when you find problems</li>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment