On 2020-04-24 6:14 p.m., Denys wrote:
>
> Aslo, @Mark, in your last reply I saw that you asked about "parsing"
> merge-requests and comments/issues. If I understood the problem
> correctly, you may try my approach.
>
> I am using Thunderbird, and created 2 filters for pattern "Subject
>
Hello.
As we discussed this with @Danylo, milestones may help developers to be
aware, that their patches were/will be nominated to the next release.
They will get notification about this and (according to our
expectations) will review these patches. It is ideal case, for sure, but
this will
Michel Dänzer writes:
> On 2020-04-23 8:37 p.m., Mark Janes wrote:
>> - search for issues mentioning a test name (unless it is in the title)
>
> https://gitlab.freedesktop.org/mesa/mesa/-/issues?scope=all=%E2%9C%93=opened=test
>
> lists issues without "test" in the title, so this doesn't seem
-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 writes:
On 2020-04-23 5:14 p.m., Mark Janes wrote:
>
> Does anyone have
On 2020-04-23 8:37 p.m., Mark Janes wrote:
>
> The majority of stable point releases will have zero issues in a
> release milestone. Opening/closing empty milestones all the time is a
> lot of busy work.
If a few clicks & keystrokes is really "a lot of busy work", only
creating a milestone when
