After the move to GitLab, figure out how to batch-close tickets on LaunchPad

[nekohayo]

I changed the https://launchpad.net/gtg to say this on the front page:

❗We do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to visit our web page and find the new location where our code and bug reports are hosted 🔶 Do NOT download any code or tarballs from LaunchPad, as they are severely outdated and unsupported.

...but there are still 321 old bugs open there, either things that were fixed but not yet released ("Fix committed"), or things that are old bugs that either got silently solved or are obsolete or referencing broken plugins, or non-actionable somehow due to the sheer number.

When issue #234 is done, and 0.4 is officially released, we'll need a polite canned message to indicate that everything has been moved out of LaunchPad and into GitLab, and that if their issue still happens with the latest version provided as a Flatpak, and it is a bug (or a feature that the person is willing to work on) then they need to re-file it cleanly on our GitLab issue tracker.

And then we'll need a way to change the status of those LaunchPad bugs in a batch. In 14 years, LaunchPad never implemented batch bug processing, so my only hope (short of having to deal with each and every ticket manually) would be to batch-process via email somehow: https://answers.launchpad.net/launchpad/+question/34961 and https://help.launchpad.net/Bugs/EmailInterface?action=show&redirect=BugTrackerEmailInterface ...so that users that were waiting for fixes over there can be called into action to test the new release.

[nekohayo]

Looking at the docs linked above, I see I need to be using a GPG key, and still would need to go through pages of bug listings to extract the bug numbers and somehow clean up that information... at that point I suspect it'll be faster for me to just spend an hour or two brute-forcing my way through the ~300 LaunchPad tickets manually with my web browser, rather than to figure out how to interact with Launchpad via email and "hoping" that it works...

[nekohayo]

So I went ahead and JFDI'ed manually by spending 90 minutes going through the 319 LaunchPad tickets to close them. A fair amount of them (especially startup/quit crashers, dependency problems, etc.) can be considered "fix released" with 0.4, roughly a dozen remain open with "fix committed" targetted at 0.5 because of the current ongoing work; as for the rest, I just marked them Invalid or "Won't fix", usually with an explanation to point to the new project location.