From jani.heikkinen at qt.io  Thu Mar  1 12:10:01 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Thu, 1 Mar 2018 11:10:01 +0000
Subject: [Releasing] Qt 5.11 beta1 released
In-Reply-To: <HE1PR02MB135537BE3144EF88A0F009749DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>
References: <HE1PR02MB135537BE3144EF88A0F009749DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB135595309EA06168F8BAAD5F9DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi!

We have released Qt 5.11 beta1 today, see http://blog.qt.io/blog/2018/03/01/qt-5-11-beta-released/

You can find Qt 5.11 beta1 under 'Preview' node from Online installer. Please take a tour & start testing Qt 5.11 now. As earlier we will release new beta releases regularly until we are ready for final Qt 5.11 release. It is really important to recognize all blockers for the final release as soon as possible so please make sure all release blockers can be found from RC blocker list (https://bugreports.qt.io/issues/?filter=19209).

br
Jani


From jani.heikkinen at qt.io  Thu Mar  1 14:07:12 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Thu, 1 Mar 2018 13:07:12 +0000
Subject: [Releasing] HEADS-UP: Branching from '5.9' to '5.9.5' started
Message-ID: <HE1PR02MB135509CF48E2EACBF329528B9DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi!

We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to '5.9.5' will happen at the beginning of week 11 (most probably Monday 12.3.2018).

Please start using '5.9.5' for new changes (cherry-picks from 5.11) targeted to Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!

We are targeting to release Qt 5.9.5 during March.

br,
Jani


From jani.heikkinen at qt.io  Tue Mar 13 16:29:59 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 13 Mar 2018 15:29:59 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 13.3.2018
Message-ID: <HE1PR02MB13550039323C086B2038C9519DD20@HE1PR02MB1355.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 13th March 2018

Qt 5.11:
- Beta 1 released ~ two weeks ago
- Beta2 content in place & packages available. If RTA indicates packages are good enough beta2 will be released later this week

Qt 5.9.5:
- Branching from '5.9' to '5.9.5' ongoing
   * target was to finalize branching at the beginning of this week but qt5.git integration has been failing in '5.9'. 
   * It just succeed so we will do final downmerge tomorrow.
 - Target is to get release out during March
   * Release blocker list here: https://bugreports.qt.io/issues/?filter=19230
- Release team will create initial changes files for Qt 5.9.5 immediately after branching is finalized 

Next meeting Tue 20.3.2018 16:00 CET

br
Jani Heikkinen
Release Manager

irc log below

[17:00:12] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping 
[17:00:29] <fregl> hi
[17:01:06] <akseli> jaheikki3: pong
[17:01:40] <jaheikki3> Time to start qt release team meeting
[17:01:45] <jaheikki3> On agenda today:
[17:01:50] <jaheikki3> Qt 5.11 status
[17:01:56] <jaheikki3> Qt 5.9.5 status
[17:02:07] <jaheikki3> Any additional item to the agenda?
[17:03:53] <jaheikki3> Lets start from 5.11 status:
[17:04:03] <thiago> jaheikki3: pong
[17:04:18] <jaheikki3> beta1 released ~ two weeks ago
[17:04:29] <jaheikki3> beta2 content in place & packages created
[17:04:34] <jaheikki3> RTA ongoing
[17:04:50] <jaheikki3> If all seems to be OK we will release beta2 later this week
[17:06:31] <thiago> is the API review done?
[17:06:38] <jaheikki3> thiago: ongoing
[17:06:55] <frkleint> Has the enum argument been settled?
[17:07:15] <jaheikki3> frkleint: ?
[17:07:31] <frkleint> other than that, it was ok, wasn't it (give or take qdoc things)
[17:07:54] <thiago> frkleint: I don't think we've had the argument
[17:07:58] <thiago> frkleint: post to the ML
[17:08:00] <frkleint> jaheikki3: during   API review , there was some argument
[17:08:09] <frkleint> me?
[17:08:19] <frkleint> it was between you and peppe, mostly?
[17:08:43] <jaheikki3> frkleint: I have missed that one...
[17:08:51] <thiago> right, peppe did
[17:08:59] <thiago> there's a question whether we should use enum class instead of plain enums
[17:09:27] <frkleint> right , or have the enum name in each value
[17:09:38] <frkleint> as settled in the current guide lines
[17:09:45] <frkleint> anyways
[17:10:10] <jaheikki3> Yeah, there is still time to finalize that before RC
[17:10:40] <frkleint> yup unless it is used all over the place in dependent modules ;-) 
[17:11:32] <jaheikki3> true :D 
[17:11:41] <jaheikki3>  I think that was all about Qt 5.11 at this time
[17:11:52] <jaheikki3> Then Qt 5.9.5 status:
[17:11:52] <frkleint> what does the blocker list look like?
[17:11:57] <frkleint> size() > 5 ?
[17:12:21] <jaheikki3> Yeah, 13 atm, see https://bugreports.qt.io/issues/?filter=19209
[17:12:27] <frkleint> uh
[17:12:37] <jaheikki3> That was for 5.11 RC, 
[17:12:39] <jaheikki3> :D
[17:13:25] <jaheikki3> For 5.9.5 there isn't that many, only 7 open. See https://bugreports.qt.io/issues/?filter=19230
[17:13:36] <carewolf> not on the blocker list are the security patches frmo chrome 64 and 65, but we are almost done with them
[17:13:59] <carewolf> no wait it is there, at least 64 :D
[17:14:17] <jaheikki3> carewolf: Yeah, it is there
[17:14:46] <jaheikki3> And great to hear that it is almost done. I was planning to check statuses tomorrow
[17:15:01] <jaheikki3> Branching from 5.9 -> 5.9.5 still ongoing
[17:15:31] <jaheikki3> we were waiting to get qt5.git integration through in '5.9' before finalizing it
[17:15:49] <frkleint> with some "surprises"
[17:16:11] <jaheikki3> And it just succeed & Ossi promised to do final downmerge tomorrow
[17:16:19] <jaheikki3> frkleint: What do you mean?
[17:16:38] <frkleint> the qt5.git failures in gesturemanager ,etc
[17:16:44] <frkleint> which no one had touched in years ;-) 
[17:16:48] <frkleint> anywyas
[17:17:18] <jaheikki3> yeah, there has been some weird problems lately but anyway; it finally integrates
[17:17:56] <jaheikki3> We will do initial change files for Qt 5.9.5 immediately after final downmerge
[17:18:26] <jaheikki3> & target is still to get release out during march
[17:18:42] <frkleint> did we discuss dropping change files for LTS, since they should be empty?
[17:19:08] <jaheikki3> ? I don't recall that kind of discussion
[17:19:23] <frkleint> hm, maybe we just discussed it here
[17:19:32] <frkleint> ok, but maybe requires broader consent
[17:19:38] <jaheikki3> frkleint: true
[17:19:46] <thiago> why should they be empty?
[17:19:54] <thiago> if we didn't have changes, we wouldn't release at all
[17:20:00] <frkleint> there shouldn;t be any changelog-worthy  changes
[17:20:09] <thiago> there should be change entries
[17:20:11] <frkleint> like behavioural changes,./ featyures
[17:20:17] <frkleint> security maybe
[17:20:21] <thiago> mostly bugfixes, etc., but we should be listing those
[17:21:29] <frkleint> hm at least for 5.6 I think there is not much point in having change files any more...
[17:23:12] <jaheikki3> Ok, I think this was all at this time. Let's have new meeting tue 20.3 as planned
[17:23:21] <frkleint> ok
[17:23:27] <jaheikki3> Thanks for your participation
[17:23:30] <jaheikki3> Bye!
[17:23:39] <frkleint> bye


