Re: [Development] Qt 5.8 branching & Feature Freeze

[Oswald Buddenhagen]

On Mon, Jun 27, 2016 at 10:29:34AM +, Edward Welbourne wrote:
> this would bring them to light early and one at a time, which tends to
> make them easier to resolve !
> 
given that mutiple conflicts in the same place are pretty rare, i'll
challenge that claim.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Edward Welbourne]

Jędrzej Nowacki said (inter alia):
>Technically waiting for merges is not necessary. Coin is able
> to test arbitrary refs from gerrit, I encourage you to not wait for
> the system, but just make bunch of changes and tests the expected
> combination, before it gets merged from stable branches. You can also
> request a feature branch for testing if you want to work that way. In
> the same time I agree, the merge cycle is too slow, it is just
> annoying. In my opinion the system should automatically create merge
> patches after each successful integration and warn if it was not
> possible because of conflicts. It seems also that I'm extremist in
> that area, but one merge per day seems to be a reasonable compromise.

+1 for regular automated up-merging as often as possible.  We'd still
need to manually resolve conflicts, but this would bring them to light
early and one at a time, which tends to make them easier to resolve !

Eddy.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Jani Heikkinen]

Hi all,


It seems there isn't that much objections to proposed schedule. Tony's points 
are valid but after discussion with several persons we agree it isn't necessary 
to postpone feature freeze because of missing platforms/versions from CI. So 
let's proceed with proposed schedule to be able to release Qt 5.8.0 still 
during this year:


- Branching from 'dev' to '5.8' starts 2.8.2016

- Qt 5.8 feature freeze 9.8.2016


Please make sure all new features are really in 'dev' well before actual 
feature freeze date (and fulfilling the FF criteria: 
https://wiki.qt.io/Qt5_feature_freeze). Also make sure all new submodules (also 
technology preview ones) are in qt5.git (.gitmodules) early enough. By default 
all modules missing at FF date will be out from Qt 5.8 release (Lars can give 
an exception by request but we should really avoid that).


Please start updating Qt 5.8.0 new features page here: 
https://wiki.qt.io/New_Features_in_Qt_5.8 .



br,

Jani
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Jędrzej Nowacki]

On Thursday 16 of June 2016 06:57:50 Tony Sarajärvi wrote:
> Hi,
> 
> Our aim was to get new platforms in immediately after the previous platforms
> branched away from dev branch. Meaning, when 5.7 branch was created and it
> branched away from dev branch, all new platforms aiming for 5.8 should have
> been put into dev branch. However, in practice it didn't quite go as
> expected. Not to blame anyone, but all focus was to get 5.6.x and 5.7.x
> out. Meaning, dev branch was left broken for several months. The individual
> submodules did pass in the CI, but the last time Qt5 has passed is 4 months
> ago.
> 
> To tackle this we agreed that we can start inserting new platforms submodule
> by submodule, but right after that we froze Coin setup so that we don't
> break 5.7.x by accident. And by having several branches, with alphas,
> betas, release candidates and releases themselves we have a lot of these
> freezes, which means that the time window, where we can put in any new
> platform, is very short. And if the submodule in dev don't happen to have
> everything merged from earlier branches and finally work, an insertion
> won't happen.
> 
> This is why we've not been successful in bringing openSUSE 42.1, Ubuntu
> 16.04, RHEL 7.2, OS X 10.11 in into dev branch albeit trying to do that for
> months.
> 
> So back to this day. Currently we can't put anything new in, since Coin
> setup is frozen. We have holidays coming up and we have a skeleton crew
> working the entire summer. Right as we get back to work, we have 5.8 branch
> coming up and feature freeze right after that. When did you expect us to
> push in these new platforms? According to process, we shouldn't put them
> into 5.8 after FF. If we bend this rule (as we usually do), we might get
> them in there as people focus on fixing issues there, or the same thing
> happens as happened with 5.7: the new platforms simply never passed
> autotests so that they could be brought in (we actually did try to get them
> into 5.7 early on, but not lately due to release being too close).
> 
> Ok...perhaps I should propose something. Let's postpone branching 5.8. As
> much as I like the motto of Blizzard Entertainment "done when it's done" ,
> I've found that people like time schedules as well. Alas, I have to suggest
> that we postpone it as much as possible. I think that we can fix the things
> we want to fix in 5.8 in dev branch as well. When we get a more mature dev
> branch that actually works, we can generate the alpha package for 5.8 much
> faster after the branch, as 5.8 already worked right of the bat (because
> dev worked). Also, we'll get a working dev branch as well simultaneously.
> 
> Also, we've noticed that often when people fix problems found in autotests,
> being it a bug in the autotest itself or as it actually more often is, a
> problem in Qt sources themselves, people push the fix to the most mature
> branch available. In this case, when we report that we can't get openSUSE
> 42.1 in, because this and that fails, the fix is pushed into 5.6 as it
> already appears there but haven't been found or studied before. Then we
> have to sit down and in worst case wait for a 5.6.1 -> 5.6 -> 5.7 -> dev
> merge. With all the general flakiness in the system, that usually takes a
> fortnight at least.
> 
> So by fixing dev, we can skip doing merges from 5.8 -> dev when we
> eventually find the problems for these new platforms.
> 
> With regards,
> -Tony
> 
> PS: The list with new platforms actually increases yet with OS X...ehm macOS
> Sierra (10.12) beta coming up, tvOS etc...

Hi,
Ok, the process here is suboptimal, let' me extract certain aspects 
that 
can be handled separately.

