fdo-mirrors/cairo
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/cairo/cairo.git synced 2025-12-20 07:00:08 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

BUGS: update bug database links to use gitlab instead of bugzilla

Browse source 
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
This commit is contained in:
Alan Coopersmith 2024-09-30 18:58:00 -07:00
parent b9eed915f9
commit 6702561c74
2 changed files with 11 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
BUGS
View file

@ -6,22 +6,22 @@ extra effort users put in to providing high-quality bug reports.
There are two acceptable ways to report cairo bugs, and you can choose
which you prefer:
1) Bugzilla bug tracking database:
1) Gitlab bug tracking database:
You can use the following web interface to report new bugs, follow
up on previous bug reports, and search for existing, known
bugs. Just use the "cairo" product:
bugs:
https://bugs.freedesktop.org
https://gitlab.freedesktop.org/cairo/cairo/-/issues
It is necessary to go through a quick account creation process,
(with email address verification), in order to be able to report
new bugs in bugzilla. We apologize for any inconvenience that might
new bugs in gitlab. We apologize for any inconvenience that might
cause, and hope it won't prevent you from reporting bugs.
2) Cairo mailing list:
For people who cannot stand the bugzilla interface, you can just
For people who cannot stand the gitlab interface, you can just
send an email to cairo mailing list (cairo@cairographics.org). The
mailing list only allows posting from subscribers, so use the
following page for subscription instructions:
@ -39,8 +39,8 @@ which you prefer:
Which of the above you use to report bugs depends on your own
preferences. Some people find just typing an email message much easier
than using the web-based forms on bugzilla. Others greatly prefer the
ability to check back on a specific bug entry in bugzilla without
than using the web-based forms on gitlab. Others greatly prefer the
ability to check back on a specific bug entry in gitlab without
having to ask on the mailing list if an issue has been resolved.
Regardless of which method you use, here are some general tips that
@ -48,9 +48,8 @@ will help you improve the quality of your bug report, (which will help
in getting the bug fixed sooner):
1) Check to see if the bug has been reported already. It's pretty easy
to run a search or two against the cairo product in the
https://bugs.freedesktop.org bugzilla database. Another place to
look for known bugs is the cairo ROADMAP:
to run a search or two against the cairo product in the gitlab
database. Another place to look for known bugs is the cairo ROADMAP:
https://cairographics.org/ROADMAP

4
HACKING
View file

@ -46,9 +46,9 @@ the -commit and -bugs lists.
Bug Tracking System
-------------------
We use a standard bugzilla bug tracking system available at:
We use a standard gitlab bug tracking system available at:
https://bugs.freedesktop.org/
https://gitlab.freedesktop.org/cairo/cairo/-/issues
See file named BUGS for detailed information on reporting bugs. In short,
for straight bug reports, it's best to report them there such that they