From jani.heikkinen at qt.io  Wed Mar 14 08:03:50 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 14 Mar 2018 07:03:50 +0000
Subject: [Releasing] Qt API review process (was: Re: Qt 5.11 Alpha released)
In-Reply-To: <AM4PR02MB3249374A01572D28FC81C8A887CE0@AM4PR02MB3249.eurprd02.prod.outlook.com>
References: <HE1PR02MB13558E81E1BB83D0AF3655EC9DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<HE1PR02MB1355CA6BD5467CAA1D31D0189DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<AM4PR02MB3249374A01572D28FC81C8A887CE0@AM4PR02MB3249.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB1355561204669993E6382C069DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi all,

We have API review ongoing for Qt 5.11. For me our process for that is a bit unclear; At which point we can say the review is really done? There are comments in the reviews but then pretty much nothing... At some there is -1, few +1 but that's it. I think we should clarify the process so that we can more easily see the status there. That's why I propose following:

1) API review for the module is ready when there is '+2'  (from Module/Chief Maintainer)
2) During the review reviewer must add 'Code Review -1/-2' if there is something which should be corrected before we can agree API review to be ready. And vice versa: if API seems to be OK +1 should be added to indicate API is reviewed.
3) Reviewer needs to create a bug report about the findings. That makes it easier to follow up & we can add needed ones in the release blocker list.
   * These bug reports should be added in review's comment field as well. And if one is something which really needs to be fixed before release reviewer should add the issue in release blocker list.