Qt5 dev is in disastrous state, nobody managed to pass CI from 
February. 
Having  Qt5 working is crucial because otherwise, how can we distinguish 
between regressions in a new platform and just standard regressions. As you 
wrote Qt5 dev was not prioritized, because of two concurrent releases. That 
has to change, because state of Qt5 dev directly affects a next release. We 
have to accept the fact that we are doing 3-4 releases in parallel: LTS, 
current (potentially could be two of them) and next. Down-prioritizing one is 
just moving problems in time, which doesn't work with time based releases.

We were not updating Coin in any way for last 2 weeks. That is an 
exceptional situation. I strongly believe that in future it will not be 
requested and we will limit such freeze just to test configurations not the 
whole system. 

New platforms are features, they affect releases in exactly the same 
way as 
code. So feature freeze should apply to them too and it is great that it was 
enforced. Now, porting to new platform also should be done as a feature 
development. No need to wait for branching.

Technically waiting for merges is not necessary. Coin is able to test 
arbitrary refs from gerrit, I encourage you to not wait for the system, but 

Re: [Development] Qt 5.8 branching & Feature Freeze

[Tuukka Turunen]

Hi,

Another approach for tvOS and other items that we can not have in by Qt 5.8 FF 
(or shortly after), would be to add these into dev after 5.8 has branched and 
have these in good time for Qt 5.9. Although we are constantly improving, we 
are not yet where we want in the CI flexibility and Qt is a complex platform. 
There are many important new features coming with Qt 5.8 and I would not want 
to risk getting these out in time by adding a lot of new platforms to CI at a 
late phase.

Yours,

 Tuukka

From: Tony Sarajärvi
Sent: torstaina 16. kesäkuuta 2016 9.58
To: Maurice Kalinowski <maurice.kalinow...@qt.io>; Tuukka Turunen 
<tuukka.turu...@qt.io>; Jake Petroules <jake.petrou...@qt.io>; Mike Krus 
<mike.k...@kdab.com>
Cc: development@qt-project.org
Subject: RE: [Development] Qt 5.8 branching & Feature Freeze

Hi,

Our aim was to get new platforms in immediately after the previous platforms 
branched away from dev branch. Meaning, when 5.7 branch was created and it 
branched away from dev branch, all new platforms aiming for 5.8 should have 
been put into dev branch. However, in practice it didn't quite go as expected. 
Not to blame anyone, but all focus was to get 5.6.x and 5.7.x out. Meaning, dev 
branch was left broken for several months. The individual submodules did pass 
in the CI, but the last time Qt5 has passed is 4 months ago.

To tackle this we agreed that we can start inserting new platforms submodule by 
submodule, but right after that we froze Coin setup so that we don't break 
5.7.x by accident. And by having several branches, with alphas, betas, release 
candidates and releases themselves we have a lot of these freezes, which means 
that the time window, where we can put in any new platform, is very short. And 
if the submodule in dev don't happen to have everything merged from earlier 
branches and finally work, an insertion won't happen.

This is why we've not been successful in bringing openSUSE 42.1, Ubuntu 16.04, 
RHEL 7.2, OS X 10.11 in into dev branch albeit trying to do that for months.

So back to this day. Currently we can't put anything new in, since Coin setup 
is frozen. We have holidays coming up and we have a skeleton crew working the 
entire summer. Right as we get back to work, we have 5.8 branch coming up and 
feature freeze right after that. When did you expect us to push in these new 
platforms? According to process, we shouldn't put them into 5.8 after FF. If we 
bend this rule (as we usually do), we might get them in there as people focus 
on fixing issues there, or the same thing happens as happened with 5.7: the new 
platforms simply never passed autotests so that they could be brought in (we 
actually did try to get them into 5.7 early on, but not lately due to release 
being too close).

Ok...perhaps I should propose something. Let's postpone branching 5.8. As much 
as I like the motto of Blizzard Entertainment "done when it's done" , I've 
found that people like time schedules as well. Alas, I have to suggest that we 
postpone it as much as possible. I think that we can fix the things we want to 
fix in 5.8 in dev branch as well. When we get a more mature dev branch that 
actually works, we can generate the alpha package for 5.8 much faster after the 
branch, as 5.8 already worked right of the bat (because dev worked). Also, 
we'll get a working dev branch as well simultaneously.

Also, we've noticed that often when people fix problems found in autotests, 
being it a bug in the autotest itself or as it actually more often is, a 
problem in Qt sources themselves, people push the fix to the most mature branch 
available. In this case, when we report that we can't get openSUSE 42.1 in, 
because this and that fails, the fix is pushed into 5.6 as it already appears 
there but haven't been found or studied before. Then we have to sit down and in 
worst case wait for a 5.6.1 -> 5.6 -> 5.7 -> dev merge. With all the general 
flakiness in the system, that usually takes a fortnight at least.

So by fixing dev, we can skip doing merges from 5.8 -> dev when we eventually 
find the problems for these new platforms.

With regards,
-Tony

PS: The list with new platforms actually increases yet with OS X...ehm macOS 
Sierra (10.12) beta coming up, tvOS etc...

From: Development 
[mailto:development-bounces+tony.sarajarvi=qt...@qt-project.org] On Behalf Of 
Maurice Kalinowski
Sent: 15. kesäkuuta 2016 16:51
To: Tuukka Turunen <tuukka.turu...@qt.io<mailto:tuukka.turu...@qt.io>>; Jake 
Petroules <jake.petrou...@qt.io<mailto:jake.petrou...@qt.io>>; Mike Krus 
<mike.k...@kdab.com<mailto:mike.k...@kdab.com>>
Cc: development@qt-project.org<mailto:development@qt-project.org>
Subject: Re: [Development] Qt 5.8 branching & Feature Freeze

Hi,

Another option might be to do it the same way like we do for UWP currently due 
to limited resources on the CI syst

Re: [Development] Qt 5.8 branching & Feature Freeze - Qt Speech TTS

