[Development] Qt 4.6.5 and 4.7.6 release candidates available

[Turunen Tuukka]

Hi Thiago,

The whole idea of 4.6.5 and 4.7.6 is to unfork these and unify. It has
never been about making a Digia specific release. We have no intention to
make any Digia specific 4.6 and 4.7 release - quite the opposite - we wish
to unify those releases that have been done earlier (and even then we
actually preferred in having the 4.6.4 and 4.7.5 release to be in the
right place, which was not possible at the time).

It is hard to change history, but we can at least come up with such a
solution that where 4.6 and 4.7 branches end things are somewhat aligned.

As discussed earlier the rationale for making 4.6.5 and 4.7.6 releases is:

-> Do the copyrights change also in packages
-> Address important security vulnerabilities
-> "Unfork" 4.6 and 4.7 branches

Š and all this done in such a way that does not take overwhelmingly high
amount of time as it is away from Qt 5 and 4.8 work.

What we are proposing is somewhat the same as you listed as 'Plan II'.

Yours,

--

Tuukka Turunen
Director, R&D
Digia, Qt

Address: Piippukatu 11, 40100 Jyväskylä, FINLAND
Email: tuukka.turunen at digia.com
Mobile: + 358 40 7655 800

Qt Website: http://qt.digia.com
Qt Blog: http://blog.qt.digia.com
Qt Project: http://www.qt-project.org

------------------------------------------------------------------
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.
------------------------------------------------------------------






On 19.2.2013 18.14, "Thiago Macieira" <thiago.macieira at intel.com> wrote:

>On sexta-feira, 21 de dezembro de 2012 16.11.08, Salovaara Akseli wrote:
>> We have created Qt 4.6.5 and 4.7.6 release candidates that bring the
>> following changes over the previous ones in their series:
>
>$ ncftpls ftp://ftp.qt-project.org/qt/source/*4.7.*.tar.gz
>qt-everywhere-opensource-src-4.7.0.tar.gz
>qt-everywhere-opensource-src-4.7.1.tar.gz
>qt-everywhere-opensource-src-4.7.2.tar.gz
>qt-everywhere-opensource-src-4.7.3.tar.gz
>qt-everywhere-opensource-src-4.7.4.tar.gz
>
>What happened to 4.7.5?
>
>Answer: it was a Digia release. (cf discussion in https://codereview.qt-
>project.org/48232)
>
>The next Qt 4.7 release from the Qt Project is 4.7.5. I am fine still
>with the 
>plan as posted:
>
>> We do not want to add other than important security fixes and mandatory
>> copyright changes in order not to cause regressions.
>
>But the content (the 4.6-digia and 4.7-digia branches) is not following
>the 
>plan. They include a lot of unrelated changes that aren't the copyright
>changes and security fixes. And there has been an extra security fix
>since then 
>that isn't in those vendor branches.
>
>I propose therefore the following plan (Plan I):
>
>1) release Qt Project's Qt 4.6.5 and 4.7.5 following the plan above, by
>branching off the latest tags (4.6.4 and 4.7.4), applying the security
>fixes and 
>the copyright changes
>
>2) release again Qt Project's 4.7.6 that includes those plus all the
>other 
>fixes
>
>3) after that, Digia is allowed to release 4.7.6-digia.
>
>
>Alternative plan (Plan II):
>1) release Qt Project's 4.7.6 and announce that we're skipping one
>version 
>number to align with a past commercial release by Digia, but that it
>won't 
>happen again. This release must come from the 4.7 branch, not the
>4.7-digia 
>branch.
>
>2) after that, Digia is allowed to release 4.7.6-digia.
>
>
>And Plan III:
>1) Digia releases 4.7.4-digia2 or 4.7.5-digia2, without increasing the
>main Qt 
>version number again. That is not a Qt Project release.
>
>Remember: only the Qt Project can create a new Qt version number.
>
>-- 
>Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center