Re: Migrating to the gitlab issue tracker

["Daniel P. Berrangé" <berrange@redhat.com>]

On Fri, Oct 30, 2020 at 10:03:44AM +0000, Peter Maydell wrote:
> On Fri, 30 Oct 2020 at 09:23, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > My convincing strategy is "do nothing" :-)
> 
> I am, er, not convinced :-)
> 
> > Most importantly we need to be able to make the existing "QEMU" component
> > in launch read-only to prevent people filing new bugs there, ideally with
> > a change in the description to point people to the new bug tracker.
> >
> > We can leave existing bugs in LP to continue their discussion. If there
> > are some we explicitly want in gitlab manually re-file them. Aside from
> > that if we periodically auto-close any stale bugs, after a while we'll
> > have culled launchpad down to zero.
> 
> Minimally, we should have an easy way to refile specific bugs
> that doesn't involve manual cut-n-paste. Most of the Arm bugs
> in launchpad are valid, for instance, I think, and I really
> don't want to be spending a day in unnecessary clerical work
> copying information into gitlab...

Auto-migrating content is easy enough. The challenge is user accounts,
because theres no mapping from launchpad to gitlab. If you just
import issues using a generic account, then you loose the communication
with the original bug report in a large portion of migrated bugs. This
makes it more appealing to leave existing bugs in the LP tracker until
they are resolved, auto-closed, or there is a compelling reason to move
to gitlab.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|