[Philippe]

+1

Philippe

On Thu, 16 Jun 2016 12:22:02 +0200
Frederik Gladhorn <frederik.gladh...@qt.io> wrote:

> On onsdag 15. juni 2016 07.15.16 CEST Tuukka Turunen wrote:
> > Hi,
> > 
> > I would also like to have all new modules (if any) of Qt 5.8 as well as
> > implement all (feasible) platform and compiler versions well before the
> > feature freeze. Is it possible to agree that latest by 1.8. all these are
> > completed? Preferably earlier, if possible.
> > 
> 
> I'd like to finally get Qt Speech in as Tech Preview in Qt 5.8. Only the text 
> to speech parts, unless someone does major work on future proofing the speech 
> recognition parts before the release.
> 
> I'll start adding it to qt5.git - it already got green light for Qt 5.6 and 
> got pushed further and further out since it had some compile issues at the 
> time and everything got too tight schedule wise.
> Please let me know if there's some reason not to add it.
> 
> Please also look through the API for inconsistencies and general blunders. 
> It's a really small API, so shouldn't take much time. Maybe there's also 
> stuff 
> missing - I know there was a request to serialize and deserialize the current 
> voice selection, that might for example be nice to add if anyone wants to 
> work 
> on a fun small module ;-)
> 
> Cheers,
> Frederik
> 
> 
> > Yours,
> > 
> >  Tuukka
> > 
> > From: Development
> > [mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On Behalf
> > Of Jani Heikkinen Sent: keskiviikkona 15. kesäkuuta 2016 9.27
> > To: development@qt-project.org
> > Subject: [Development] Qt 5.8 branching & Feature Freeze
> > 
> > 
> > Hi all,
> > 
> > 
> > 
> > It was agreed in yesterday's release team meeting to propose following
> > schedule for Qt 5.8 branching and Feature Freeze:
> > 
> > 
> > 
> > - Start branching '5.8' from 'dev': 2.8.2016
> > 
> > - Feature Freeze (and finalize branching): 9.8.2016
> > 
> > 
> > 
> > With that schedule we should be able to release Qt 5.8.0 before Christmas.
> > Delaying these would cause Qt 5.8.0 release to be delayed to the beginning
> > of next year. Any objections?
> > 
> > 
> > 
> > br,
> > 
> > Jani
> > 
> > 
> > 
> > 
> > Jani Heikkinen
> > Release Manager
> > 
> > The Qt Company
> > Elektroniikkatie 13
> > 90590 Oulu Finland
> > jani.heikki...@qt.io<mailto:jani.heikki...@qt.io>
> > +358 50 4873735
> > http://qt.io<http://qt.io/>
> > 
> > 
> > 
> > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rg
> > b_400x141.png]<http://qt.io/>
> > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] > p://www.facebook.com/Qt>
> > 
> > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] > //www.twitter.com/qtproject>
> > 
> > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] > s://www.linkedin.com/company/the-qt-company/>
> > 
> > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] > tps://plus.google.com/104580575722059274792>
> > 
> > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] > ://www.youtube.com/QtStudios>
> 
> 
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze - Qt Speech TTS

[Tuukka Turunen]

> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Frederik
> Gladhorn
> Sent: torstaina 16. kesäkuuta 2016 13.22
> To: development@qt-project.org
> Subject: Re: [Development] Qt 5.8 branching & Feature Freeze - Qt Speech
> TTS
> 
> On onsdag 15. juni 2016 07.15.16 CEST Tuukka Turunen wrote:
> > Hi,
> >
> > I would also like to have all new modules (if any) of Qt 5.8 as well
> > as implement all (feasible) platform and compiler versions well before
> > the feature freeze. Is it possible to agree that latest by 1.8. all
> > these are completed? Preferably earlier, if possible.
> >
> 
> I'd like to finally get Qt Speech in as Tech Preview in Qt 5.8. Only the text 
> to
> speech parts, unless someone does major work on future proofing the
> speech recognition parts before the release.
> 

There is some implementation for the speech recognition API as well for using a 
local recognizer. It would be nice to get that also polished, but if it is not 
feasible yet at least we can have the text to speech parts. But in case anyone 
is interested in the speech recognition as well, there is already a start to 
look into and polish.

Yours,

Tuukka