4) API review for module needs to be updated in gerrit until it gets '+2'. After that no more updates. That way we can link the approved review in releasing wiki for the evidence :D

br,
Jani 
________________________________________
From: Edward Welbourne
Sent: Wednesday, February 21, 2018 6:43 PM
To: development at qt-project.org
Cc: releasing at qt-project.org; Jani Heikkinen
Subject: Re: Qt 5.11 Alpha released

Jani Heikkinen (20 February 2018 11:14)
> We have release Qt 5.11 Alpha today, see http://blog.qt.io/blog/2018/02/20/qt-5-11-alpha-released/

and so, of course, we also have 5.11 API reviews, vs v5.10.1:

https://codereview.qt-project.org/221039 qtbase
https://codereview.qt-project.org/221040 qtdeclarative
https://codereview.qt-project.org/221041 qtmultimedia
https://codereview.qt-project.org/221042 qttools
https://codereview.qt-project.org/221043 qtxmlpatterns
https://codereview.qt-project.org/221044 qtlocation
https://codereview.qt-project.org/221045 qtconnectivity
https://codereview.qt-project.org/221046 qtwayland
https://codereview.qt-project.org/221047 qt3d
https://codereview.qt-project.org/221048 qtserialbus
https://codereview.qt-project.org/221049 qtandroidextras
https://codereview.qt-project.org/221050 qtwebengine
https://codereview.qt-project.org/221051 qtcharts
https://codereview.qt-project.org/221052 qtgamepad
https://codereview.qt-project.org/221053 qtremoteobjects

See the review comments for guidance, consult actual source for
definitive views of code - note that these reviews are generated by a
script that filters out changes deemed boring; it has learned, on this
iteration, to not waste your time with s/Q_DECL_FINAL/final/ or
s/Q_QDOC/Q_CLANG_QDOC/ changes; and to ignore the addition of
Q_DECL_COLD_FUNCTION.  Speaking of which, please accept my apologies
for not delivering this two days ago - I got distracted by trying to
revamp the script to be a bit smarter about detecting boring changes
that add a line, among other things.

        Eddy.


From jani.heikkinen at qt.io  Wed Mar 14 12:01:32 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 14 Mar 2018 11:01:32 +0000
Subject: [Releasing] HEADS-UP: Branching from '5.9' to '5.9.5' ready
In-Reply-To: <HE1PR02MB135509CF48E2EACBF329528B9DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>
References: <HE1PR02MB135509CF48E2EACBF329528B9DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB13555E07ACF6E08937A7DA459DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi!

Branching from '5.9' to '5.9.5' is now competed. From now on '5.9' if for Qt 5.9.6 and all changes targeted to Qt 5.9.5 release must be done in '5.9.5'. And as usual no any 'nice-to-haves' in '5.9.5' anymore!

