Tuukka Turunen wrote:
> Of those 2a and 2b sound the best to me, however we should be able to make
> 5.10.2 at least in case needed on top of 5.10.1 with a critical security
> fix (or similar).
You are talking about needing maybe one security fix. I can tell you that it
is practically certain tha
Hi,
Of those 2a and 2b sound the best to me, however we should be able to make
5.10.2 at least in case needed on top of 5.10.1 with a critical security fix
(or similar).
I think keeping 5.9 open a bit longer has benefit due to it being an LTS. It
adds a bit merge effort, but should be managea
On Thu, Feb 01, 2018 at 02:35:58PM +0100, Tuukka Turunen wrote:
> So based on this Qt 5.9 should be in cherry pick mode next week. With
> previous wording it should have been in cherry pick mode from 2.9.2017
> onwards, which was way too soon (hence the change to QUIP5).
>
right.
> What about Qt
Hi,
To be clear, the updated QUIP5
(http://code.qt.io/cgit/meta/quips.git/tree/quip-0005.rst) says:
"*strict*
This period starts when the one after next stable branch is created (for the
5.9 LTS, the one after next is 5.11). Submitting to the LTS branch directly
is then no longer p
01.02.2018, 14:19, "Oswald Buddenhagen" :
> On Tue, Jan 30, 2018 at 09:38:29PM +, Tuukka Turunen wrote:
>> The item that has received comments both in favor and against is what
>> to do with 5.10 now. I think that instead of closing 5.10, we could
>> move it to cherry pick mode, just like
On Tue, Jan 30, 2018 at 09:38:29PM +, Tuukka Turunen wrote:
> The item that has received comments both in favor and against is what
> to do with 5.10 now. I think that instead of closing 5.10, we could
> move it to cherry pick mode, just like Qt 5.9 is. That allows putting
> the necessary fixes
-1 from me. How is this any less work than merging, especially with git
rerere?
Can we please keep 5.9 open until we have at least released 5.11.0?
I really don't want to get into a situation where we have bug fixes on
5.9 and 5.11 but not 5.10.2 say.
Once 5.10 is properly closed then fine,
> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Tuukka Turunen
> Sent: tiistai 30. tammikuuta 2018 23.38
> To: Konrad Rosenbaum ; development@qt-project.org
> Subject: Re: [Development] Qt branches & proposal how to c
Hello,
after a discussion on the wayland maillinglist this bug was created:
https://bugs.freedesktop.org/show_bug.cgi?id=104867
Maybe it is of some interest for Qt too.
Regards,
Hannes
___
Development mailing list
Development@qt-project.org
http://list
