[Development] About our CI update notifications

[Adam Treat]

Speaking of...

https://codereview.qt-project.org/#/c/223224/

That integration is stuck and I don't know how to stop it and restage 
it. Apparently, the Windows 7 (mingw53-x86) VM crashed and COIN is not 
aware of that due to these:

 1. https://bugreports.qt.io/browse/QTQAINFRA-1750
 2. https://bugreports.qt.io/browse/QTQAINFRA-1748

Anyone know how to stop the integration so I can restage?

Cheers,

Adam


On 03/15/2018 09:35 AM, Adam Treat wrote:
> I would not regard this as excess spam at all. It is important to know 
> when the CI is not available and what the status is. If a restart or 
> scheduled update of any kind requires to restage commits for COIN, 
> please include that info.
>
> On 03/15/2018 04:26 AM, Tony Sarajärvi wrote:
>>
>> Hi
>>
>> We’re trying to improve our communication toward you regarding our CI 
>> and what’s going on with it. So our suggestion comes as follows:
>>
>> ·- In case of a scheduled update, we send an e-mail to the public 
>> developer mailing list the day before
>>
>> ·- In case of emergency update or pure restart, no notifications are 
>> needed
>>
>> ·- If Coin is unavailable for more than 30 min, we send an e-mail to 
>> the public developer mail list and inform about it followed by an 
>> e-mail when it’s back up again.
>>
>> ·- Keep community updated in case of prolonged downtime
>>
>> ·- We mention a contact address where e-mails should be sent if 
>> abnormalities are seen after the update/restart, usually qt.ci 
>> <http://qt.ci/>@qt.io <http://qt.io/>
>>
>> How does this sound to you recipients of these e-mails? Enough or 
>> would this be excess spam to some degree?
>>
>> -Tony
>>
>
>
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180315/fd811fd0/attachment.html>