[Paraview] Dropping Qt 4 support from ParaView 5.5 onwards

Bruno Santos bruno.santos at bluecape.com.pt
Wed Jun 7 08:37:10 EDT 2017

+1 on either Qt 5.6 or 5.9 being the minimum

But for the sake of numbering sanity, shouldn't ParaView's version be 
bumped up to 6.0 instead of 5.5? Or at least 5.98 as a precursor to this 
rather big change?

Best regards,
Bruno Santos

On 06-06-2017 17:44, Michael Jackson wrote:
> +1.
>  Also I would vote to jump all the way to Qt 5.9 since it is a LTS 
> release and you can stabilize on Qt 5.9 for the next 3 years at least 
> where as Qt 5.6 is only supported in a security bug fix from here on 
> for another 2 years. I don't think Qt is going to add support for 
> newer operating systems so if something breaks on newer releases of 
> macOS or Windows Qt made it sound like they would not fix Qt 5.6
> Utkarsh Ayachit wrote:
>> Folks,
>> Continuing with dropping of support for legacy components, I wanted to
>> raise the question of dropping support for Qt older than 5.6 starting
>> with ParaView 5.5 (planned for Nov 2017).
>> Qt 5.6 has been out since March 2016 and is a LTS release. Qt 4 is no
>> longer maintained and does not support newer macOS versions, Windows 10
>> or retina displays. Supporting Qt 4 and 5 together is not only causing
>> code complexity, but also straining our testing resources.
>> If there are strong reasons to continue supporting Qt 4 beyond the
>> upcoming ParaView 5.4 release, please make us aware before June 30,
>> 2017. One can always use older versions of ParaView, if required.
>> Utkarsh 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170607/9f9d10da/attachment.html>

More information about the ParaView mailing list