Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On Wed, Sep 18, 2019 at 8:45 AM Adam Jackson wrote:
>
> 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.
Thanks Adam! I moved the freedreno bugs from krh/mesa to mesa/mesa.
For reference, here's the commandline I pieced together from Adam's
pointers:
https://docs.gitlab.com/ee/api/issues.html#move-an-issue
and
https://gitlab.freedesktop.org/profile/personal_access_tokens
and then:
for i in {1..46}; do echo move issue $i; curl --header "PRIVATE-TOKEN:
$token" --form to_project_id=176
https://gitlab.freedesktop.org/api/v4/projects/420/issues/$i/move;
echo; done
Kristian
> 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
>
> ___
> mesa-dev mailing list
> mesa-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
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 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On 04/09/2019 21:01, Daniel Vetter wrote: > On Wed, Sep 4, 2019 at 6:52 PM Adam Jackson wrote: >> >> On Fri, 2019-08-30 at 14:26 +0100, Chris Wilson wrote: >>> Quoting Daniel Stone (2019-08-30 14:13:08) Hi, On Thu, 29 Aug 2019 at 21:35, Chris Wilson wrote: > > 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. >> >> You can do a top-level search for arbitrary strings, and get a list of >> matching issues: >> >> https://gitlab.freedesktop.org/search?group_id=_id=_ref==issues=i965 >> >> But that's perhaps not super useful. There's no way to globally search >> for issues with a particular label, probably because labels are scoped >> either to projects or groups and not site-wide. But you _do_ get >> project-wide labels, so we could promote mesa/mesa's i965 label to be >> usable from mesa/*. The xorg project has this already for some labels: I found a way to do global searches: https://gitlab.freedesktop.org/dashboard/issues/?scope=all=%E2%9C%93=opened_name[]=1.%20Security However, it looks like there isn't a way to browse bugs from multiple projects from one. I guess you would have to check two links (mesa group, and drm group) to get what you are looking for unless there would be common tags/author/assignee/milestone. You can also subscribe to the RSS feeds for issues, which could allow a local rss client to display all the bugs you might be interested in. Would any of that be acceptable? >> >> https://gitlab.freedesktop.org/groups/xorg/-/labels >> https://gitlab.freedesktop.org/groups/xorg/-/issues?scope=all=%E2%9C%93=opened_name[]=gsoc >> >> This probably implies that we'd want the kernel repo to be a mesa >> subproject. And then you'd just have top-level label searches for the >> xorg and mesa projects. > > Looking at https://gitlab.freedesktop.org/drm and > https://cgit.freedesktop.org/drm we have the following list of kernel > projects we'd need to move: > - overall drm (really probably want no bug reports on that, Dave > ignore them all anyway or at most redirect to subtrees) > - drm-misc > - drm-intel > - amgpu tree > - msm > - nouveau is somewhere else, probably wants to keep its separate > bugzilla component too > - anything else that's not maintained in one of the above perhaps > (it's marginal, but might happen) > - igt > - libdrm (currently under gitlab/mesa/drm) > - maintainer-tools (not going to have a real need for reassigning bugs > with any of the above, but why leave it out) > > btw for git repo reasons at least drm-misc, drm and drm-intel need to > be in a group of their own, for acl reasons. Or at least we need a > group somwhere for these, so we can give them all access to drm-tip. > But that's only for once we move the git repos, but I kinda don't want > to move everything once more again. I don't think putting everything under mesa would make sense at all for access control and general organisation reasons. Let's please keep the mesa and drm groups separate. Cross-referencing of issues is possible using the mesa/mesa#12345 syntax, or simply using the full link: https://gitlab.freedesktop.org/mesa/vulkan-wsi-layer/issues/4 I am in favor of always using the full link, since it would allow people with a local git repo to easily access the related bug. And speaking about this, the kernel commit messages should stop using "Bugzilla: https://; and move to "Closes: https://...;. As for moving the i915 bugs already, this is doable after a small change to the gztogl that would convert custom fields to tags. I can try to get this done next week. Thoughts anyone? Martin > -Daniel > 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
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
+1 Quoting Kenneth Graunke (2019-08-29 11:52:51) > Hi all, > > As a lot of you have probably noticed, Bugzilla seems to be getting a > lot of spam these days - several of us have been disabling a bunch of > accounts per day, sweeping new reports under the rug, hiding comments, > etc. This bug spam causes emails to be sent (more spam!) and then us > to have to look at ancient bugs that suddenly have updates. > > I think it's probably time to consider switching away from Bugzilla. > We are one of the few projects remaining - Mesa, DRM, and a few DDX > drivers are still there, but almost all other projects are gone: > > https://bugs.freedesktop.org/enter_bug.cgi > > Originally, I was in favor of retaining Bugzilla just to not change too > many processes all at once. But we've been using Gitlab a while now, > and several of us have been using Gitlab issues in our personal repos; > it's actually pretty nice. > > Some niceities: > > - Bug reporters don't necessarily need to sign up for an account > anymore. They can sign in with their Gitlab.com, Github, Google, > or Twitter accounts. Or make one as before. This may be nicer for > reporters that don't want to open yet another account just to report > an issue to us. > > - Anti-spam support is actually maintained. Bugzilla makes it near > impossible to actually delete garbage, Gitlab makes it easier. It > has a better account creation hurdle than Bugzilla's ancient captcha, > and Akismet plug-ins for handling spam. > > - The search interface is more modern and easier to use IMO. > > - Permissions & accounts are easier - it's the same unified system. > > - Easy linking between issues and MRs - mention one in the other, and > both get updated with cross-links so you don't miss any discussion. > > - Milestone tracking > > - This could be handy for release trackers - both features people > want to land, and bugs blocking the release. > > - We could also use it for big efforts like direct state access, > getting feature parity with fglrx, or whatnot. > > - Khronos switched a while ago as well, so a number of us are already > familiar with using it there. > > Some cons: > > - 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...) > > 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. > > --Ken > > > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On Wed, Sep 4, 2019 at 6:52 PM Adam Jackson wrote: > > On Fri, 2019-08-30 at 14:26 +0100, Chris Wilson wrote: > > Quoting Daniel Stone (2019-08-30 14:13:08) > > > Hi, > > > > > > On Thu, 29 Aug 2019 at 21:35, Chris Wilson > > > wrote: > > > > > > > > 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. > > You can do a top-level search for arbitrary strings, and get a list of > matching issues: > > https://gitlab.freedesktop.org/search?group_id=_id=_ref==issues=i965 > > But that's perhaps not super useful. There's no way to globally search > for issues with a particular label, probably because labels are scoped > either to projects or groups and not site-wide. But you _do_ get > project-wide labels, so we could promote mesa/mesa's i965 label to be > usable from mesa/*. The xorg project has this already for some labels: > > https://gitlab.freedesktop.org/groups/xorg/-/labels > https://gitlab.freedesktop.org/groups/xorg/-/issues?scope=all=%E2%9C%93=opened_name[]=gsoc > > This probably implies that we'd want the kernel repo to be a mesa > subproject. And then you'd just have top-level label searches for the > xorg and mesa projects. Looking at https://gitlab.freedesktop.org/drm and https://cgit.freedesktop.org/drm we have the following list of kernel projects we'd need to move: - overall drm (really probably want no bug reports on that, Dave ignore them all anyway or at most redirect to subtrees) - drm-misc - drm-intel - amgpu tree - msm - nouveau is somewhere else, probably wants to keep its separate bugzilla component too - anything else that's not maintained in one of the above perhaps (it's marginal, but might happen) - igt - libdrm (currently under gitlab/mesa/drm) - maintainer-tools (not going to have a real need for reassigning bugs with any of the above, but why leave it out) btw for git repo reasons at least drm-misc, drm and drm-intel need to be in a group of their own, for acl reasons. Or at least we need a group somwhere for these, so we can give them all access to drm-tip. But that's only for once we move the git repos, but I kinda don't want to move everything once more again. -Daniel > > > 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. > > You (individually) can subscribe to a label (per-project-or-group), > yes. Subscribing a mailing list to a label is somewhat awkward since > the email address for an account is where things like password reset > requests get sent. > > - ajax > > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On Fri, 2019-08-30 at 14:26 +0100, Chris Wilson wrote: > Quoting Daniel Stone (2019-08-30 14:13:08) > > Hi, > > > > On Thu, 29 Aug 2019 at 21:35, Chris Wilson wrote: > > > > > > 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. You can do a top-level search for arbitrary strings, and get a list of matching issues: https://gitlab.freedesktop.org/search?group_id=_id=_ref==issues=i965 But that's perhaps not super useful. There's no way to globally search for issues with a particular label, probably because labels are scoped either to projects or groups and not site-wide. But you _do_ get project-wide labels, so we could promote mesa/mesa's i965 label to be usable from mesa/*. The xorg project has this already for some labels: https://gitlab.freedesktop.org/groups/xorg/-/labels https://gitlab.freedesktop.org/groups/xorg/-/issues?scope=all=%E2%9C%93=opened_name[]=gsoc This probably implies that we'd want the kernel repo to be a mesa subproject. And then you'd just have top-level label searches for the xorg and mesa projects. > > 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. You (individually) can subscribe to a label (per-project-or-group), yes. Subscribing a mailing list to a label is somewhat awkward since the email address for an account is where things like password reset requests get sent. - ajax ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
Just adding to the pile of :+1: I think an empty repo for drm with just issues enabled is a good solution. On Thursday, 2019-08-29 11:52:51 -0700, Kenneth Graunke wrote: > Hi all, > > As a lot of you have probably noticed, Bugzilla seems to be getting a > lot of spam these days - several of us have been disabling a bunch of > accounts per day, sweeping new reports under the rug, hiding comments, > etc. This bug spam causes emails to be sent (more spam!) and then us > to have to look at ancient bugs that suddenly have updates. > > I think it's probably time to consider switching away from Bugzilla. > We are one of the few projects remaining - Mesa, DRM, and a few DDX > drivers are still there, but almost all other projects are gone: > > https://bugs.freedesktop.org/enter_bug.cgi > > Originally, I was in favor of retaining Bugzilla just to not change too > many processes all at once. But we've been using Gitlab a while now, > and several of us have been using Gitlab issues in our personal repos; > it's actually pretty nice. > > Some niceities: > > - Bug reporters don't necessarily need to sign up for an account > anymore. They can sign in with their Gitlab.com, Github, Google, > or Twitter accounts. Or make one as before. This may be nicer for > reporters that don't want to open yet another account just to report > an issue to us. > > - Anti-spam support is actually maintained. Bugzilla makes it near > impossible to actually delete garbage, Gitlab makes it easier. It > has a better account creation hurdle than Bugzilla's ancient captcha, > and Akismet plug-ins for handling spam. > > - The search interface is more modern and easier to use IMO. > > - Permissions & accounts are easier - it's the same unified system. > > - Easy linking between issues and MRs - mention one in the other, and > both get updated with cross-links so you don't miss any discussion. > > - Milestone tracking > > - This could be handy for release trackers - both features people > want to land, and bugs blocking the release. > > - We could also use it for big efforts like direct state access, > getting feature parity with fglrx, or whatnot. > > - Khronos switched a while ago as well, so a number of us are already > familiar with using it there. > > Some cons: > > - 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...) > > 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. > > --Ken > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
Quoting Daniel Stone (2019-08-30 14:13:08) > Hi, > > On Thu, 29 Aug 2019 at 21:35, Chris Wilson wrote: > > Quoting Kristian Høgsberg (2019-08-29 21:20:12) > > > On Thu, Aug 29, 2019 at 12:44 PM Chris Wilson > > > 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
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
Hi, On Thu, 29 Aug 2019 at 21:35, Chris Wilson wrote: > Quoting Kristian Høgsberg (2019-08-29 21:20:12) > > On Thu, Aug 29, 2019 at 12:44 PM Chris Wilson > > 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 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? 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. > 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. Cheers, Daniel ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On 2019-08-29 9:36 p.m., Rob Clark wrote: > On Thu, Aug 29, 2019 at 12:02 PM Kenneth Graunke > wrote: >> >> - 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...) > > If that was a concern, we could setup a kernel gitlab project that has > an empty git repository (at least until we are ready to move drm git > tree). Yeah, the obvious solution for this is to migrate everything that's left together (which is what I've been asking all along :). Given that, I'm in favour. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
+1 On 8/29/19 8:52 PM, Kenneth Graunke wrote: Hi all, As a lot of you have probably noticed, Bugzilla seems to be getting a lot of spam these days - several of us have been disabling a bunch of accounts per day, sweeping new reports under the rug, hiding comments, etc. This bug spam causes emails to be sent (more spam!) and then us to have to look at ancient bugs that suddenly have updates. I think it's probably time to consider switching away from Bugzilla. We are one of the few projects remaining - Mesa, DRM, and a few DDX drivers are still there, but almost all other projects are gone: https://bugs.freedesktop.org/enter_bug.cgi Originally, I was in favor of retaining Bugzilla just to not change too many processes all at once. But we've been using Gitlab a while now, and several of us have been using Gitlab issues in our personal repos; it's actually pretty nice. Some niceities: - Bug reporters don't necessarily need to sign up for an account anymore. They can sign in with their Gitlab.com, Github, Google, or Twitter accounts. Or make one as before. This may be nicer for reporters that don't want to open yet another account just to report an issue to us. - Anti-spam support is actually maintained. Bugzilla makes it near impossible to actually delete garbage, Gitlab makes it easier. It has a better account creation hurdle than Bugzilla's ancient captcha, and Akismet plug-ins for handling spam. - The search interface is more modern and easier to use IMO. - Permissions & accounts are easier - it's the same unified system. - Easy linking between issues and MRs - mention one in the other, and both get updated with cross-links so you don't miss any discussion. - Milestone tracking - This could be handy for release trackers - both features people want to land, and bugs blocking the release. - We could also use it for big efforts like direct state access, getting feature parity with fglrx, or whatnot. - Khronos switched a while ago as well, so a number of us are already familiar with using it there. Some cons: - 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...) 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. --Ken ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
Kenneth Graunke writes: > [ Unknown signature status ] > Hi all, > > As a lot of you have probably noticed, Bugzilla seems to be getting a > lot of spam these days - several of us have been disabling a bunch of > accounts per day, sweeping new reports under the rug, hiding comments, > etc. This bug spam causes emails to be sent (more spam!) and then us > to have to look at ancient bugs that suddenly have updates. > > I think it's probably time to consider switching away from Bugzilla. > We are one of the few projects remaining - Mesa, DRM, and a few DDX > drivers are still there, but almost all other projects are gone: > > https://bugs.freedesktop.org/enter_bug.cgi > > Originally, I was in favor of retaining Bugzilla just to not change too > many processes all at once. But we've been using Gitlab a while now, > and several of us have been using Gitlab issues in our personal repos; > it's actually pretty nice. Yes, please. I haven't been participating in bugzilla, in favor of personal github and krh's mesa gitlab. signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
Quoting Kristian Høgsberg (2019-08-29 21:20:12) > On Thu, Aug 29, 2019 at 12:44 PM Chris Wilson > wrote: > > > > Quoting Kenneth Graunke (2019-08-29 19:52:51) > > > Some cons: > > > > > > - 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? 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. 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. -Chris ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On Thu, Aug 29, 2019 at 12:44 PM Chris Wilson wrote: > > Quoting Kenneth Graunke (2019-08-29 19:52:51) > > Some cons: > > > > - 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? Kristian > -Chris > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
Quoting Kenneth Graunke (2019-08-29 19:52:51) > Some cons: > > - 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... -Chris ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
+1 On Thu, Aug 29, 2019 at 2:36 PM Rob Clark wrote: > On Thu, Aug 29, 2019 at 12:02 PM Kenneth Graunke > wrote: > > > > Hi all, > > > > As a lot of you have probably noticed, Bugzilla seems to be getting a > > lot of spam these days - several of us have been disabling a bunch of > > accounts per day, sweeping new reports under the rug, hiding comments, > > etc. This bug spam causes emails to be sent (more spam!) and then us > > to have to look at ancient bugs that suddenly have updates. > > > > I think it's probably time to consider switching away from Bugzilla. > > We are one of the few projects remaining - Mesa, DRM, and a few DDX > > drivers are still there, but almost all other projects are gone: > > > > https://bugs.freedesktop.org/enter_bug.cgi > > > > Originally, I was in favor of retaining Bugzilla just to not change too > > many processes all at once. But we've been using Gitlab a while now, > > and several of us have been using Gitlab issues in our personal repos; > > it's actually pretty nice. > > > > Some niceities: > > > > - Bug reporters don't necessarily need to sign up for an account > > anymore. They can sign in with their Gitlab.com, Github, Google, > > or Twitter accounts. Or make one as before. This may be nicer for > > reporters that don't want to open yet another account just to report > > an issue to us. > > > > - Anti-spam support is actually maintained. Bugzilla makes it near > > impossible to actually delete garbage, Gitlab makes it easier. It > > has a better account creation hurdle than Bugzilla's ancient captcha, > > and Akismet plug-ins for handling spam. > > > > - The search interface is more modern and easier to use IMO. > > > > - Permissions & accounts are easier - it's the same unified system. > > > > - Easy linking between issues and MRs - mention one in the other, and > > both get updated with cross-links so you don't miss any discussion. > > > > - Milestone tracking > > > > - This could be handy for release trackers - both features people > > want to land, and bugs blocking the release. > > > > - We could also use it for big efforts like direct state access, > > getting feature parity with fglrx, or whatnot. > > > > - Khronos switched a while ago as well, so a number of us are already > > familiar with using it there. > > > > Some cons: > > > > - 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...) > > If that was a concern, we could setup a kernel gitlab project that has > an empty git repository (at least until we are ready to move drm git > tree). > > > 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. > > > > yes, please, let's move! > > BR, > -R > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On Thu, Aug 29, 2019 at 12:02 PM Kenneth Graunke wrote: > > Hi all, > > As a lot of you have probably noticed, Bugzilla seems to be getting a > lot of spam these days - several of us have been disabling a bunch of > accounts per day, sweeping new reports under the rug, hiding comments, > etc. This bug spam causes emails to be sent (more spam!) and then us > to have to look at ancient bugs that suddenly have updates. > > I think it's probably time to consider switching away from Bugzilla. > We are one of the few projects remaining - Mesa, DRM, and a few DDX > drivers are still there, but almost all other projects are gone: > > https://bugs.freedesktop.org/enter_bug.cgi > > Originally, I was in favor of retaining Bugzilla just to not change too > many processes all at once. But we've been using Gitlab a while now, > and several of us have been using Gitlab issues in our personal repos; > it's actually pretty nice. > > Some niceities: > > - Bug reporters don't necessarily need to sign up for an account > anymore. They can sign in with their Gitlab.com, Github, Google, > or Twitter accounts. Or make one as before. This may be nicer for > reporters that don't want to open yet another account just to report > an issue to us. > > - Anti-spam support is actually maintained. Bugzilla makes it near > impossible to actually delete garbage, Gitlab makes it easier. It > has a better account creation hurdle than Bugzilla's ancient captcha, > and Akismet plug-ins for handling spam. > > - The search interface is more modern and easier to use IMO. > > - Permissions & accounts are easier - it's the same unified system. > > - Easy linking between issues and MRs - mention one in the other, and > both get updated with cross-links so you don't miss any discussion. > > - Milestone tracking > > - This could be handy for release trackers - both features people > want to land, and bugs blocking the release. > > - We could also use it for big efforts like direct state access, > getting feature parity with fglrx, or whatnot. > > - Khronos switched a while ago as well, so a number of us are already > familiar with using it there. > > Some cons: > > - 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...) If that was a concern, we could setup a kernel gitlab project that has an empty git repository (at least until we are ready to move drm git tree). > 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. > yes, please, let's move! BR, -R ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
On Thu, Aug 29, 2019 at 12:02 PM Kenneth Graunke wrote: > > Hi all, > > As a lot of you have probably noticed, Bugzilla seems to be getting a > lot of spam these days - several of us have been disabling a bunch of > accounts per day, sweeping new reports under the rug, hiding comments, > etc. This bug spam causes emails to be sent (more spam!) and then us > to have to look at ancient bugs that suddenly have updates. > > I think it's probably time to consider switching away from Bugzilla. > We are one of the few projects remaining - Mesa, DRM, and a few DDX > drivers are still there, but almost all other projects are gone: > > https://bugs.freedesktop.org/enter_bug.cgi > > Originally, I was in favor of retaining Bugzilla just to not change too > many processes all at once. But we've been using Gitlab a while now, > and several of us have been using Gitlab issues in our personal repos; > it's actually pretty nice. > > Some niceities: > > - Bug reporters don't necessarily need to sign up for an account > anymore. They can sign in with their Gitlab.com, Github, Google, > or Twitter accounts. Or make one as before. This may be nicer for > reporters that don't want to open yet another account just to report > an issue to us. > > - Anti-spam support is actually maintained. Bugzilla makes it near > impossible to actually delete garbage, Gitlab makes it easier. It > has a better account creation hurdle than Bugzilla's ancient captcha, > and Akismet plug-ins for handling spam. > > - The search interface is more modern and easier to use IMO. > > - Permissions & accounts are easier - it's the same unified system. > > - Easy linking between issues and MRs - mention one in the other, and > both get updated with cross-links so you don't miss any discussion. > > - Milestone tracking > > - This could be handy for release trackers - both features people > want to land, and bugs blocking the release. > > - We could also use it for big efforts like direct state access, > getting feature parity with fglrx, or whatnot. > > - Khronos switched a while ago as well, so a number of us are already > familiar with using it there. > > Some cons: > > - 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...) > > 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. Definitely in favor here. We've been using it for tracking freedreno issues over in my gitlab mesa, but would much prefer to use the main repo. Kristian > --Ken > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] Switching to Gitlab Issues instead of Bugzilla?
Hi all, As a lot of you have probably noticed, Bugzilla seems to be getting a lot of spam these days - several of us have been disabling a bunch of accounts per day, sweeping new reports under the rug, hiding comments, etc. This bug spam causes emails to be sent (more spam!) and then us to have to look at ancient bugs that suddenly have updates. I think it's probably time to consider switching away from Bugzilla. We are one of the few projects remaining - Mesa, DRM, and a few DDX drivers are still there, but almost all other projects are gone: https://bugs.freedesktop.org/enter_bug.cgi Originally, I was in favor of retaining Bugzilla just to not change too many processes all at once. But we've been using Gitlab a while now, and several of us have been using Gitlab issues in our personal repos; it's actually pretty nice. Some niceities: - Bug reporters don't necessarily need to sign up for an account anymore. They can sign in with their Gitlab.com, Github, Google, or Twitter accounts. Or make one as before. This may be nicer for reporters that don't want to open yet another account just to report an issue to us. - Anti-spam support is actually maintained. Bugzilla makes it near impossible to actually delete garbage, Gitlab makes it easier. It has a better account creation hurdle than Bugzilla's ancient captcha, and Akismet plug-ins for handling spam. - The search interface is more modern and easier to use IMO. - Permissions & accounts are easier - it's the same unified system. - Easy linking between issues and MRs - mention one in the other, and both get updated with cross-links so you don't miss any discussion. - Milestone tracking - This could be handy for release trackers - both features people want to land, and bugs blocking the release. - We could also use it for big efforts like direct state access, getting feature parity with fglrx, or whatnot. - Khronos switched a while ago as well, so a number of us are already familiar with using it there. Some cons: - 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...) 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. --Ken signature.asc Description: This is a digitally signed message part. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
