[Development] Qt 4.6.5 and 4.7.6 release candidates available

[Turunen Tuukka]

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

>On terça-feira, 19 de fevereiro de 2013 19.29.50, Turunen Tuukka wrote:
>> Hi Thiago,
>> 
>> Due to the way earlier releases are done it is not possible to have
>> perfectly clean history. This has been discussed in December and after
>>the
>> different options were analysed it was seen the best one to do as it now
>> is. End result is the same, we have 4.6.5 and 4.7.6 releases available
>>in a
>> way closer to where they should be.
>
>I understand how the previous releases were done, but I disagree on the
>plan. 
>I want the changes in the 4.7 branch released and I don't want the
>changes in 
>the 4.7-digia branch released unless the rest of the Qt Project is given
>the 
>opportunity to review them.

These are all already reviewed as the items are from 4.7 or 4.8 branch.
There is no new functionality and we are not proposing to sneak in
something. To our knowledge e.g. 4.7.5 has been used quite much by the
LGPL users, and from that perspective 4.7.6 is a natural addition.

As said before this does not represent the way branches should be handled,
but in these circumstances it is seen as the best approach - especially
since everything is ready and tested now - we just need to release
packages and make sure right branch is found.

>
>> We have the packages ready and tested with minor fixes compared to RC1
>>(21st
>> Dec). If we re-do these packages it is a significant effort with very
>> limited benefits.
>
>Sorry, the current packages are a complete no-go. They need to be
>recreated 
>anyway, since they're missing the shmget security fix.

As the shmget security fix changes behavior and its risk rating, I would
not like to put it into these.

And if we start re-do packages and release content we will delay work with
5.0.x and 5.1.x releases, which I am sure no-one wants.

>
>Let's compromise then: we release the 4.7-digia branch provided that the
>4.7 
>branch also gets released within six months. Plan:
>
>1) the security fix is backported into the 4.x-digia branches

The fixes included should be the ones also in the RC1 in my opinion as the
shmget contains functionality change prone to cause problems.

>
>2) we review all changes made to those branches that aren't in the
>respective 
>4.x branch, with silent approval: if no one objects, the change is
>approved

There is none of such to my knowledge.

>
>3) we release from the 4.x-digia branch, with the public note of the
>mistake 
>in the 4.7 version number

We can omit the -digia as it causes confusion.

>
>4) we merge the 4.x-digia branch into the 4.x branch and close the
>4.x-digia 
>branch
>
>5) we release Qt 4.7.7 within six months
>
>I'd like to hear that there will be people allocated to doing the release
>work 
>for the changes that went into the Qt 4.7 branch in the past year since
>the 
>two branches diverged.

As mentioned these are already done when the original contributions have
been made.

--
Tuukka

>
>-- 
>Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center