On Sat, Jul 14, 2018 at 7:56 AM, Volodymyr Vysotskyi <[email protected]> wrote: > Hello Julian, > > Sorry for bothering in non-working hours.
No worries! Work never stops. Thanks for working during your weekend, also. I replied to the dev list, since this concerns the release and development. (Usually I don't reply to personal emails on a public list, but I took the liberty this time, since there didn't seem to be anything sensitive/personal in your message. Hope that's OK.) > One of the steps in the instruction for preparing the release is triggering > a Coverity scan by merging the latest code into the julianhyde/coverity_scan > branch. > > I have created PR with the latest changes from the master: PR-13. > > Could you please merge this PR to trigger a Coverity scan or please let me > know if this step is optional and may be omitted. I have merged to julianhyde/coverity_scan. I'll forward the coverity results to you (and the dev list) when I get them. The coverity scan has become optional - we have skipped it for the last few releases. I expect the scan will turn up some interesting warnings, but it will be difficult to tell whether any are show-stoppers without significant time and effort. Therefore I recommend that we don't let the coverity results hold back the release. We can analyze them in the background, and fix any issues we find with appropriate urgency. Julian