We are targeting to get Qt 5.9.5 out as soon as possible (during March) so please make sure all release blockers are visible in blocker list (https://bugreports.qt.io/issues/?filter=19230) and all release blockers are fixed immediately.

br,
Jani
________________________________________
From: Development <development-bounces+jani.heikkinen=qt.io at qt-project.org> on behalf of Jani Heikkinen <jani.heikkinen at qt.io>
Sent: Thursday, March 1, 2018 3:07 PM
To: development at qt-project.org
Cc: releasing at qt-project.org
Subject: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' started

Hi!

We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to '5.9.5' will happen at the beginning of week 11 (most probably Monday 12.3.2018).

Please start using '5.9.5' for new changes (cherry-picks from 5.11) targeted to Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!

We are targeting to release Qt 5.9.5 during March.

br,
Jani
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


From jani.heikkinen at qt.io  Thu Mar 15 05:56:12 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Thu, 15 Mar 2018 04:56:12 +0000
Subject: [Releasing] [Development] HEADS-UP: Branching from '5.9' to
 '5.9.5' ready
In-Reply-To: <CAA1VrPpSbY1AWs_w3CuQQ+YwOyze5G0yf70NzMwTkwZASXNWsw@mail.gmail.com>
References: <HE1PR02MB135509CF48E2EACBF329528B9DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>
	<HE1PR02MB13555E07ACF6E08937A7DA459DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>
	<CAA1VrPpSbY1AWs_w3CuQQ+YwOyze5G0yf70NzMwTkwZASXNWsw@mail.gmail.com>
Message-ID: <HE1PR02MB1355C81301E9DADE47D039BE9DD00@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi!

Is there a bug report about the issue? If this is nothing new I think we can wait Qt 5.9.6 for that fix

br,
Jani

> -----Original Message-----
> From: Alexandr Akulich <akulichalexander at gmail.com>
> Sent: keskiviikko 14. maaliskuuta 2018 16.21
> To: Jani Heikkinen <jani.heikkinen at qt.io>
> Cc: development at qt-project.org; releasing at qt-project.org
> Subject: Re: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready
> 
> Hi Jani,
> 
> Can we please get in a compilation fix for qreal configured as float?
> There is a very small yet critical issue with qMax in QFusionStyle.
> 
> I submitted the fix [1] for 5.11 and it is approved, but I agreed to also fix the
> same line coding style issue before staging the change.
> 
> I will submit the final patch for 5.11 in two hours (as soon as I'll get back to my
> ssh keys) and will submit cherry-pick for 5.9 immediately after the original patch
> staging.
> 
> [1] https://codereview.qt-project.org/#/c/223101/
> 
> On Wed, Mar 14, 2018 at 2:01 PM, Jani Heikkinen <jani.heikkinen at qt.io> wrote:
> > Hi!
> >
> > Branching from '5.9' to '5.9.5' is now competed. From now on '5.9' if for Qt
> 5.9.6 and all changes targeted to Qt 5.9.5 release must be done in '5.9.5'. And as
> usual no any 'nice-to-haves' in '5.9.5' anymore!
> >
> > We are targeting to get Qt 5.9.5 out as soon as possible (during March) so
> please make sure all release blockers are visible in blocker list
> (https://bugreports.qt.io/issues/?filter=19230) and all release blockers are fixed
> immediately.
> >
> > br,
> > Jani
> > ________________________________________
> > From: Development
> > <development-bounces+jani.heikkinen=qt.io at qt-project.org> on behalf of
> > Jani Heikkinen <jani.heikkinen at qt.io>
> > Sent: Thursday, March 1, 2018 3:07 PM
> > To: development at qt-project.org
> > Cc: releasing at qt-project.org
> > Subject: [Development] HEADS-UP: Branching from '5.9' to '5.9.5'
> > started
> >
> > Hi!
> >
> > We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to '5.9.5'
> will happen at the beginning of week 11 (most probably Monday 12.3.2018).
> >
> > Please start using '5.9.5' for new changes (cherry-picks from 5.11) targeted to
> Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!
> >
> > We are targeting to release Qt 5.9.5 during March.
> >
> > br,
> > Jani
> > _______________________________________________
> > Development mailing list
> > Development at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> > _______________________________________________
> > Development mailing list
> > Development at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development

From jani.heikkinen at qt.io  Thu Mar 15 09:22:20 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Thu, 15 Mar 2018 08:22:20 +0000
Subject: [Releasing] [Development] HEADS-UP: Branching from '5.9' to
 '5.9.5' ready
In-Reply-To: <CAA1VrPq=fNUyZL0K_H8s7kLm02suynnqR_i4NkXUe6er2FYhEA@mail.gmail.com>
References: <HE1PR02MB135509CF48E2EACBF329528B9DC60@HE1PR02MB1355.eurprd02.prod.outlook.com>
	<HE1PR02MB13555E07ACF6E08937A7DA459DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>
	<CAA1VrPpSbY1AWs_w3CuQQ+YwOyze5G0yf70NzMwTkwZASXNWsw@mail.gmail.com>
	<HE1PR02MB1355C81301E9DADE47D039BE9DD00@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<CAA1VrPq=fNUyZL0K_H8s7kLm02suynnqR_i4NkXUe6er2FYhEA@mail.gmail.com>
Message-ID: <HE1PR02MB135533390C8E5023C0B43A5C9DD00@HE1PR02MB1355.eurprd02.prod.outlook.com>

Ok,
Then it would be good to get this fixed in Qt 5.9.5. Please remember to do the cherry-pick in '5.9.5', not in '5.9'

br,
Jani
________________________________________
From: Alexandr Akulich <akulichalexander at gmail.com>
Sent: Thursday, March 15, 2018 10:03 AM
To: Jani Heikkinen
Cc: development at qt-project.org; releasing at qt-project.org
Subject: Re: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready

I thought that it is an old issue (since 5.9 to 5.11) but in fact, it
is a regression since change [1] in landed to 5.9.5.
I staged the fix for 5.11 ten minutes ago and I will submit the change
for 5.9 in two hours.

[1] https://codereview.qt-project.org/#/c/212208/

On Thu, Mar 15, 2018 at 7:56 AM, Jani Heikkinen <jani.heikkinen at qt.io> wrote:
> Hi!
>
> Is there a bug report about the issue? If this is nothing new I think we can wait Qt 5.9.6 for that fix
>
> br,
> Jani
>
>> -----Original Message-----
>> From: Alexandr Akulich <akulichalexander at gmail.com>
>> Sent: keskiviikko 14. maaliskuuta 2018 16.21
>> To: Jani Heikkinen <jani.heikkinen at qt.io>
>> Cc: development at qt-project.org; releasing at qt-project.org
>> Subject: Re: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready
>>
>> Hi Jani,
>>
>> Can we please get in a compilation fix for qreal configured as float?
>> There is a very small yet critical issue with qMax in QFusionStyle.
>>
>> I submitted the fix [1] for 5.11 and it is approved, but I agreed to also fix the
>> same line coding style issue before staging the change.
>>
>> I will submit the final patch for 5.11 in two hours (as soon as I'll get back to my
>> ssh keys) and will submit cherry-pick for 5.9 immediately after the original patch
>> staging.
>>
>> [1] https://codereview.qt-project.org/#/c/223101/
>>
>> On Wed, Mar 14, 2018 at 2:01 PM, Jani Heikkinen <jani.heikkinen at qt.io> wrote:
>> > Hi!
>> >
>> > Branching from '5.9' to '5.9.5' is now competed. From now on '5.9' if for Qt
>> 5.9.6 and all changes targeted to Qt 5.9.5 release must be done in '5.9.5'. And as
>> usual no any 'nice-to-haves' in '5.9.5' anymore!
>> >
>> > We are targeting to get Qt 5.9.5 out as soon as possible (during March) so
>> please make sure all release blockers are visible in blocker list
>> (https://bugreports.qt.io/issues/?filter=19230) and all release blockers are fixed
>> immediately.
>> >
>> > br,
>> > Jani
>> > ________________________________________
>> > From: Development
>> > <development-bounces+jani.heikkinen=qt.io at qt-project.org> on behalf of
>> > Jani Heikkinen <jani.heikkinen at qt.io>
>> > Sent: Thursday, March 1, 2018 3:07 PM
>> > To: development at qt-project.org
>> > Cc: releasing at qt-project.org
>> > Subject: [Development] HEADS-UP: Branching from '5.9' to '5.9.5'
>> > started
>> >
>> > Hi!
>> >
>> > We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to '5.9.5'
>> will happen at the beginning of week 11 (most probably Monday 12.3.2018).
>> >
>> > Please start using '5.9.5' for new changes (cherry-picks from 5.11) targeted to
>> Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!
>> >
>> > We are targeting to release Qt 5.9.5 during March.
>> >
>> > br,
>> > Jani
>> > _______________________________________________
>> > Development mailing list
>> > Development at qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/development
>> > _______________________________________________
>> > Development mailing list
>> > Development at qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/development


From jani.heikkinen at qt.io  Thu Mar 15 13:54:32 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Thu, 15 Mar 2018 12:54:32 +0000
Subject: [Releasing] Qt 5.11 beta2 released
In-Reply-To: <HE1PR02MB1355B3881F09FB9C76FBAEEE9DD00@HE1PR02MB1355.eurprd02.prod.outlook.com>
References: <HE1PR02MB1355B3881F09FB9C76FBAEEE9DD00@HE1PR02MB1355.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB135536C864CB59B95521CF429DD00@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi all,

We have published Qt 5.11 beta2 today. As earlier you can get it via online installer. Delta to beta1 attached.

Please test the packages now & report all findings to Jira. Also make sure all release blockers can be found from release blocker list (https://bugreports.qt.io/issues/?filter=19209). It is really time to test the packages now; even the plan is to release at the end of May we will do it earlier if possible.

br,
Jani
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: delta_qt511-beta1-qt511.beta2.txt
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20180315/242109ef/attachment.txt>

From edward.welbourne at qt.io  Fri Mar 16 11:41:34 2018
From: edward.welbourne at qt.io (Edward Welbourne)
Date: Fri, 16 Mar 2018 10:41:34 +0000
Subject: [Releasing] Qt API review process (was: Re: Qt 5.11 Alpha
 released)
In-Reply-To: <HE1PR02MB1355561204669993E6382C069DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>
References: <HE1PR02MB13558E81E1BB83D0AF3655EC9DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<HE1PR02MB1355CA6BD5467CAA1D31D0189DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<AM4PR02MB3249374A01572D28FC81C8A887CE0@AM4PR02MB3249.eurprd02.prod.outlook.com>,
	<HE1PR02MB1355561204669993E6382C069DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>
Message-ID: <AM5PR0202MB262507002BD8453E3ED301C087D70@AM5PR0202MB2625.eurprd02.prod.outlook.com>

Jani Heikkinen (14 March 2018 08:03) wrote:
> We have API review ongoing for Qt 5.11.
> For me our process for that is a bit unclear;

That sounds like something we should aim to turn into a QUIP,
once discussion here has produced something close enough to
a consensus to be worth documenting.

Folks out there with opinions on the process Jani proposed,
please speak up !

[...]
> 4) API review for module needs to be updated in gerrit until it gets
> '+2'.  After that no more updates.

If there are updates to the code that change API, I shall feel
duty-bound to update the API review; of course, those shouldn't happen
except in responses to the API review, but we do things asynchronously,
so it's possible some change that's been on its way in for some time
lands after my last update to the API review before it gets its +2;
particularly if there was an objection to something in the API review,
that someone set about addressing but despite which the maintainer
decided to +2 (e.g. it might be in new API that's not yet subject to
[BS]C promises; but its perpetrator sees the wisdom of the objection so
addresses it).

The QUIP shall, at least, need to document how we deal with such cases,
if they arise,

	Eddy.


From jani.heikkinen at qt.io  Mon Mar 19 06:42:59 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Mon, 19 Mar 2018 05:42:59 +0000
Subject: [Releasing] HEADS UP : Qt 5.11 soft string freeze
Message-ID: <HE1PR02MB13557DF93A2B9B1F07DD0E1C9DD40@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi all,

First beta releases from Qt 5.11 are already out so it is time to start keeping translatable strings as it is. Let's have official string freeze Mon 26th March 2018. 

br,
Jani

From Kai.Koehne at qt.io  Tue Mar 20 09:34:35 2018
From: Kai.Koehne at qt.io (Kai Koehne)
Date: Tue, 20 Mar 2018 08:34:35 +0000
Subject: [Releasing] Qt API review process (was: Re: Qt 5.11 Alpha
 released)
In-Reply-To: <HE1PR02MB1355561204669993E6382C069DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>
References: <HE1PR02MB13558E81E1BB83D0AF3655EC9DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<HE1PR02MB1355CA6BD5467CAA1D31D0189DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<AM4PR02MB3249374A01572D28FC81C8A887CE0@AM4PR02MB3249.eurprd02.prod.outlook.com>
	<HE1PR02MB1355561204669993E6382C069DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>
Message-ID: <HE1PR0202MB25713E29100015758918561998AB0@HE1PR0202MB2571.eurprd02.prod.outlook.com>

(comment below)

> -----Original Message-----
> From: Development [mailto:development-bounces+kai.koehne=qt.io at qt-
> project.org] On Behalf Of Jani Heikkinen
> Subject: [Development] Qt API review process (was: Re: Qt 5.11 Alpha
> released)
> 
> Hi all,
> 
> We have API review ongoing for Qt 5.11. For me our process for that is a bit
> unclear; At which point we can say the review is really done? There are
> comments in the reviews but then pretty much nothing... At some there is -1,
> few +1 but that's it. I think we should clarify the process so that we can more
> easily see the status there. That's why I propose following:
> 
> 1) API review for the module is ready when there is '+2'  (from Module/Chief
> Maintainer)
> 2) During the review reviewer must add 'Code Review -1/-2' if there is
> something which should be corrected before we can agree API review to be
> ready. And vice versa: if API seems to be OK +1 should be added to indicate API
> is reviewed.
> 3) Reviewer needs to create a bug report about the findings. That makes it
> easier to follow up & we can add needed ones in the release blocker list.
>    * These bug reports should be added in review's comment field as well. And if
> one is something which really needs to be fixed before release reviewer should
> add the issue in release blocker list.
> 4) API review for module needs to be updated in gerrit until it gets '+2'. After
> that no more updates. That way we can link the approved review in releasing
> wiki for the evidence :D

