[Mesa-dev] Mesa 19.1.0 release plan

[Eero Tamminen]

Hi,

On 16.4.2019 11.38, Juan A. Suarez Romero wrote:
> On Mon, 2019-04-15 at 18:57 +0300, Eero Tamminen wrote:
>> On 15.4.2019 17.15, Juan A. Suarez Romero wrote:
>>> Here is the tentative release plan for 19.1.0.
>>>
>>> As many of you are well aware, it's time to the next branch point.
>>> The calendar is already updated, so these are the tentative dates:
>>>
>>>    Apr 30 2019 - Feature freeze/Release candidate 1
>>>    May 07 2019 - Release candidate 2
>>>    May 14 2019 - Release candidate 3
>>>    May 21 2019 - Release candidate 4/final release
>>>
>>> This gives us around 2 weeks until the branch point.
>>>
>>> Note: In the spirit of keeping things clearer and more transparent, we
>>> will be keeping track of any features planned for the release in
>>> Bugzilla [1].
>>>
>>> Do add a separate "Depends on" for each work you have planned.
>>> Alternatively you can reply to this email and I'll add them for you.
>>>
>>> [1] https://bugs.freedesktop.org/show_bug.cgi?id=110439
>>
>> Should the current GPU hang bugs initially be blockers for that?

I'm asking because I assume that GPU hangs are serious enough issues, 
that they should be checked out before release.

At least if they have reproducible test-case and/or error state files.


>> For example the remaining (open) mesa-19.0 blocker bug:
>> 	https://bugs.freedesktop.org/show_bug.cgi?id=108820
> 
> I understand as 19.0 was released anyway, that issue is not actually a blocker.

So it seems.

If it would have worked according to process (as I understand it), some 
Mesa developer should have looked at the bug, decided that it's not a 
blocker, and removed it from the dependencies before release, instead of 
it just being ignored.

(I had added the bug as blocker after getting confirmation from list 
that regressions from previous release can be added as such.)


>> (There has been no comment for the attached error states from Mesa devs
>> since Lionel's initial comment 4 months ago, e.g. on whether Jakub's and
>> my cases are same or should they be filed as separate bugs.)


	- Eero