> I'll start adding it to qt5.git - it already got green light for Qt 5.6 and 
> got
> pushed further and further out since it had some compile issues at the time
> and everything got too tight schedule wise.
> Please let me know if there's some reason not to add it.
> 
> Please also look through the API for inconsistencies and general blunders.
> It's a really small API, so shouldn't take much time. Maybe there's also stuff
> missing - I know there was a request to serialize and deserialize the current
> voice selection, that might for example be nice to add if anyone wants to
> work on a fun small module ;-)
> 
> Cheers,
> Frederik
> 
> 
> > Yours,
> >
> >  Tuukka
> >
> > From: Development
> > [mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On
> > Behalf Of Jani Heikkinen Sent: keskiviikkona 15. kesäkuuta 2016 9.27
> > To: development@qt-project.org
> > Subject: [Development] Qt 5.8 branching & Feature Freeze
> >
> >
> > Hi all,
> >
> >
> >
> > It was agreed in yesterday's release team meeting to propose following
> > schedule for Qt 5.8 branching and Feature Freeze:
> >
> >
> >
> > - Start branching '5.8' from 'dev': 2.8.2016
> >
> > - Feature Freeze (and finalize branching): 9.8.2016
> >
> >
> >
> > With that schedule we should be able to release Qt 5.8.0 before Christmas.
> > Delaying these would cause Qt 5.8.0 release to be delayed to the
> > beginning of next year. Any objections?
> >
> >
> >
> > br,
> >
> > Jani
> >
> >
> >
> >
> > Jani Heikkinen
> > Release Manager
> >
> > The Qt Company
> > Elektroniikkatie 13
> > 90590 Oulu Finland
> > jani.heikki...@qt.io<mailto:jani.heikki...@qt.io>
> > +358 50 4873735
> > http://qt.io<http://qt.io/>
> >
> >
> >
> > [http://s3-eu-west-1.amazonaws.com/qt-
> files/logos/qt_logo_with_text_gr
> > een_rg
> > b_400x141.png]<http://qt.io/>
> > [http://s3-eu-west-1.amazonaws.com/qt-
> files/logos/SoMe/qt_facebook.png
> > ] > p://www.facebook.com/Qt>
> >
> > [http://s3-eu-west-1.amazonaws.com/qt-
> files/logos/SoMe/qt_twitter.png] > //www.twitter.com/qtproject>
> >
> > [http://s3-eu-west-1.amazonaws.com/qt-
> files/logos/SoMe/qt_linkedin.png
> > ]
> >
> > [http://s3-eu-west-1.amazonaws.com/qt-
> files/logos/SoMe/qt_googleplus.p
> > ng]
> >
> > [http://s3-eu-west-1.amazonaws.com/qt-
> files/logos/SoMe/qt_youtube.png]
> >  > ://www.youtube.com/QtStudios>
> 
> 
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze - Qt Speech TTS

[Frederik Gladhorn]

On onsdag 15. juni 2016 07.15.16 CEST Tuukka Turunen wrote:
> Hi,
> 
> I would also like to have all new modules (if any) of Qt 5.8 as well as
> implement all (feasible) platform and compiler versions well before the
> feature freeze. Is it possible to agree that latest by 1.8. all these are
> completed? Preferably earlier, if possible.
> 

I'd like to finally get Qt Speech in as Tech Preview in Qt 5.8. Only the text 
to speech parts, unless someone does major work on future proofing the speech 
recognition parts before the release.

I'll start adding it to qt5.git - it already got green light for Qt 5.6 and 
got pushed further and further out since it had some compile issues at the 
time and everything got too tight schedule wise.
Please let me know if there's some reason not to add it.

Please also look through the API for inconsistencies and general blunders. 
It's a really small API, so shouldn't take much time. Maybe there's also stuff 
missing - I know there was a request to serialize and deserialize the current 
voice selection, that might for example be nice to add if anyone wants to work 
on a fun small module ;-)

Cheers,
Frederik


> Yours,
> 
>  Tuukka
> 
> From: Development
> [mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On Behalf
> Of Jani Heikkinen Sent: keskiviikkona 15. kesäkuuta 2016 9.27
> To: development@qt-project.org
> Subject: [Development] Qt 5.8 branching & Feature Freeze
> 
> 
> Hi all,
> 
> 
> 
> It was agreed in yesterday's release team meeting to propose following
> schedule for Qt 5.8 branching and Feature Freeze:
> 
> 
> 
> - Start branching '5.8' from 'dev': 2.8.2016
> 
> - Feature Freeze (and finalize branching): 9.8.2016
> 
> 
> 
> With that schedule we should be able to release Qt 5.8.0 before Christmas.
> Delaying these would cause Qt 5.8.0 release to be delayed to the beginning
> of next year. Any objections?
> 
> 
> 
> br,
> 
> Jani
> 
> 
> 
> 
> Jani Heikkinen
> Release Manager
> 
> The Qt Company
> Elektroniikkatie 13
> 90590 Oulu Finland
> jani.heikki...@qt.io<mailto:jani.heikki...@qt.io>
> +358 50 4873735
> http://qt.io<http://qt.io/>
> 
> 
> 
> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rg
> b_400x141.png]<http://qt.io/>
> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] p://www.facebook.com/Qt>
> 
> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] //www.twitter.com/qtproject>
> 
> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] s://www.linkedin.com/company/the-qt-company/>
> 
> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] tps://plus.google.com/104580575722059274792>
> 
> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] ://www.youtube.com/QtStudios>


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Liang Qi]

