https://bugs.freedesktop.org/show_bug.cgi?id=111444
Adam Jackson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|MOVED
https://bugs.freedesktop.org/show_bug.cgi?id=111444
--- Comment #4 from Mark Janes ---
I thought we were going to leave the 19.2 tracker bugs in bugzilla until after
the release. The migration of this bug doesn't hurt the release, because we
can still see the list of bugs that need to be resolve
On Wed, 2019-09-18 at 23:41 +0200, Bas Nieuwenhuizen wrote:
> Has anybody put any though in how to best manage things here? e.g.
> some process, or do we want some form of automatic labeling, or is my
> concern overblown?
Well, there's the list of issues with no label:
https://gitlab.freedesktop
On 2019-09-18 9:15 p.m., Adam Jackson wrote:
> On Wed, 2019-09-18 at 12:08 -0700, Mark Janes wrote:
>>
>>> We'll also need to replace the Bugzilla: tag with a tag that gitlab
>>> recognizes
>>> for closing issues. Since we already use "Fixes:" for something else, I'd
>>> like
>>> to propose "Clos
Quoting Juan A. Suarez Romero (2019-09-19 04:26:53)
> On Wed, 2019-09-18 at 12:08 -0700, Mark Janes wrote:
> > Adding the release managers to the CC to make sure they see the thread...
> >
> > Dylan Baker writes:
> >
> > > Hi everyone,
> > >
> > > Since we're migrating to gitlab issues, it seem
https://bugs.freedesktop.org/show_bug.cgi?id=111444
--- Comment #3 from Adam Jackson ---
See also the 19.2 release milestone in gitlab:
https://gitlab.freedesktop.org/mesa/mesa/-/milestones/1
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for t
On Wed, 2019-09-18 at 12:08 -0700, Mark Janes wrote:
> Adding the release managers to the CC to make sure they see the thread...
>
> Dylan Baker writes:
>
> > Hi everyone,
> >
> > Since we're migrating to gitlab issues, it seems like a good time to review
> > how
> > we track stable releases,
During playing with notifications, I found out that actually gitlab
allows to subscribe to exact labels
https://about.gitlab.com/2016/04/13/feature-highlight-subscribe-to-label/
So, this may sort part of the issues related to "be up-to-date"
according to interesting things in the big project.
That's sad fact of gitlab, agree. The only thing came into mind - to get
a "template" for issue, which should include all important information
in the Summary
(example - Intel. Vulkan. GPU hand during playing dota ...)
There are many better ways to do this, for example, simply make a map of
a
