[Releasing] https://bugreports.qt-project.org/browse/QTBUG-35143 :Scene graph threaded render loop deadlocks on X11

Turunen Tuukka Tuukka.Turunen at digia.com
Wed Nov 27 23:18:38 CET 2013


On 27.11.2013 17.30, "Ziller Eike" <Eike.Ziller at digia.com> wrote:

>
>On Nov 27, 2013, at 3:59 PM, Knoll Lars <Lars.Knoll at digia.com> wrote:
>
>> 
>> 
>> On 27/11/13 15:03, "Heikkinen Jani" <Jani.Heikkinen at digia.com> wrote:
>>> 
>>> Hi all,
>>>  
>>> This issue is P0 and so on blocking the RC1 at the moment. There is
>>>already fix proposals available but those aren¹t passing the CI
>>>  
>>> https://codereview.qt-project.org/#change,72183 : This seems to be
>>>real failure and fix needed before re-stage
>>> https://codereview.qt-project.org/#change,72535 : Failure seems to be
>>>unrelated to change and that¹s why re-staged
>>>  
>>> Because we don¹t have these through CI yet it means it will be
>>>impossible to get packages with these fixes tomorrow morning. If we get
>>>these through CI soon and after that qt5.git can be integrated without
>>>problems it might be possible to get packages during tomorrow. But what
>>>if we couldn¹t get these packages tomorrow? I recommend that we release
>>>RC1 on Friday and fix issue on final.
>>> 
>> It would be very good to get the fixes in, but I don't believe we
>>should delay the RC a lot further because of them. The hanging of the
>>render loop can apparently be worked around by setting the
>>QSG_RENDER_LOOP environment variable to basic.
>
>
>> But then we'd somehow need to make sure it's being set in the packages
>>for creator.
>
>What side effects would that have? There must be some reason why that
>isn¹t the default ;)
>
>Also I have actually very bad feelings regarding releasing on a friday.
>We had a policy not to do that, what has happened with that?


Any production release should be done Tue - Thu, if at all possible. But
for development release, like this RC, basically any day is good.

I really would like to have the RC out either tomorrow or Friday so that
we would get some testing ongoing during the weekend already. It has been
a while since the beta and pretty much all valid feedback on that has been
received long ago. Having much less that two weeks between RC and Final
most likely does not work as it takes some time to get the feedback - and
making the final release the last week before holidays does not sound
tempting at all.

So I would be inclined to say we have this bug in the known issues and get
the RC out Thursday or Friday, unless there is something new that makes it
impossible. Especially since the issue apparently does not happen in the
reference configurations and can be worked around, I do not see this a P0
/ blocker for the RC.

Yours,

		Tuukka








More information about the Releasing mailing list