[Mesa-dev] [ANNOUNCE] mesa 20.0.5

Danylo Piliaiev danylo.piliaiev at gmail.com
Thu Apr 23 17:07:41 UTC 2020

On 23.04.20 19:56, Dylan Baker wrote:
> Quoting Michel Dänzer (2020-04-23 09:24:45)
>> On 2020-04-23 6:19 p.m., Mark Janes wrote:
>>> Michel Dänzer <michel at daenzer.net> writes:
>>>> On 2020-04-23 5:14 p.m., Mark Janes wrote:
>>>>> Does anyone have recommendations for how to use Gitlab to verify that
>>>>> there are no identified-but-unfixed bugs in a pending release?
>>>> I'd say GitLab milestones could be used to address the issues you raised
>>>> above: Create a milestone for each release, and only cut the release
>>>> once all issues and MRs assigned to it have been dealt with.
>>> Milestones have been used to track progress toward recent releases.  It
>>> is non-trivial to audit all open bugs to determine which ones must be
>>> assigned to a milestone.  Bugs are opened long before milestones are
>>> created.
>> Of course there are more complicated cases, but the particular case
>> which spawned this thread should have been pretty straightforward to
>> handle with a 20.0.5 milestone.
> Indeed, I like the milestone approach and I've gone ahead and created the
> milestone.
Yes, even if milestones don't alleviate all issues - at least it is better
than nothing, thanks!

More information about the mesa-dev mailing list