[librsvg/gitlab-migration] Change git and bugzilla URLs to gitlab

commit 52fb0440470c91f61283baad9a5c1e5cb8364d94
Author: Federico Mena Quintero <federico gnome org>
Date:   Wed Dec 13 21:55:13 2017 -0600

    Change git and bugzilla URLs to gitlab
    We still need to rename test files to match the new bug numbers...

 CONTRIBUTING.md    | 33 +++++++++++++++++++--------------
 README.md          |  2 +-
 configure.ac       |  2 +-
 librsvg.doap       |  3 ++-
 rsvg-cairo-draw.c  |  2 +-
 rust/src/marker.rs |  2 +-
 tests/README.md    |  8 ++++++--
 tests/styles.c     |  1 -
 8 files changed, 31 insertions(+), 22 deletions(-)
index 3f7c594..ab7da73 100644
@@ -14,10 +14,10 @@ file [`code_of_conduct.md`][coc].
 ## Source repository
-Librsvg's main source repository is at git.gnome.org.  You can view
+Librsvg's main source repository is at gitlab.gnome.org.  You can view
 the web interface here:
 Development happens in the master branch.  There are also branches for
 stable releases.
@@ -30,11 +30,12 @@ Note that we don't do bug tracking in the Github mirror; see the next
 If you need to publish a branch, feel free to do it at any
-publically-accessible Git hosting service.
+publically-accessible Git hosting service, although gitlab.gnome.org
+makes things easier for the maintainers of librsvg.
 ## Reporting bugs
-Please report bugs at http://bugzilla.gnome.org/enter_bug.cgi?product=librsvg
+Please report bugs at https://gitlab.gnome.org/GNOME/librsvg/issues
 If you want to report a rendering bug, or a missing SVG feature,
 please provide an example SVG file as an attachment to your bug
@@ -61,18 +62,22 @@ directed there.
 It is especially helpful if you file bug for a feature request along
 with a sample SVG file.
