<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">+1 on either Qt 5.6 or 5.9 being the
minimum<br>
<br>
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?<br>
<br>
Best regards,<br>
Bruno Santos<br>
<br>
On 06-06-2017 17:44, Michael Jackson wrote:<br>
</div>
<blockquote type="cite" cite="mid:5936DBF8.7030908@bluequartz.net">+1.
<br>
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
<br>
<br>
<div class="moz-txt-sig"><br>
Utkarsh Ayachit wrote:
<br>
<blockquote type="cite" style="color: #000000;">Folks,
<br>
<br>
Continuing with dropping of support for legacy components, I
wanted to
<br>
raise the question of dropping support for Qt older than 5.6
starting
<br>
with ParaView 5.5 (planned for Nov 2017).
<br>
<br>
Qt 5.6 has been out since March 2016 and is a LTS release. Qt
4 is no
<br>
longer maintained and does not support newer macOS versions,
Windows 10
<br>
or retina displays. Supporting Qt 4 and 5 together is not only
causing
<br>
code complexity, but also straining our testing resources.
<br>
<br>
If there are strong reasons to continue supporting Qt 4 beyond
the
<br>
upcoming ParaView 5.4 release, please make us aware before
June 30,
<br>
2017. One can always use older versions of ParaView, if
required.
<br>
<br>
Utkarsh
</blockquote>
</div>
</blockquote>
<br>
<br>
</body>
</html>