[arch-dev-public] Bug tracker migration

Jelle van der Waa jelle at vdwaa.nl
Sun Aug 30 14:21:29 UTC 2020

On 30/08/2020 01:02, Frederik Schwan via arch-dev-public wrote:
> Hi folks,
> I'd like to migrate the beloved Flyspray bug tracker to our new Gitlab instance.


> - Bug wrangling day on the 13th of September; see 1)
> - Flyspray will be read-only after we rewrite the Archweb URLs
> - new bug tracker -> Gitlab
> 1) I'd like to hold a bug wrangling day, where our goal is to close as many bugs as possible.
>    Any TU, Reporter and bug wrangler is invited to help out :) Unfortunately I can't offer any cookies that day :/

This is coordinated on #archlinux-bugs on Freenode right?

>    Rules:
>      a) Bug with no reply for at least 6 months which has been submitted for a different version than the current one in 
>         the repos shall be closed with a message that a reopen request may be filled if this issue is still present.

I think we have a lot of issues which are fixable but the packager has
not been able to do it yet. In my opinion we should also try to fix as
much packages as possible, which everyone should be able to do.

>      b) Any infrastructure ticket shall not be touched. This will be handled by $DevOps.

What infrastructure tickets are there on flyspray? What about other
projects such as aurweb, pacman etc?

> 2) Afterwards we will point the bug tracker links in the Archweb to the new location and opening new tickets in Flyspray
>    will be disabled. The project structure of the future Gitlab bug tracker will be discussed in a seperate mail and
>    is not part of this mail(thread).

It would be amazing if this goes together with the Git migration, how
would the bug tracker on Gitlab work for community/core/extra?

> 3) When enough tickets are closed or when $DevOps is tired enough of Flyspray, we'll migrate the rest of the tickets to 
>    Gitlab. We seek to keep Flyspray as a static homepage to allow the reference in the new bug tracker to old tickets and
>    to keep the integrity of search engine results.

Can you create an isse on the infrastructure repository with these
steps? Would be nice to keep track of the progress in a central location.


Jelle van der Waa

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20200830/63356ebe/attachment.sig>

More information about the arch-dev-public mailing list