for these new platforms.
>
>
>
> With regards,
>
> -Tony
>
>
>
> PS: The list with new platforms actually increases yet with OS X…ehm macOS
> Sierra (10.12) beta coming up, tvOS etc…
>
>
>
> *From:* Development [mailto:development-bounces+tony.sarajarvi=
> qt...@qt-project.org] *On Behalf Of *Maurice Kalinowski
> *Sent:* 15. kesäkuuta 2016 16:51
> *To:* Tuukka Turunen <tuukka.turu...@qt.io>; Jake Petroules <
> jake.petrou...@qt.io>; Mike Krus <mike.k...@kdab.com>
> *Cc:* development@qt-project.org
>
> *Subject:* Re: [Development] Qt 5.8 branching & Feature Freeze
>
>
>
> Hi,
>
>
>
> Another option might be to do it the same way like we do for UWP currently
> due to limited resources on the CI system. There we have at least a compile
> check every time qt5.git integration is supposed to happen.
>
>
>
> This is bare minimum, but at least guarantees that compilation will work
> for release. The rest still needs to be manually tested and/or is covered
> by Windows 8.1 WinRT test coverage (which isn’t too high either).
>
>
>
> BR,
>
> Maurice
>
>
>
> *Von:* Development [mailto:development-bounces+maurice.kalinowski=
> qt...@qt-project.org] *Im Auftrag von *Tuukka Turunen
> *Gesendet:* Wednesday, June 15, 2016 11:59 AM
> *An:* Jake Petroules <jake.petrou...@qt.io>; Mike Krus <mike.k...@kdab.com
> >
> *Cc:* development@qt-project.org
> *Betreff:* Re: [Development] Qt 5.8 branching & Feature Freeze
>
>
>
>
>
> Hi,
>
>
>
> Perhaps we could do without CI for tvOS for Qt 5.8 and fix issues when
> breakages happen. We are still quite stretched with the CI and adding tvOS
> increases the load of the CI and also risk of breakages for everyone. That
> of course is the role of CI, but since tvOS is not at the moment so
> critical, perhaps it is better to monitor it and fix afterwards when
> breakages do occur.
>
>
>
> Yours,
>
>
>
>  Tuukka
>
>
>
>
>
> *From:* Jake Petroules
> *Sent:* keskiviikkona 15. kesäkuuta 2016 12.01
> *To:* Mike Krus <mike.k...@kdab.com>
> *Cc:* Tuukka Turunen <tuukka.turu...@qt.io>; development@qt-project.org
> *Subject:* Re: [Development] Qt 5.8 branching & Feature Freeze
>
>
>
> +1. I requested this earlier as well.
>
>
>
> On Jun 15, 2016, at 1:51 AM, Mike Krus <mike.k...@kdab.com> wrote:
>
>
>
> Hi
>
>
>
> would it be possible to have CI for tvOS in time for this too?
>
>
>
>
>
> Cheers,
>
>
>
> Mike
>
>
>
>
>
> On 15 Jun 2016, at 08:15, Tuukka Turunen <tuukka.turu...@qt.io> wrote:
>
>
>
>
>
> Hi,
>
>
>
> I would also like to have all new modules (if any) of Qt 5.8 as well as
> implement all (feasible) platform and compiler versions well before the
> feature freeze. Is it possible to agree that latest by 1.8. all these are
> completed? Preferably earlier, if possible.
>
>
>
> Yours,
>
>
>
>  Tuukka
>
>
>
> *From:* Development [
> mailto:development-bounces+tuukka.turunen=qt...@qt-project.org
> <development-bounces+tuukka.turunen=qt...@qt-project.org>] *On Behalf Of *Jani
> Heikkinen
> *Sent:* keskiviikkona 15. kesäkuuta 2016 9.27
> *To:* development@qt-project.org
> *Subject:* [Development] Qt 5.8 branching & Feature Freeze
>
>
>
> Hi all,
>
>
>
> It was agreed in yesterday's release team meeting to propose following
> schedule for Qt 5.8 branching and Feature Freeze:
>
>
>
> - Start branching '5.8' from 'dev': 2.8.2016
>
> - Feature Freeze (and finalize branching): 9.8.2016
>
>
>
> With that schedule we should be able to release Qt 5.8.0 before Christmas.
> Delaying these would cause Qt 5.8.0 release to be delayed to the beginning
> of next year. Any objections?
>
>
>
> br,
>
> Jani
>
>
>
>
>
> Jani Heikkinen
> Release Manager
>
> The Qt Company
> Elektroniikkatie 13
> 90590 Oulu Finland
> jani.heikki...@qt.io
> +358 50 4873735
> http://qt.io
>
>
> [image: Image removed by sender.] <http://qt.io/>
>
> [image: Image removed by sender.] <http://www.facebook.com/Qt>
>
> [image: Image removed by sender.] <http://www.twitter.com/qtproject>
>
> [image: Image removed by sender.]
> <https://www.linkedin.com/company/the-qt-company/>
>
> [image: Image removed by sender.]
> <https://plus.google.com/104580575722059274792>
>
> [image: Image removed by sender.] <https://www.youtube.com/QtStudios>
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
>
> --
> Mike Krus | mike.k...@kdab.com | Senior Software Engineer
> KDAB (UK) Ltd., a KDAB Group company
> Tel: UK +44-1625-809908   Mobile: +44 7833 491941
> KDAB - The Qt Experts
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
>
> --
> Jake Petroules - jake.petrou...@qt.io
> Consulting Services Engineer - The Qt Company
>
> Qbs build system evangelist - qbs.io
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Tony Sarajärvi]

Hi,

Our aim was to get new platforms in immediately after the previous platforms 
branched away from dev branch. Meaning, when 5.7 branch was created and it 
branched away from dev branch, all new platforms aiming for 5.8 should have 
been put into dev branch. However, in practice it didn't quite go as expected. 
Not to blame anyone, but all focus was to get 5.6.x and 5.7.x out. Meaning, dev 
branch was left broken for several months. The individual submodules did pass 
in the CI, but the last time Qt5 has passed is 4 months ago.

To tackle this we agreed that we can start inserting new platforms submodule by 
submodule, but right after that we froze Coin setup so that we don't break 
5.7.x by accident. And by having several branches, with alphas, betas, release 
candidates and releases themselves we have a lot of these freezes, which means 
that the time window, where we can put in any new platform, is very short. And 
if the submodule in dev don't happen to have everything merged from earlier 
branches and finally work, an insertion won't happen.

This is why we've not been successful in bringing openSUSE 42.1, Ubuntu 16.04, 
RHEL 7.2, OS X 10.11 in into dev branch albeit trying to do that for months.

So back to this day. Currently we can't put anything new in, since Coin setup 
is frozen. We have holidays coming up and we have a skeleton crew working the 
entire summer. Right as we get back to work, we have 5.8 branch coming up and 
feature freeze right after that. When did you expect us to push in these new 
platforms? According to process, we shouldn't put them into 5.8 after FF. If we 
bend this rule (as we usually do), we might get them in there as people focus 
on fixing issues there, or the same thing happens as happened with 5.7: the new 
platforms simply never passed autotests so that they could be brought in (we 
actually did try to get them into 5.7 early on, but not lately due to release 
being too close).

