On Tuesday 26 February 2013 10:22:27 Thiago Macieira wrote:
> On domingo, 24 de fevereiro de 2013 09.34.43, Thiago Macieira wrote:
> The backport of 8afc6773067bb878020c29b3bebfe8662e3fbfdd (as
> 2fd21f04d23d5dd87ca0f6db238ae268492f5528) to add support for signed char as
> a metatype is dubious. I
On domingo, 24 de fevereiro de 2013 09.34.43, Thiago Macieira wrote:
> However, I can't be sure because the diff between the two branches is
> unreviewable, since every header is modified. Someone needs to produce a
> clean diff we can review and post to the list.
Tuukka told me in an email prob
On domingo, 24 de fevereiro de 2013 06.43.24, Turunen Tuukka wrote:
> Getting back to the topic of these releases - what is our decision?
>
> Shall we do the RC2 as proposed, but with shmget fix in 4.7.6, and later go
> to release unless problems are found? This would mean we accept that there
>
Thiago Macieira [thiago.macie...@intel.com] puolesta
Lähetetty: 21. helmikuuta 2013 20:07
Vastaanottaja: development@qt-project.org
Aihe: Re: [Development] Qt 4.6.5 and 4.7.6 release candidates available
On quinta-feira, 21 de fevereiro de 2013 13.00.50, Turunen Tuukka wrote:
> -> Digia did
On 21 February 2013 12:53, Turunen Tuukka wrote:
>
>
> This is incorrect assumption as we have discussed this before making the
> RC1 - it just took a lot of time due to other release creation activities
> to continue the releasing work, so it seems that some persons (at least
> Thiago) just notic
On 21.02.2013 14:00, Turunen Tuukka wrote:
>
> Unfortunately we do not have unlimited resources in the release team, so
> pointlessly redoing the packages is not something I want to do.
>
I would release the already packaged versions as they are as a
Digia-only release, and skip 4.8.5/4.7.6 in the
On quinta-feira, 21 de fevereiro de 2013 11.53.42, Turunen Tuukka wrote:
> On 21.2.2013 10.07, "Peter Kümmel" wrote:
> >On 19.02.2013 20:29, Turunen Tuukka wrote:
> >> We have the packages ready and tested with minor
> >>
> > > fixes compared to RC1 (21st Dec). If we re-do these
> > > packages it
On quinta-feira, 21 de fevereiro de 2013 13.00.50, Turunen Tuukka wrote:
> -> Digia did 4.6.4 and 4.7.5 releases for the needs of the commercial
> customers
> -> Digia did similar releases for LGPL
> -> These were not accepted for distribution at the time (by Nokia)
> -> Source code is available in
ia@qt-project.org
> [mailto:development-bounces+akseli.salovaara=digia@qt-project.org]
> On Behalf Of Turunen Tuukka
> Sent: 21. helmikuuta 2013 15:01
> To: Thiago Macieira; development@qt-project.org
> Subject: Re: [Development] Qt 4.6.5 and 4.7.6 release candidates
Long emails and good discussion. It would have been great to have this in
December, but better late than never.
To summarize, here is the situation up until now:
-> Digia did 4.6.4 and 4.7.5 releases for the needs of the commercial
customers
-> Digia did similar releases for LGPL
-> These were n
The original talk in Dec, 2012:
http://lists.qt-project.org/pipermail/releasing/2012-December/000930.html
Maybe not many people have noticed it.
In my own opinion, they are from 4.7-digia and 4.6-digia branch, better name
the packages like that. Otherwise, need to merge them to upstream at first
On 21.2.2013 10.07, "Peter Kümmel" wrote:
>On 19.02.2013 20:29, Turunen Tuukka wrote:
>>
>> 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.
>>
>
>It seems to me this alrea
On 19.02.2013 20:29, Turunen Tuukka wrote:
>
> 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.
>
It seems to me this already happens before:
you first do the packaging and the
On 21.2.2013 2.43, "Thiago Macieira" wrote:
>On quarta-feira, 20 de fevereiro de 2013 16.34.19, Thiago Macieira wrote:
>> You cannot make that call alone. What's more, we discussed the problem
>>and
>> the solution for two months in the security mailing list, which you're
>>a
>> part of. If th
On quarta-feira, 20 de fevereiro de 2013 16.34.19, Thiago Macieira wrote:
> You cannot make that call alone. What's more, we discussed the problem and
> the solution for two months in the security mailing list, which you're a
> part of. If there's a problem, please start a new thread on this maili
On quarta-feira, 20 de fevereiro de 2013 21.03.10, Turunen Tuukka wrote:
> >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
On 19.2.2013 22.02, "Thiago Macieira" 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
>> diff
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
: 19. helmikuuta 2013 20:16
Vastaanottaja: development@qt-project.org
Aihe: Re: [Development] Qt 4.6.5 and 4.7.6 release candidates available
On terça-feira, 19 de fevereiro de 2013 16.42.44, Turunen Tuukka wrote:
> Hi Thiago,
>
> The whole idea of 4.6.5 and 4.7.6 is to unfork these and
On terça-feira, 19 de fevereiro de 2013 16.42.44, Turunen Tuukka wrote:
> 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 oppos
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
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.
22 matches
Mail list logo
