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
I don't think this was preventable given how many things went wrong.
Sometimes we have to accept that shit happens. We can fix that in the next
release.
Marek
On Thu., Apr. 23, 2020, 07:01 Danylo Piliaiev,
wrote:
> I want to sum up what happened from my perspective, I think it could be
>
Michel Dänzer writes:
> 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 recommendations for how to use Gitlab to verify that
there are no identified-but-unfixed bugs in a pending release?
>>>
>>>
While we talked about the general communication issues, I want to finish
with this
particular one.
Is this release going out as normal and the fix will be in the next
20.0.6 on 2020-04-29?
The current scope of the regression is non-iris drivers or iris compiled
without llvm.
The regression
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 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
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 recommendations for how to use Gitlab to verify that
> >>> there are no identified-but-unfixed bugs in a
On Thu, Apr 23, 2020 at 08:14:59AM -0700, Mark Janes wrote:
Danylo Piliaiev writes:
I want to sum up what happened from my perspective, I think it could be
useful to improve the process:
1) There was a regression in 20.*
(https://gitlab.freedesktop.org/mesa/mesa/-/issues/2758)
2) I "fixed"
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 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
Michel Dänzer 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:
On 2020-04-23 5:14 p.m., Mark Janes wrote:
> Danylo Piliaiev writes:
>
> 3a) Bisected regressions tagged with Fixes or mesa-stable are
> automatically applied to Mesa's release branch.
>
> This failure point has burned us many times, most recently with the 20.0
> regression fixed by
Danylo Piliaiev writes:
> I want to sum up what happened from my perspective, I think it could be
> useful to improve the process:
>
> 1) There was a regression in 20.*
> (https://gitlab.freedesktop.org/mesa/mesa/-/issues/2758)
> 2) I "fixed" the regression and broke non-iris drivers
>
I want to sum up what happened from my perspective, I think it could be
useful to improve the process:
1) There was a regression in 20.*
(https://gitlab.freedesktop.org/mesa/mesa/-/issues/2758)
2) I "fixed" the regression and broke non-iris drivers
On Thu, Apr 23, 2020 at 12:39 AM Dylan Baker wrote:
>
> Quoting Ilia Mirkin (2020-04-22 15:47:59)
> > On Wed, Apr 22, 2020 at 6:39 PM Danylo Piliaiev
> > wrote:
> > > I'm sorry for this trouble. However looking at it I think: maybe
> > > something could be
> > > changed about applying patches
Quoting Ilia Mirkin (2020-04-22 15:47:59)
> On Wed, Apr 22, 2020 at 6:39 PM Danylo Piliaiev
> wrote:
> > I'm sorry for this trouble. However looking at it I think: maybe something
> > could be
> > changed about applying patches to stable to safeguard against such issues.
>
> We used to get
This is particularly problematic, as that solved a regression in 20.0.4, and
we held up the release for that fix. The second patch is in the staging
branch and I can do an emergency release, but if there's another patch that's
needed then that doesn't help. I'm not sure that reverting the original
On Wed, Apr 22, 2020 at 6:39 PM Danylo Piliaiev
wrote:
> I'm sorry for this trouble. However looking at it I think: maybe something
> could be
> changed about applying patches to stable to safeguard against such issues.
We used to get pre-announcements a few days prior to a release which
would
My commit "st/mesa: Update shader info of ffvp/ARB_vp after translation
to NIR" did
introduce regression and its fix, which was merged (but isn't in this
release even though
there is "fixes" tag), didn't fully fix it.
See https://gitlab.freedesktop.org/mesa/mesa/-/issues/2815
This commit may
Hi list,
I'd like to announce the availability of mesa 20.0.5. It's one week late due to
a number of issues, including a regression in mesa, a regression in piglit, and
some CI trouble. I'm still planning to make 20.0.6 next week at it's secheduled
time.
This is a pretty big release, as it
22 matches
Mail list logo
