Quoting Daniel Stone (2019-08-30 14:13:08) > Hi, > > On Thu, 29 Aug 2019 at 21:35, Chris Wilson <ch...@chris-wilson.co.uk> wrote: > > Quoting Kristian Høgsberg (2019-08-29 21:20:12) > > > On Thu, Aug 29, 2019 at 12:44 PM Chris Wilson <ch...@chris-wilson.co.uk> > > > wrote: > > > > Quoting Kenneth Graunke (2019-08-29 19:52:51) > > > > > - Moving bug reports between the kernel and Mesa would be harder. > > > > > We would have to open a bug in the other system. (Then again, > > > > > moving bugs between Mesa and X or Wayland would be easier...) > > > > > > > > All that I ask is that we move the kernel bugzilla along with it. Trying > > > > to keep abreast of the bugs in the whole stack is important. Fwiw, the > > > > kernel contains the > > > > https:////bugs.freedesktop.org/enter_bug.cgi?product=DRI > > > > URL so would need some redirection for a few years... > > > > > > Would Rob's suggestion of creating a placeholder drm kernel repo for > > > the purpose of issue tracking work for you? > > We can definitely get placeholder DRM repos and move those issues too. > And set up redirects. > > (To be honest, rather than one-by-one redirects, my thought with > Bugzilla was just to statically scrape all the bug pages and leave > them as read-only static copies frozen in amber for time eternal. I'd > welcome help from anyone who had the time to figure out the scripting > and Apache runes required to make those be proper HTTP redirects, but > am definitely not going to be able to do that myself.)
I'd be happy with a static page telling them how to file a new issue on gitlab. > > I think so. I just want a list of all bugs that may affect the code I'm > > working on, wherever they were filed. I have a search in bugs.fdo, I > > just need instructions on how to get the same from gitlab, hopefully in > > a compact format. > > It's not clear to me what you need. Can you please give more details? At the moment, I always have open a couple of searches which are basically Product: DRI, Mesa, xorg Component: Driver/intel, Drivers/DRI/i830, Drivers/DRI/i915, Drivers/DRI/i965, Drivers/Vulkan/intel, DRM/AMDgpu, DRM/Intel, IGT Status: NEW, ASSIGNED, REOPENED, NEEDINFO I would like a similar way of getting a quick glance at the issues under discussion and any new issues across the products -- basically I want a heads up in case I've broken something, however subtle. And sometimes you just need to trawl through every bug in case you missed something. > If you want cross-component search results in a single list, that's > not really something we can do today, and I don't know if it would > land any time soon. You can however subscribe to particular issue > labels, and when you see something that catches your eye add a 'todo' > for it, then the main UI shows all your outstanding todos, including > where people have mentioned you etc. One thing we did for bugzilla was set the default QA component to a mailing list, so we had a single place to subscribe to get all the spam. I presume something similar would be available to subscribe to every issue across a range of categories. > > The issue URL will also need to be stable so that we can include it in > > commits. From a glance, > > https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/861, > > looks like it will be adjusted if it ever gets moved. > > Sorry, 'moved' how? If you mean moved between components, yes the > issue will move and there will be a new URL for that. However, going > to that old URL will auto-redirect you to the new one. That's fine. I was just worrying about old links becoming stale, or worse replaced, if the issue was moved (or whatever). -Chris _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