I would rather create a task in JIRA for the review itself, with priority 1 
and appropriate fixVersion. Any subsequent findings could be made subtasks of
this task. 

This automatically makes the API review part of the blockers list, and makes sure
everyone understands that this needs to be done before a release.

Regards

Kai



From edward.welbourne at qt.io  Tue Mar 20 11:19:08 2018
From: edward.welbourne at qt.io (Edward Welbourne)
Date: Tue, 20 Mar 2018 10:19:08 +0000
Subject: [Releasing] Qt API review process (was: Re: Qt 5.11 Alpha
 released)
In-Reply-To: <HE1PR0202MB25713E29100015758918561998AB0@HE1PR0202MB2571.eurprd02.prod.outlook.com>
References: <HE1PR02MB13558E81E1BB83D0AF3655EC9DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<HE1PR02MB1355CA6BD5467CAA1D31D0189DCF0@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<AM4PR02MB3249374A01572D28FC81C8A887CE0@AM4PR02MB3249.eurprd02.prod.outlook.com>
	<HE1PR02MB1355561204669993E6382C069DD10@HE1PR02MB1355.eurprd02.prod.outlook.com>,
	<HE1PR0202MB25713E29100015758918561998AB0@HE1PR0202MB2571.eurprd02.prod.outlook.com>