Ok...perhaps I should propose something. Let's postpone branching 5.8. As much 
as I like the motto of Blizzard Entertainment "done when it's done" , I've 
found that people like time schedules as well. Alas, I have to suggest that we 
postpone it as much as possible. I think that we can fix the things we want to 
fix in 5.8 in dev branch as well. When we get a more mature dev branch that 
actually works, we can generate the alpha package for 5.8 much faster after the 
branch, as 5.8 already worked right of the bat (because dev worked). Also, 
we'll get a working dev branch as well simultaneously.

Also, we've noticed that often when people fix problems found in autotests, 
being it a bug in the autotest itself or as it actually more often is, a 
problem in Qt sources themselves, people push the fix to the most mature branch 
available. In this case, when we report that we can't get openSUSE 42.1 in, 
because this and that fails, the fix is pushed into 5.6 as it already appears 
there but haven't been found or studied before. Then we have to sit down and in 
worst case wait for a 5.6.1 -> 5.6 -> 5.7 -> dev merge. With all the general 
flakiness in the system, that usually takes a fortnight at least.

So by fixing dev, we can skip doing merges from 5.8 -> dev when we eventually 
find the problems for these new platforms.

With regards,
-Tony

PS: The list with new platforms actually increases yet with OS X...ehm macOS 
Sierra (10.12) beta coming up, tvOS etc...

From: Development 
[mailto:development-bounces+tony.sarajarvi=qt...@qt-project.org] On Behalf Of 
Maurice Kalinowski
Sent: 15. kesäkuuta 2016 16:51
To: Tuukka Turunen <tuukka.turu...@qt.io>; Jake Petroules 
<jake.petrou...@qt.io>; Mike Krus <mike.k...@kdab.com>
Cc: development@qt-project.org
Subject: Re: [Development] Qt 5.8 branching & Feature Freeze

Hi,

Another option might be to do it the same way like we do for UWP currently due 
to limited resources on the CI system. There we have at least a compile check 
every time qt5.git integration is supposed to happen.

This is bare minimum, but at least guarantees that compilation will work for 
release. The rest still needs to be manually tested and/or is covered by 
Windows 8.1 WinRT test coverage (which isn't too high either).

BR,
Maurice

Von: Development 
[mailto:development-bounces+maurice.kalinowski=qt...@qt-project.org] Im Auftrag 
von Tuukka Turunen
Gesendet: Wednesday, June 15, 2016 11:59 AM
An: Jake Petroules <jake.petrou...@qt.io>; Mike Krus <mike.k...@kdab.com>
Cc: development@qt-project.org
Betreff: Re: [Development] Qt 5.8 branching & Feature Freeze


Hi,

Perhaps we could do without CI for tvOS for Qt 5.8 and fix issues when 
breakages happen. We are still quite stretched with the CI and adding tvOS 
increases the load of the CI and also risk of breakages for everyone. That of 
course is the role of CI, but since tvOS is not at the moment so critical, 
perhaps it is better to m

Re: [Development] Qt 5.8 branching & Feature Freeze

[Maurice Kalinowski]

Hi,

Another option might be to do it the same way like we do for UWP currently due 
to limited resources on the CI system. There we have at least a compile check 
every time qt5.git integration is supposed to happen.

This is bare minimum, but at least guarantees that compilation will work for 
release. The rest still needs to be manually tested and/or is covered by 
Windows 8.1 WinRT test coverage (which isn't too high either).

BR,
Maurice

Von: Development 
[mailto:development-bounces+maurice.kalinowski=qt...@qt-project.org] Im Auftrag 
von Tuukka Turunen
Gesendet: Wednesday, June 15, 2016 11:59 AM
An: Jake Petroules <jake.petrou...@qt.io>; Mike Krus <mike.k...@kdab.com>
Cc: development@qt-project.org
Betreff: Re: [Development] Qt 5.8 branching & Feature Freeze


Hi,

Perhaps we could do without CI for tvOS for Qt 5.8 and fix issues when 
breakages happen. We are still quite stretched with the CI and adding tvOS 
increases the load of the CI and also risk of breakages for everyone. That of 
course is the role of CI, but since tvOS is not at the moment so critical, 
perhaps it is better to monitor it and fix afterwards when breakages do occur.

Yours,

 Tuukka


From: Jake Petroules
Sent: keskiviikkona 15. kesäkuuta 2016 12.01
To: Mike Krus <mike.k...@kdab.com<mailto:mike.k...@kdab.com>>
Cc: Tuukka Turunen <tuukka.turu...@qt.io<mailto:tuukka.turu...@qt.io>>; 
development@qt-project.org<mailto:development@qt-project.org>
Subject: Re: [Development] Qt 5.8 branching & Feature Freeze

+1. I requested this earlier as well.

On Jun 15, 2016, at 1:51 AM, Mike Krus 
<mike.k...@kdab.com<mailto:mike.k...@kdab.com>> wrote:

Hi

would it be possible to have CI for tvOS in time for this too?


Cheers,

Mike


On 15 Jun 2016, at 08:15, Tuukka Turunen 
<tuukka.turu...@qt.io<mailto:tuukka.turu...@qt.io>> wrote:


Hi,

I would also like to have all new modules (if any) of Qt 5.8 as well as 
implement all (feasible) platform and compiler versions well before the feature 
freeze. Is it possible to agree that latest by 1.8. all these are completed? 
Preferably earlier, if possible.

Yours,

 Tuukka

From: Development 
[mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of 
Jani Heikkinen
Sent: keskiviikkona 15. kesäkuuta 2016 9.27
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] Qt 5.8 branching & Feature Freeze

Hi all,

It was agreed in yesterday's release team meeting to propose following schedule 
for Qt 5.8 branching and Feature Freeze:

- Start branching '5.8' from 'dev': 2.8.2016
- Feature Freeze (and finalize branching): 9.8.2016

With that schedule we should be able to release Qt 5.8.0 before Christmas. 
Delaying these would cause Qt 5.8.0 release to be delayed to the beginning of 
next year. Any objections?

br,
Jani


Jani Heikkinen
Release Manager

The Qt Company
Elektroniikkatie 13
90590 Oulu Finland
jani.heikki...@qt.io<mailto:jani.heikki...@qt.io>
+358 50 4873735
http://qt.io<http://qt.io/>



[http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]<http://qt.io/>
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]<http://www.facebook.com/Qt>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png]<http://www.twitter.com/qtproject>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png]<https://www.linkedin.com/company/the-qt-company/>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png]<https://plus.google.com/104580575722059274792>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png]<https://www.youtube.com/QtStudios>


___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

--
Mike Krus | mike.k...@kdab.com<mailto:mike.k...@kdab.com> | Senior Software 
Engineer
KDAB (UK) Ltd., a KDAB Group company
Tel: UK +44-1625-809908   Mobile: +44 7833 491941
KDAB - The Qt Experts

___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

--
Jake Petroules - jake.petrou...@qt.io<mailto:jake.petrou...@qt.io>
Consulting Services Engineer - The Qt Company
Qbs build system evangelist - qbs.io<http://qbs.io>

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Tuukka Turunen]

