Hey Board,
Is there any way we can prioritize getting the successor to LP figured out? I know we're moving two big pieces of infrastructure in the near future (mailing lists and repo), but the spam from LP has had me far less engaged than I have been in the past with the bug tracker.
It doesn't seem like Canonical is going to put the resources behind fixing it (especially with recent cutbacks they've made). I don't want us to move to something less useful prematurely, but at the same time, LP is much less useful IMHO given how blueprints have been destroyed and we have false reports filling mailboxes (even if temporary, it's an inconvenience).
Cheers, Josh
On Fri, 2017-04-14 at 21:11 -0700, Josh Andler wrote:
Hey Board,
Is there any way we can prioritize getting the successor to LP figured out? I know we're moving two big pieces of infrastructure in the near future (mailing lists and repo), but the spam from LP has had me far less engaged than I have been in the past with the bug tracker.
It doesn't seem like Canonical is going to put the resources behind fixing it (especially with recent cutbacks they've made). I don't want us to move to something less useful prematurely, but at the same time, LP is much less useful IMHO given how blueprints have been destroyed and we have false reports filling mailboxes (even if temporary, it's an inconvenience).
To a degree, moving to Gitlab issues would allow us a bit of a fresh slate. But the process of moving would need to be done very carefully.
Firstly I'd recommend backing everything up from launchpad.
Then switching launchpad bugs tracker to "We manage our bugs somewhere else" this is so users are redirected correctly to our new issue tracker from old links.
With the old bugs (lots and lots and lots of them) we'd need to host them somewhere for archiving. Given my experience with getting things into gitlab, I don't really think it's useful to have them migrated. (But I'm willing to be convinced!)
Best Regards, Martin Owens
participants (2)
-
Josh Andler
-
Martin Owens