Message-ID: <AM5PR0202MB262560512B65D71C91485C4E87AB0@AM5PR0202MB2625.eurprd02.prod.outlook.com>

Kai Koehne (20 March 2018 09:34)
> I would rather create a task in JIRA for the review itself, with priority 1
> and appropriate fixVersion. Any subsequent findings could be made subtasks of
> this task.
>
> This automatically makes the API review part of the blockers list, and makes sure
> everyone understands that this needs to be done before a release.

Good idea - I'll add a --task[-number] option to the api-review-gen
script; if you open that bug and tell me its ID, I'll exercise this
option when next I run the script (hopefully later today) to pick up all
the changes folk have made in response to reviews so far,

How will the fact that I abandon reviews once they have +2 (or we ship a
release) bear on that task's view of them ?

	Eddy.


From jani.heikkinen at qt.io  Tue Mar 27 08:01:03 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 27 Mar 2018 06:01:03 +0000
Subject: [Releasing] HEADS UP : Qt 5.11 string freeze
In-Reply-To: <HE1PR02MB13557DF93A2B9B1F07DD0E1C9DD40@HE1PR02MB1355.eurprd02.prod.outlook.com>
References: <HE1PR02MB13557DF93A2B9B1F07DD0E1C9DD40@HE1PR02MB1355.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB1355415EF9084E986ADB366A9DAC0@HE1PR02MB1355.eurprd02.prod.outlook.com>