Hi,

Perhaps we could do without CI for tvOS for Qt 5.8 and fix issues when 
breakages happen. We are still quite stretched with the CI and adding tvOS 
increases the load of the CI and also risk of breakages for everyone. That of 
course is the role of CI, but since tvOS is not at the moment so critical, 
perhaps it is better to monitor it and fix afterwards when breakages do occur.

Yours,

 Tuukka


From: Jake Petroules
Sent: keskiviikkona 15. kesäkuuta 2016 12.01
To: Mike Krus <mike.k...@kdab.com>
Cc: Tuukka Turunen <tuukka.turu...@qt.io>; development@qt-project.org
Subject: Re: [Development] Qt 5.8 branching & Feature Freeze

+1. I requested this earlier as well.

On Jun 15, 2016, at 1:51 AM, Mike Krus 
<mike.k...@kdab.com<mailto:mike.k...@kdab.com>> wrote:

Hi

would it be possible to have CI for tvOS in time for this too?


Cheers,

Mike


On 15 Jun 2016, at 08:15, Tuukka Turunen 
<tuukka.turu...@qt.io<mailto:tuukka.turu...@qt.io>> wrote:


Hi,

I would also like to have all new modules (if any) of Qt 5.8 as well as 
implement all (feasible) platform and compiler versions well before the feature 
freeze. Is it possible to agree that latest by 1.8. all these are completed? 
Preferably earlier, if possible.

Yours,

 Tuukka

From: Development 
[mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of 
Jani Heikkinen
Sent: keskiviikkona 15. kesäkuuta 2016 9.27
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] Qt 5.8 branching & Feature Freeze

Hi all,

It was agreed in yesterday's release team meeting to propose following schedule 
for Qt 5.8 branching and Feature Freeze:

- Start branching '5.8' from 'dev': 2.8.2016
- Feature Freeze (and finalize branching): 9.8.2016

With that schedule we should be able to release Qt 5.8.0 before Christmas. 
Delaying these would cause Qt 5.8.0 release to be delayed to the beginning of 
next year. Any objections?

br,
Jani


Jani Heikkinen
Release Manager

The Qt Company
Elektroniikkatie 13
90590 Oulu Finland
jani.heikki...@qt.io<mailto:jani.heikki...@qt.io>
+358 50 4873735
http://qt.io<http://qt.io/>



[http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]<http://qt.io/>
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]<http://www.facebook.com/Qt>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png]<http://www.twitter.com/qtproject>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png]<https://www.linkedin.com/company/the-qt-company/>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png]<https://plus.google.com/104580575722059274792>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png]<https://www.youtube.com/QtStudios>


___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

--
Mike Krus | mike.k...@kdab.com<mailto:mike.k...@kdab.com> | Senior Software 
Engineer
KDAB (UK) Ltd., a KDAB Group company
Tel: UK +44-1625-809908   Mobile: +44 7833 491941
KDAB - The Qt Experts

___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

--
Jake Petroules - jake.petrou...@qt.io<mailto:jake.petrou...@qt.io>
Consulting Services Engineer - The Qt Company
Qbs build system evangelist - qbs.io<http://qbs.io>

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Jake Petroules]

+1. I requested this earlier as well.

On Jun 15, 2016, at 1:51 AM, Mike Krus 
<mike.k...@kdab.com<mailto:mike.k...@kdab.com>> wrote:

Hi

would it be possible to have CI for tvOS in time for this too?


Cheers,

Mike


On 15 Jun 2016, at 08:15, Tuukka Turunen 
<tuukka.turu...@qt.io<mailto:tuukka.turu...@qt.io>> wrote:


Hi,

I would also like to have all new modules (if any) of Qt 5.8 as well as 
implement all (feasible) platform and compiler versions well before the feature 
freeze. Is it possible to agree that latest by 1.8. all these are completed? 
Preferably earlier, if possible.

Yours,

 Tuukka

From: Development 
[mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of 
Jani Heikkinen
Sent: keskiviikkona 15. kesäkuuta 2016 9.27
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] Qt 5.8 branching & Feature Freeze

Hi all,

It was agreed in yesterday's release team meeting to propose following schedule 
for Qt 5.8 branching and Feature Freeze:

- Start branching '5.8' from 'dev': 2.8.2016
- Feature Freeze (and finalize branching): 9.8.2016

