Humnm, we can have different coverity scan branches if we want to analyze
several releases. Anyway is no problem for me to wait to 3.6 :).
2017-08-07 19:25 GMT+02:00 Robert Osfield <robert.osfi...@gmail.com>:
> On 7 August 2017 at 16:40, Jordi Torres <jtorresfa...@gmail.com> wrote:
>> Can I ask for a coverity_scan build before tagging the release?
> You can indeed ask :-)
> The coverity_scan is based on master rather than the 3.4 branch so it
> won't affect the 3.4.1 release.
> Doing a converity_scan and fix cycle is on my TODO list, should get to it
> soon as there haven't been many issues with 3.4.1 reported for me to chase
> up :-)
> osg-users mailing list
osg-users mailing list