Hi,

As informed a week ago string freeze for Qt 5.11 is now in effect. So please, no changes to translatable strings from this point, unless approved by the documentation team.

br,
Jani
________________________________________
From: Development <development-bounces+jani.heikkinen=qt.io at qt-project.org> on behalf of Jani Heikkinen <jani.heikkinen at qt.io>
Sent: Monday, March 19, 2018 7:42 AM
To: localization at qt-project.org
Cc: development at qt-project.org; releasing at qt-project.org
Subject: [Development] HEADS UP : Qt 5.11 soft string freeze

Hi all,

First beta releases from Qt 5.11 are already out so it is time to start keeping translatable strings as it is. Let's have official string freeze Mon 26th March 2018.

br,
Jani
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


From jani.heikkinen at qt.io  Tue Mar 27 16:23:03 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 27 Mar 2018 14:23:03 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 27.3.2018
Message-ID: <HE1PR02MB1355FA1BE9FCAF8E2E0AB8DE9DAC0@HE1PR02MB1355.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 27th March 2018

Qt 5.9.5:
- 3 blockers open, see https://bugreports.qt.io/issues/?filter=19230
   * Only one is missing a fix (QTBUG-61415)
      ** Le for a fix is this week 
--> We can't get release out during March as planned
   * New target is to do the release immediately after the Easter