-## Pull requests
+## Merge requests / pull requests
-You may upload a forked version of librsvg to [GNOME's Gitlab
+You may created a forked version of librsvg in [GNOME's Gitlab
 instance][gitlab], or any other publically-accesible Git hosting
+service.  You can register an account there, or log in with your
+account from other OAuth services.
-For technical reasons, the maintainers of librsvg do not get
-automatically notified if you submit a pull request through Github.
-[Please mail the maintainer][mail] directly if you have a pull request
-there or a branch that you would like to contribute.
+Note that the maintainers of librsvg only get notified about merge
+requests (or pull requests) if your fork is in
-Alternatively, you can use [GNOME's Gitlab][gitlab] instead.
+For technical reasons, the maintainers of librsvg do not get
+automatically notified if you submit a pull request through the GNOME
+mirror in Github.  [Please mail the maintainer][mail] directly if you
+have a pull request there or a branch that you would like to
 **Test suite:** Please make sure that the test suite passes with the
 changes in your branch.  The easiest way to run all the tests is to go
@@ -85,7 +90,7 @@ things that we weren't testing!), or for additional information on how
 the test suite works, please see the file [`tests/README.md`][tests-readme].
 [coc]: code_of_conduct.md
-[gitlab]: https://gitlab.gnome.org/
-[bugs-browse]: https://bugzilla.gnome.org/page.cgi?id=browse.html&product=librsvg
+[gitlab]: https://gitlab.gnome.org/GNOME/librsvg
+[bugs-browse]: https://gitlab.gnome.org/GNOME/librsvg/issues
 [mail]: mailto:federico gnome org
 [tests-readme]: tests/README.md
diff --git a/README.md b/README.md
index ed46537..40f284a 100644
--- a/README.md
+++ b/README.md
@@ -94,7 +94,7 @@ can [mail me][mail] for any other questions you have about librsvg.
 [compiling]: COMPILING.md
 [docs]: https://developer.gnome.org/rsvg/stable/
 [mail]: mailto:federico gnome org
-[bugs]: https://bugzilla.gnome.org/page.cgi?id=browse.html&product=librsvg
+[bugs]: https://gitlab.gnome.org/GNOME/librsvg/issues
 [gi]: https://wiki.gnome.org/Projects/GObjectIntrospection
 [contributing]: CONTRIBUTING.md
 [reporting-bugs]: CONTRIBUTING.md#reporting-bugs
diff --git a/configure.ac b/configure.ac
index 16c5f69..821e6b7 100644
--- a/configure.ac
+++ b/configure.ac
@@ -5,7 +5,7 @@ m4_define([rsvg_extra_version],[])
 m4_define([rsvg_lt_version_info],m4_eval(rsvg_major_version + 
diff --git a/librsvg.doap b/librsvg.doap
index 9a2f8d1..7f47d9e 100644
--- a/librsvg.doap
+++ b/librsvg.doap
@@ -17,9 +17,10 @@
   <homepage rdf:resource="https://wiki.gnome.org/action/show/Projects/LibRsvg"; />
   <mailing-list rdf:resource="https://mail.gnome.org/mailman/listinfo/desktop-devel-list"; />
   <download-page rdf:resource="https://download.gnome.org/sources/librsvg/"; />
-  <bug-database rdf:resource="https://bugzilla.gnome.org/browse.cgi?product=librsvg"; />
+  <bug-database rdf:resource="https://gitlab.gnome.org/GNOME/librsvg/issues"; />
   <category rdf:resource="http://api.gnome.org/doap-extensions#deprecated"; />
+  <programming-language>Rust</programming-language>
diff --git a/rsvg-cairo-draw.c b/rsvg-cairo-draw.c
index 6cc792b..f16a39a 100644
--- a/rsvg-cairo-draw.c
+++ b/rsvg-cairo-draw.c
@@ -358,7 +358,7 @@ rsvg_cairo_render_path_builder (RsvgDrawingCtx * ctx, RsvgPathBuilder *builder)
      * viewports/clipping, and one for user applications like a
      * rsvg_compute_ink_rect() function in the future.
-     * See https://bugzilla.gnome.org/show_bug.cgi?id=760112 for discussion of a
+     * See https://gitlab.gnome.org/GNOME/librsvg/issues/128 for discussion of a
      * public API to get the ink rectangle.
diff --git a/rust/src/marker.rs b/rust/src/marker.rs
index 092b076..cff75bd 100644
--- a/rust/src/marker.rs
+++ b/rust/src/marker.rs
@@ -1173,7 +1173,7 @@ mod marker_tests {
-    // https://bugzilla.gnome.org/show_bug.cgi?id=777854
+    // https://gitlab.gnome.org/GNOME/librsvg/issues/161
     fn emits_for_closed_subpath () {
         let mut builder = RsvgPathBuilder::new ();
         builder.move_to (0.0, 0.0);
diff --git a/tests/README.md b/tests/README.md
index 62dcf12..df0f938 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -87,8 +87,12 @@ As of 2016/Nov/03 we have an informal organization of these files:
   by one as librsvg starts implementing the features.
 * `fixtures/reftests/bugs/*.svg` - Tests for particular bug numbers.
-  Please use the bug number from Bugzilla, like `123456.svg`, and the
-  corresponding `123456-ref.png` for the known-good reference image.
+  Please use the bug number from Gitlab, like `1234.svg`, and the
+  corresponding `1234-ref.png` for the known-good reference image.
+  **Note:** Librsvg migrated from git.gnome.org and bugzilla.gnome.org
+  to gitlab.gnome.org.  Bug numbers in Bugzilla were around 6 digits
+  in length; in Gitlab, they are small numbers.
 * `fixtures/reftests/*.svg` - Tests for special situations
   that arose during development.
diff --git a/tests/styles.c b/tests/styles.c
index ae90f62..1af4f0b 100644
--- a/tests/styles.c
+++ b/tests/styles.c
@@ -117,7 +117,6 @@ main (int argc, char *argv[])
     g_test_init (&argc, &argv, NULL);
-    g_test_bug_base ("https://bugzilla.gnome.org/show_bug.cgi?id=";);
     for (i = 0; i < n_fixtures; i++)
         g_test_add_data_func (fixtures[i].test_name, &fixtures[i], (void*)test_value);

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]