| Message ID | 20240514085801.3202503-1-thomas.petazzoni@bootlin.com |
|---|---|
| State | Accepted |
| Headers | show |
| Series | docs, package/gcc: switch to Gitlab issue tracker | expand |
Hello, On Tue, 14 May 2024 10:58:00 +0200 Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote: > Our Bugzilla is so slow and unstable that it has become > unusable. Let's switch to using the Gitlab issue tracker instead. > > There are still lots of references to the Bugzilla bug tracker in our > News page at https://buildroot.org/news.html, but these are for older > news. > > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> I was wondering if the other maintainers had any feedback on this patch? Thanks! Thomas
Hello Thomas, On 13/06/24 23:41, Thomas Petazzoni via buildroot wrote: > Hello, > > On Tue, 14 May 2024 10:58:00 +0200 > Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote: > >> Our Bugzilla is so slow and unstable that it has become >> unusable. Let's switch to using the Gitlab issue tracker instead. >> >> There are still lots of references to the Bugzilla bug tracker in our >> News page at https://buildroot.org/news.html, but these are for older >> news. >> >> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> > > I was wondering if the other maintainers had any feedback on this patch? I'm not a Maintainer, but I use Gitlab daily with Issues since 1 year in team and in generale I find it a good tool. As bug tracker is pretty good also because of Labels we could define to better address the bug. This has been tested at my Customer's Gitlab with 3 different final customers in Horeca sector. Both developers and final customers have been happy since 2 year with many projects started and finished and still maintaining(I count 10 circa). And all the above can be done with the free license with no problem. These are my 2 cents. Best regards
Thomas, All, On 2024-05-14 10:58 +0200, Thomas Petazzoni via buildroot spake thusly: > Our Bugzilla is so slow and unstable that it has become > unusable. Let's switch to using the Gitlab issue tracker instead. It would have been nice if you had suggested a plan to deal with the existing issues. We can extract the list of bugs from Bugzilla (as CSV): https://bugs.busybox.net/buglist.cgi?bug_status=__all__&limit=0&list_id=26023&product=buildroot&query_format=specific&ctype=csv&human=1 And then we can extract individual bugs (as XML): https://bugs.busybox.net/show_bug.cgi?ctype=xml&id=3 Gitlab can import from CSV: https://docs.gitlab.com/ee/user/project/issues/csv_import.html However, the Gitlab import is ultra limited: it can only import issues as a title, a description, a due date (optional), and a milestone (optional). There is no place for comments, attachments, status... So, what do we do for the existing issues? Regards, Yann E. MORIN. > There are still lots of references to the Bugzilla bug tracker in our > News page at https://buildroot.org/news.html, but these are for older > news. > > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> > --- > docs/manual/contribute.adoc | 2 +- > docs/manual/resources.adoc | 2 +- > docs/website/contribute.html | 2 +- > docs/website/support.html | 5 +++-- > package/gcc/gcc.mk | 2 +- > 5 files changed, 7 insertions(+), 6 deletions(-) > > diff --git a/docs/manual/contribute.adoc b/docs/manual/contribute.adoc > index 6ff6c15314..c88035597e 100644 > --- a/docs/manual/contribute.adoc > +++ b/docs/manual/contribute.adoc > @@ -25,7 +25,7 @@ for more information on obtaining a Buildroot git tree. > === Reproducing, analyzing and fixing bugs > > A first way of contributing is to have a look at the open bug reports in > -the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot bug > +the https://gitlab.com/buildroot.org/buildroot/-/issues[Buildroot bug > tracker]. As we strive to keep the bug count as small as possible, all > help in reproducing, analyzing and fixing reported bugs is more than > welcome. Don't hesitate to add a comment to bug reports reporting your > diff --git a/docs/manual/resources.adoc b/docs/manual/resources.adoc > index 68b7eb9062..4ef709c317 100644 > --- a/docs/manual/resources.adoc > +++ b/docs/manual/resources.adoc > @@ -40,7 +40,7 @@ better as it will reach more people, both developers and users. > Bug tracker:: > + > Bugs in Buildroot can be reported via the mailing list or alternatively > -via the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot > +via the https://gitlab.com/buildroot.org/buildroot/-/issues[Buildroot > bugtracker]. Please refer to xref:reporting-bugs[] before creating a bug > report. > > diff --git a/docs/website/contribute.html b/docs/website/contribute.html > index aa1cf93f1b..95028ee788 100644 > --- a/docs/website/contribute.html > +++ b/docs/website/contribute.html > @@ -13,7 +13,7 @@ > > <ul> > <li>Reproducing, analyzing and fixing bugs from our > - <a href="https://bugs.buildroot.org/">bug tracker</a></li> > + <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">bug tracker</a></li> > <li>Analyzing and fixing <a href="http://autobuild.buildroot.org/"> > autobuild failures</a></li> > <li>Reviewing and testing patches sent by other developers. See the > diff --git a/docs/website/support.html b/docs/website/support.html > index 28873c6d76..75551b770e 100644 > --- a/docs/website/support.html > +++ b/docs/website/support.html > @@ -80,8 +80,9 @@ > <img class="img-responsive" src="images/bug-buddy.png" style="max-width:50px; margin-bottom:10px;"> > </div> > <div class="col-sm-11"> > - <p>If you think you found a bug in Buildroot, you can use the > - <a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or > + <p>If you think you found a bug in Buildroot, you > + can use the > + <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">Bug Tracker</a> to post your bugs and/or > participate to find solutions to existing problems.</p> > > <p>Note: patches are only accepted through the mailing list.</p> > diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk > index 672f9472a9..e4780353cb 100644 > --- a/package/gcc/gcc.mk > +++ b/package/gcc/gcc.mk > @@ -83,7 +83,7 @@ HOST_GCC_COMMON_CONF_OPTS = \ > --with-mpc=$(HOST_DIR) \ > --with-mpfr=$(HOST_DIR) \ > --with-pkgversion="Buildroot $(BR2_VERSION_FULL)" \ > - --with-bugurl="http://bugs.buildroot.net/" \ > + --with-bugurl="https://gitlab.com/buildroot.org/buildroot/-/issues" \ > --without-zstd > > ifeq ($(BR2_REPRODUCIBLE),y) > -- > 2.45.0 > > _______________________________________________ > buildroot mailing list > buildroot@buildroot.org > https://lists.buildroot.org/mailman/listinfo/buildroot
On Sat, 15 Jun 2024 10:08:13 +0200 "Yann E. MORIN" <yann.morin.1998@free.fr> wrote: > It would have been nice if you had suggested a plan to deal with the > existing issues. Indeed, but there was a reason, see below :-) > We can extract the list of bugs from Bugzilla (as CSV): > https://bugs.busybox.net/buglist.cgi?bug_status=__all__&limit=0&list_id=26023&product=buildroot&query_format=specific&ctype=csv&human=1 > > And then we can extract individual bugs (as XML): > https://bugs.busybox.net/show_bug.cgi?ctype=xml&id=3 > > Gitlab can import from CSV: > https://docs.gitlab.com/ee/user/project/issues/csv_import.html > > However, the Gitlab import is ultra limited: it can only import issues > as a title, a description, a due date (optional), and a milestone > (optional). > > There is no place for comments, attachments, status... > > So, what do we do for the existing issues? My plan was to have no plan at all, and simply "ignore" the existing issues. But alternatively, we could do a massive close of all existing open issues with a message saying that we moved to Gitlab and that if the issue still exists, it should be reopened in Gitlab. To me, this is probably good enough. Thomas
Thomas, All, On 2024-06-15 14:46 +0200, Thomas Petazzoni spake thusly: > On Sat, 15 Jun 2024 10:08:13 +0200 > "Yann E. MORIN" <yann.morin.1998@free.fr> wrote: > > > It would have been nice if you had suggested a plan to deal with the > > existing issues. [--SNIP--] > My plan was to have no plan at all, and simply "ignore" the existing > issues. But alternatively, we could do a massive close of all existing > open issues with a message saying that we moved to Gitlab and that if > the issue still exists, it should be reopened in Gitlab. > To me, this is probably good enough. I am fine with that. Regards, Yann E. MORIN.
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes: > Thomas, All, > On 2024-06-15 14:46 +0200, Thomas Petazzoni spake thusly: >> On Sat, 15 Jun 2024 10:08:13 +0200 >> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote: >> >> > It would have been nice if you had suggested a plan to deal with the >> > existing issues. > [--SNIP--] >> My plan was to have no plan at all, and simply "ignore" the existing >> issues. But alternatively, we could do a massive close of all existing >> open issues with a message saying that we moved to Gitlab and that if >> the issue still exists, it should be reopened in Gitlab. >> To me, this is probably good enough. > I am fine with that. yeah, me too. I don't think we have a lot of very interesting open issues.
Thomas, All, On 2024-05-14 10:58 +0200, Thomas Petazzoni via buildroot spake thusly: > Our Bugzilla is so slow and unstable that it has become > unusable. Let's switch to using the Gitlab issue tracker instead. > > There are still lots of references to the Bugzilla bug tracker in our > News page at https://buildroot.org/news.html, but these are for older > news. > > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [--SNIP--] > diff --git a/docs/website/support.html b/docs/website/support.html > index 28873c6d76..75551b770e 100644 > --- a/docs/website/support.html > +++ b/docs/website/support.html > @@ -80,8 +80,9 @@ > <img class="img-responsive" src="images/bug-buddy.png" style="max-width:50px; margin-bottom:10px;"> > </div> > <div class="col-sm-11"> > - <p>If you think you found a bug in Buildroot, you can use the > - <a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or > + <p>If you think you found a bug in Buildroot, you > + can use the Spurious reflow; I dropped it. Applied to master, thanks. As planned with your non-plan, I'm planning on planing out old bug tracker, and closing still-opened issues. Still, it would be nice if we could get an issue template for new issues that will be opened in our shinny new bug tracker. Regards, Yann E. MORIN. > + <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">Bug Tracker</a> to post your bugs and/or > participate to find solutions to existing problems.</p> > > <p>Note: patches are only accepted through the mailing list.</p> > diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk > index 672f9472a9..e4780353cb 100644 > --- a/package/gcc/gcc.mk > +++ b/package/gcc/gcc.mk > @@ -83,7 +83,7 @@ HOST_GCC_COMMON_CONF_OPTS = \ > --with-mpc=$(HOST_DIR) \ > --with-mpfr=$(HOST_DIR) \ > --with-pkgversion="Buildroot $(BR2_VERSION_FULL)" \ > - --with-bugurl="http://bugs.buildroot.net/" \ > + --with-bugurl="https://gitlab.com/buildroot.org/buildroot/-/issues" \ > --without-zstd > > ifeq ($(BR2_REPRODUCIBLE),y) > -- > 2.45.0 > > _______________________________________________ > buildroot mailing list > buildroot@buildroot.org > https://lists.buildroot.org/mailman/listinfo/buildroot
diff --git a/docs/manual/contribute.adoc b/docs/manual/contribute.adoc index 6ff6c15314..c88035597e 100644 --- a/docs/manual/contribute.adoc +++ b/docs/manual/contribute.adoc @@ -25,7 +25,7 @@ for more information on obtaining a Buildroot git tree. === Reproducing, analyzing and fixing bugs A first way of contributing is to have a look at the open bug reports in -the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot bug +the https://gitlab.com/buildroot.org/buildroot/-/issues[Buildroot bug tracker]. As we strive to keep the bug count as small as possible, all help in reproducing, analyzing and fixing reported bugs is more than welcome. Don't hesitate to add a comment to bug reports reporting your diff --git a/docs/manual/resources.adoc b/docs/manual/resources.adoc index 68b7eb9062..4ef709c317 100644 --- a/docs/manual/resources.adoc +++ b/docs/manual/resources.adoc @@ -40,7 +40,7 @@ better as it will reach more people, both developers and users. Bug tracker:: + Bugs in Buildroot can be reported via the mailing list or alternatively -via the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot +via the https://gitlab.com/buildroot.org/buildroot/-/issues[Buildroot bugtracker]. Please refer to xref:reporting-bugs[] before creating a bug report. diff --git a/docs/website/contribute.html b/docs/website/contribute.html index aa1cf93f1b..95028ee788 100644 --- a/docs/website/contribute.html +++ b/docs/website/contribute.html @@ -13,7 +13,7 @@ <ul> <li>Reproducing, analyzing and fixing bugs from our - <a href="https://bugs.buildroot.org/">bug tracker</a></li> + <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">bug tracker</a></li> <li>Analyzing and fixing <a href="http://autobuild.buildroot.org/"> autobuild failures</a></li> <li>Reviewing and testing patches sent by other developers. See the diff --git a/docs/website/support.html b/docs/website/support.html index 28873c6d76..75551b770e 100644 --- a/docs/website/support.html +++ b/docs/website/support.html @@ -80,8 +80,9 @@ <img class="img-responsive" src="images/bug-buddy.png" style="max-width:50px; margin-bottom:10px;"> </div> <div class="col-sm-11"> - <p>If you think you found a bug in Buildroot, you can use the - <a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or + <p>If you think you found a bug in Buildroot, you + can use the + <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">Bug Tracker</a> to post your bugs and/or participate to find solutions to existing problems.</p> <p>Note: patches are only accepted through the mailing list.</p> diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk index 672f9472a9..e4780353cb 100644 --- a/package/gcc/gcc.mk +++ b/package/gcc/gcc.mk @@ -83,7 +83,7 @@ HOST_GCC_COMMON_CONF_OPTS = \ --with-mpc=$(HOST_DIR) \ --with-mpfr=$(HOST_DIR) \ --with-pkgversion="Buildroot $(BR2_VERSION_FULL)" \ - --with-bugurl="http://bugs.buildroot.net/" \ + --with-bugurl="https://gitlab.com/buildroot.org/buildroot/-/issues" \ --without-zstd ifeq ($(BR2_REPRODUCIBLE),y)
Our Bugzilla is so slow and unstable that it has become unusable. Let's switch to using the Gitlab issue tracker instead. There are still lots of references to the Bugzilla bug tracker in our News page at https://buildroot.org/news.html, but these are for older news. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> --- docs/manual/contribute.adoc | 2 +- docs/manual/resources.adoc | 2 +- docs/website/contribute.html | 2 +- docs/website/support.html | 5 +++-- package/gcc/gcc.mk | 2 +- 5 files changed, 7 insertions(+), 6 deletions(-)