Qt 5.11:
- String freeze in effect
- Beta3 preparations ongoing
   * waiting for Qt5.git integration (https://codereview.qt-project.org/#/c/224019/). When succeed then packaging, RTA smoke and beta3 out if all OK
- Pretty good situation with release blockers, see https://bugreports.qt.io/issues/?filter=19209
   * 15 open but  ~half of those has already a fix in place

Next meeting Tue 3.4.2018 16:00 CET
   
br,
Jani

irc log below:
[17:01:44] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping 
[17:01:51] <akseli> jaheikki3: pong
[17:02:15] <jaheikki3> Time to start qt release team meeting
[17:02:21] <jaheikki3> On agenda today:
[17:02:27] <jaheikki3> Qt 5.9.5 status
[17:02:31] <jaheikki3> Qt 5.11 status
[17:02:41] <jaheikki3> Any additional item to the agenda?
[17:03:04] <frkleint> jaheikki3: pong
[17:04:14] <jaheikki3> Ok, Qt 5.9.5 status:
[17:04:26] <jaheikki3> 3 release blockers open, see https://bugreports.qt.io/issues/?filter=19230
[17:04:50] <jaheikki3> Only one is missing a fix (QTBUG-61415), Le for a fix: this week
[17:04:51] <qt_gerrit> jaheikki3: Potential license problem with examples/qt3d/exampleresources/assets/textures/pattern_09/* - https://bugreports.qt.io/browse/QTBUG-61415 (Open)
[17:05:16] <jaheikki3> Unfortunately that means we can't get release out before Easter
[17:05:33] <jaheikki3> New target is get it out immediately after Easter
[17:06:13] <jaheikki3> Also Qtbase changes file still waiting '+2'
[17:06:41] <jaheikki3> But that's all about 5.9.5 at this time. Any comments or questions?
[17:06:58] <thiago> jaheikki3: pong
[17:07:51] -*- thiago will not have time to review changes file until early next week
[17:07:54] <thiago> one week from now
[17:09:19] <jaheikki3> thiago: Ok, we are targeting to get release out soon after the Easter
[17:09:41] <jaheikki3> Ok, then Qt 5.11 status:
[17:09:55] <jaheikki3> String freeze in effect
[17:10:01] <jaheikki3> Beta3 preparations ongoing
[17:11:00] <jaheikki3> We will create beta3 packages after Qt5.git integration (https://codereview.qt-project.org/#/c/224019/) succeed.  then  RTA smoke and beta3 out if all OK
[17:11:01] <qt_gerrit> jaheikki3: [qt/qt5/5.11] Update submodules on '5.11' in qt5 from Qt Submodule Update Bot - https://codereview.qt-project.org/224019 (INTEGRATING)
[17:12:02] <jaheikki3> Let's see if we can get beta3 out before Easter. It is still possible but if not then we will release it immediately after Easter
[17:12:30] <jaheikki3> Qt 5.11 RC blocker list here: https://bugreports.qt.io/issues/?filter=19209
[17:12:54] <jaheikki3> Pretty good situation with release blockers: 15 open but ~half of those has already a fix in place
[17:13:25] -*- jaheikki3 is hoping all known blockers are really viusible there
[17:13:57] <jaheikki3> I think that's all about 5.11 status at the moment. Any comments or questions?
[17:17:01] <jaheikki3> Ok, it was all at this time. Let's have new meeting Tue 3.4 as planned.
[17:17:18] <jaheikki3> Thanks for your participation, bye!
[17:18:06] <frkleint> bye