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
> useful
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?
>>>
>>> I
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 w
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 identified-but-un
Due to a recent spat of regressions in the mesa stable branch and some
miscommunication about the status of these issues, we're going to experiment
with using a gitlab milestone for each stable release. If there are issues or
MRs that need to be resolved before the next release please ensure that t
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 p
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" th
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 be
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: C
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 2120f1
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
> (https:
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
(https://gitlab.freedesktop.org/mesa/mesa/-/c
12 matches
Mail list logo
