[Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?

Adam Jackson ajax at redhat.com
Wed Sep 18 15:45:01 UTC 2019


On Thu, 2019-08-29 at 11:52 -0700, Kenneth Graunke wrote:

> What do people think?  If folks are in favor, Daniel can migrate
> everything for us, like he did with the other projects.  If not,
> I'd like to hear what people's concerns are.

It's been almost three weeks, and this seems to have resulted in broad
consensus and very little objection, mostly around how to build
searches effectively. So, let's do it.

I've enabled filing issues for the remaining mesa projects that didn't
have it already (vkpipeline-db, shader-db, drm, and mesa itself). I
also turned merge requests on for mesa/drm (which is just libdrm, not
the kernel). I'll be going through bugzilla for the Mesa and DRI
products and migrating or closing bugs as appropriate. After each
component is migrated it will be closed for bug entry, so there will be
a small window here where bugs can be filed in two places, hopefully
this shouldn't cause too much confusion.

The remaining bikeshed here is the drm kernel repository, and
relatedly, what to do with bugs that are kernel issues. For now I'm
going to handle that by trying to avoid migrating obvious kernel
issues. There's the outline of a migration plan already in:

https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/69

If the kernel maintainers are ready to move the canonical repo URL and
issues, then let's get that moving sooner rather than later.

For progress on the migration, suggestions about how and where to move
issues, etc., please see:

https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/190

- ajax



More information about the mesa-dev mailing list