Re: [Buildroot] [PATCH] docs, package/gcc: switch to Gitlab issue tracker

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

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 Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot