Re: [Development] Preparing Qt 5.0.2 release
Merge from stable to release branch is now done. Changes that are intended to get in for Qt 5.0.2 need to be pushed into release branch. Now that the merge has done, doesn't this in effect mean that stable is now in reality Qt 5.1.0 based as dev will be merged to stable on 15th March? If that is the case, then shouldn't this be made clearer somewhere so it is pointed out that there is no plan for a Qt 5.0.3 release currently? Andy ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Preparing Qt 5.0.2 release
On Fri, Feb 22, 2013 at 12:36:07PM +, Shaw Andy wrote: Now that the merge has done, doesn't this in effect mean that stable is now in reality Qt 5.1.0 based as dev will be merged to stable on 15th March? this may very well happen, yes. it's still a good idea to push fixes to stable: a) you never know and b) distributors may pick them up even if we never make another release of the branch. conversely, this means that stable is still utterly taboo for features. If that is the case, then shouldn't this be made clearer somewhere so it is pointed out that there is no plan for a Qt 5.0.3 release currently? i think that would be moderately counter-productive in the light of the above paragraph. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Preparing Qt 5.0.2 release
On sexta-feira, 22 de fevereiro de 2013 15.43.57, Oswald Buddenhagen wrote: On Fri, Feb 22, 2013 at 12:36:07PM +, Shaw Andy wrote: Now that the merge has done, doesn't this in effect mean that stable is now in reality Qt 5.1.0 based as dev will be merged to stable on 15th March? this may very well happen, yes. it's still a good idea to push fixes to stable: a) you never know and b) distributors may pick them up even if we never make another release of the branch. conversely, this means that stable is still utterly taboo for features. Indeed, there's still time to do a 5.0.3 if we wanted to. Here's a good question: should we tag/branch the stable branch just before the dev merge? Otherwise finding those commits later (think one year later) might be difficult. But this is the sign I was waiting for to switch my main development branch from stable to dev. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Preparing Qt 5.0.2 release
-Original Message- From: Iikka Eklund Sent: 12. helmikuuta 2013 12:47 To: releas...@qt-project.org Subject: [Releasing] Preparing Qt 5.0.2 release Hi, Making of Qt 5.0.2 patch release has started: - Plan is to move into 'release' branch 18th February. So there is roughly 6 days left to get your fixes into 'stable' - After 18th February any changes that are required to get in for 5.0.2 need to be pushed into 'release' branch. Release team will then decide if the change will be taken in (P0, P1) - First 5.0.2 offline installers for testing will become available into: releases.qt-project.org/digia/5.0.2/ - Expected release time for 5.0.2 is in March - New reference installer is planned to be provided as well: Win8/msvc2012 64bit -- Br, Mr. Iikka Eklund Senior software engineer Email: iikka.ekl...@digia.com Visit us at: www.digia.com or qt.digia.com -- PRIVACY AND CONFIDENTIALITY NOTICE This message and any attachments are intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error, please contact the sender immediately and delete the message and any attachments accompanying it. Digia Plc does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message. -- ___ Releasing mailing list releas...@qt-project.org http://lists.qt-project.org/mailman/listinfo/releasing ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
