On 24 Sep 2018, at 14:11, Danny Smit
mailto:danny.smi...@gmail.com>> wrote:
On Fri, Sep 21, 2018 at 11:11 AM Alexandru Croitor
mailto:alexandru.croi...@qt.io>> wrote:
You will probably want to read http://wiki.qt.io/Qt_Contribution_Guidelines
And specifically to your questions, bug fixes first
On Fri, Sep 21, 2018 at 11:11 AM Alexandru Croitor
wrote:
>
> You will probably want to read http://wiki.qt.io/Qt_Contribution_Guidelines
>
> And specifically to your questions, bug fixes first go to the current stable
> brach of Qt (5.11.3 in this case), and once the patches are in, they can be
Thanks both,
On Fri, Sep 21, 2018 at 10:45 PM Florian Bruhin wrote:
> According to [1], Debian stable packages Qt 5.7.1 (which is not an LTS),
> and testing/unstable both ship 5.11.1.
Yes, you are absolutely right. I got the versions mixed up.
> See [2]. The Qt 5.6 release was in March 2016, so
Hey,
On Fri, Sep 21, 2018 at 09:49:19AM +0200, Danny Smit wrote:
> I'm running into two (old) Qt bugs using the latest Debian, with still
> uses the LTS Qt 5.6.
What do you mean with "the latest Debian"?
According to [1], Debian stable packages Qt 5.7.1 (which is not an LTS),
and testing/unstabl
Hi,
Thanks for showing interest in contributing to Qt.
You will probably want to read http://wiki.qt.io/Qt_Contribution_Guidelines
And specifically to your questions, bug fixes first go to the current stable
brach of Qt (5.11.3 in this case), and once the patches are in, they can be
backported
Hi all,
I'm running into two (old) Qt bugs using the latest Debian, with still
uses the LTS Qt 5.6. Preferably I'd like to see them fixed upstream,
so that the whole world can benefit from the changes, instead of
applying patches locally. I'm willing to send pull requests of needed.
My real quest
