[Mesa-dev] [ANNOUNCE] mesa 20.0.5

[Michel Dänzer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2020-04-23 6:56 p.m., 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.

And I set it as the milestone for Danylo's issue & MR.


One gotcha is that both of these will show up as
completed/closed/merged on the milestone once the MR is merged to
master. At least in some cases it might be better to make a separate
MR for the stable staging branch and set the milestone on that as
well, to make sure they stay on the radar until the fix is on the
stable branch.


- -- 
Earthling Michel Dänzer               |               https://redhat.com
Libre software enthusiast             |             Mesa and X developer
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSwn681vpFFIZgJURRaga+OatuyAAUCXqKhIwAKCRBaga+Oatuy
AJaSAKCsKxCMp+EXfnlTjFd9uwwBDga0FwCgstcb+B5OwOfGTheQArey5W8kH3s=
=OLqq
-----END PGP SIGNATURE-----