With that schedule we should be able to release Qt 5.8.0 before Christmas. 
Delaying these would cause Qt 5.8.0 release to be delayed to the beginning of 
next year. Any objections?

br,
Jani


Jani Heikkinen
Release Manager

The Qt Company
Elektroniikkatie 13
90590 Oulu Finland
jani.heikki...@qt.io<mailto:jani.heikki...@qt.io>
+358 50 4873735
http://qt.io<http://qt.io/>



[http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]<http://qt.io/>
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]<http://www.facebook.com/Qt>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png]<http://www.twitter.com/qtproject>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png]<https://www.linkedin.com/company/the-qt-company/>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png]<https://plus.google.com/104580575722059274792>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png]<https://www.youtube.com/QtStudios>


___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

--
Mike Krus | mike.k...@kdab.com<mailto:mike.k...@kdab.com> | Senior Software 
Engineer
KDAB (UK) Ltd., a KDAB Group company
Tel: UK +44-1625-809908   Mobile: +44 7833 491941
KDAB - The Qt Experts

___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

--
Jake Petroules - jake.petrou...@qt.io<mailto:jake.petrou...@qt.io>
Consulting Services Engineer - The Qt Company
Qbs build system evangelist - qbs.io<http://qbs.io>

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Mike Krus]

Hi

would it be possible to have CI for tvOS in time for this too?


Cheers,

Mike


> On 15 Jun 2016, at 08:15, Tuukka Turunen <tuukka.turu...@qt.io> wrote:
> 
>  
> Hi,
>  
> I would also like to have all new modules (if any) of Qt 5.8 as well as 
> implement all (feasible) platform and compiler versions well before the 
> feature freeze. Is it possible to agree that latest by 1.8. all these are 
> completed? Preferably earlier, if possible.
>  
> Yours,
>  
>  Tuukka
>   <>
> From: Development 
> [mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of 
> Jani Heikkinen
> Sent: keskiviikkona 15. kesäkuuta 2016 9.27
> To: development@qt-project.org
> Subject: [Development] Qt 5.8 branching & Feature Freeze
>  
> Hi all,
>  
> It was agreed in yesterday's release team meeting to propose following 
> schedule for Qt 5.8 branching and Feature Freeze:
>  
> - Start branching '5.8' from 'dev': 2.8.2016
> - Feature Freeze (and finalize branching): 9.8.2016
>  
> With that schedule we should be able to release Qt 5.8.0 before Christmas. 
> Delaying these would cause Qt 5.8.0 release to be delayed to the beginning of 
> next year. Any objections?
>  
> br,
> Jani
>  
>  
> Jani Heikkinen
> Release Manager
> 
> The Qt Company
> Elektroniikkatie 13
> 90590 Oulu Finland
> jani.heikki...@qt.io <mailto:jani.heikki...@qt.io>
> +358 50 4873735
> http://qt.io <http://qt.io/>
> 
>  <http://qt.io/>
>  <http://www.facebook.com/Qt> 
>  <http://www.twitter.com/qtproject>   
>  <https://www.linkedin.com/company/the-qt-company/>   
>  <https://plus.google.com/104580575722059274792>  
>  <https://www.youtube.com/QtStudios>
>  
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

--
Mike Krus | mike.k...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a KDAB Group company
Tel: UK +44-1625-809908   Mobile: +44 7833 491941
KDAB - The Qt Experts

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.8 branching & Feature Freeze

[Tuukka Turunen]

Hi,

I would also like to have all new modules (if any) of Qt 5.8 as well as 
implement all (feasible) platform and compiler versions well before the feature 
freeze. Is it possible to agree that latest by 1.8. all these are completed? 
Preferably earlier, if possible.

Yours,

 Tuukka

From: Development 
[mailto:development-bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of 
Jani Heikkinen
Sent: keskiviikkona 15. kesäkuuta 2016 9.27
To: development@qt-project.org
Subject: [Development] Qt 5.8 branching & Feature Freeze


Hi all,



It was agreed in yesterday's release team meeting to propose following schedule 
for Qt 5.8 branching and Feature Freeze:



- Start branching '5.8' from 'dev': 2.8.2016

- Feature Freeze (and finalize branching): 9.8.2016



With that schedule we should be able to release Qt 5.8.0 before Christmas. 
Delaying these would cause Qt 5.8.0 release to be delayed to the beginning of 
next year. Any objections?



br,

Jani




Jani Heikkinen
Release Manager

The Qt Company
Elektroniikkatie 13
90590 Oulu Finland
jani.heikki...@qt.io<mailto:jani.heikki...@qt.io>
+358 50 4873735
http://qt.io<http://qt.io/>



[http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]<http://qt.io/>
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]<http://www.facebook.com/Qt>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png]<http://www.twitter.com/qtproject>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png]<https://www.linkedin.com/company/the-qt-company/>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png]<https://plus.google.com/104580575722059274792>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png]<https://www.youtube.com/QtStudios>


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.8 branching & Feature Freeze

[Jani Heikkinen]

Hi all,


It was agreed in yesterday's release team meeting to propose following schedule 
for Qt 5.8 branching and Feature Freeze:


- Start branching '5.8' from 'dev': 2.8.2016

- Feature Freeze (and finalize branching): 9.8.2016


With that schedule we should be able to release Qt 5.8.0 before Christmas. 
Delaying these would cause Qt 5.8.0 release to be delayed to the beginning of 
next year. Any objections?


br,

Jani



Jani Heikkinen
Release Manager

The Qt Company
Elektroniikkatie 13
90590 Oulu Finland
jani.heikki...@qt.io
+358 50 4873735
http://qt.io


[http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]
 [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] 
   
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] 
  
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] 
   
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] 


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development