On 4/5/13 12:45 PM, "Axel Waggershauser" wrote:
>Sorry for the noise, I have to correct myself again :-( There is
>no chrome_m26 branch. The last one prior to chrome_m27 is chrome_m24
>and that one does not contain the above mentioned fix for the warning.
>Hence, chrome_m27 (which does contain
On 4/5/13 12:45 PM, "Axel Waggershauser" wrote:
>On Fri, Apr 5, 2013 at 12:20 PM, Axel Waggershauser
>wrote:
>>> Based on that and without an answer from Oswald which revision is
>>> currently in preparation within the winrt branch, I'd suggest to go
>>> for the latest Chrome related branch, whi
On Fri, Apr 5, 2013 at 12:20 PM, Axel Waggershauser wrote:
>> Based on that and without an answer from Oswald which revision is
>> currently in preparation within the winrt branch, I'd suggest to go
>> for the latest Chrome related branch, which would be chrome_m27:
>> http://code.google.com/p/ang
On Fri, Apr 5, 2013 at 12:18 PM, Axel Waggershauser wrote:
> On Thu, Mar 28, 2013 at 9:18 PM, Axel Waggershauser wrote:
>> (I went ahead and posted a question on the ANGLE ML asking which
>> 'stable' revision they would suggest to ship with Qt 5.1.)
>
> I got the following reply on the ANGLE ML:
On Thu, Mar 28, 2013 at 9:18 PM, Axel Waggershauser wrote:
> (I went ahead and posted a question on the ANGLE ML asking which
> 'stable' revision they would suggest to ship with Qt 5.1.)
I got the following reply on the ANGLE ML:
--
Trunk is generally pretty stable unless a bunch of changes
On Thu, Mar 28, 2013 at 9:09 PM, Oswald Buddenhagen
wrote:
> On Thu, Mar 28, 2013 at 08:44:13PM +0100, Axel Waggershauser wrote:
>> P.S. this is not necessarily an offer to do the upgrade myself (I
>> don't even have enough space to build qt on my windows partition right
>> now) but I might be con
On Thu, Mar 28, 2013 at 08:44:13PM +0100, Axel Waggershauser wrote:
> P.S. this is not necessarily an offer to do the upgrade myself (I
> don't even have enough space to build qt on my windows partition right
> now) but I might be convinced to do so if no one else feels
> 'responsible' for ANGLE.
>
On Wed, Mar 20, 2013 at 5:50 PM, Thiago Macieira
wrote:
> qtbase:
> ANGLE (*)
If I followed this thread sufficiently, it seems as if no one has yet
made a statement about the update of ANGLE. I just remembered that a
couple of weeks ago I came across this warning message when running
some
> qtbase:
> Freetype (*)
https://codereview.qt-project.org/#change,52240 +
https://codereview.qt-project.org/52241
Konstantin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Onsdag 20. mars 2013 09.50.22 skrev Thiago Macieira:
> Hello
>
> We're feature-freezing 5.1. It's time to verify if any of the third-party
> libraries we include in Qt need updating to newer versions. I recommend
> updating all of them to their latest versions.
>
> Do we have volunteers?
>
> Lis
On 21 March 2013 18:39, Thiago Macieira wrote:
> On quinta-feira, 21 de março de 2013 18.37.52, Giuseppe D'Angelo wrote:
>> And have the test fail if a system-wide 8.30 / 8.31 is picked? Does
>> anyone know the situation on the CI machines? (Ubuntu ships 8.30 with
>> 12.10, CI should use 12.04, so
On quinta-feira, 21 de março de 2013 18.37.52, Giuseppe D'Angelo wrote:
> And have the test fail if a system-wide 8.30 / 8.31 is picked? Does
> anyone know the situation on the CI machines? (Ubuntu ships 8.30 with
> 12.10, CI should use 12.04, so we should be fine...)
I thought the CI system only
On 21 March 2013 16:01, Thiago Macieira wrote:
> On quinta-feira, 21 de março de 2013 12.03.05, Giuseppe D'Angelo wrote:
>> Replying to myself: upgrading to 8.32 actually causes failures in
>> QString tests -- an expected failure passes (line 1165 in
>> tst_qstring.cpp), as case folding support wa
On quinta-feira, 21 de março de 2013 12.03.05, Giuseppe D'Angelo wrote:
> Replying to myself: upgrading to 8.32 actually causes failures in
> QString tests -- an expected failure passes (line 1165 in
> tst_qstring.cpp), as case folding support was finally added to PCRE.
> Although distributions pro
On 20 March 2013 20:04, Giuseppe D'Angelo wrote:
>
> PCRE 8.31 and 8.32 do indeed introduce new features as well as fix
> various bugs, so I'm a bit undecided whether it's worth including them
> in stable at this point, although slightly inclined for the inclusion
> (we won't use the new features;
> Sqlite (*)
done.
https://codereview.qt-project.org/#q,status:open+project:qt/qtbase+branch:stable+topic:sqlite-upgrade,n,z
Mark
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On quarta-feira, 20 de março de 2013 18.52.40, Qi Liang wrote:
> Then this "Updating" notice doesn't have much meaning in this very short
> periode. I would suggest only important bug fix should go into stable
> branch. All general updates should happen in dev branch after the frozen.
> Better to h
On 20 March 2013 17:50, Thiago Macieira wrote:
> PCRE (*)
PCRE 8.31 and 8.32 do indeed introduce new features as well as fix
various bugs, so I'm a bit undecided whether it's worth including them
in stable at this point, although slightly inclined for the inclusion
(we won't use the new f
> Actually, the merges are already happening, so 5.1 *is* feature frozen.
>
> Please target your updates to stable if you're updating within minor (non-
> feature) releases of your third-party or if you're fixing important bugs.
>
> Updates for the sake of update should be in dev and will wait for
On quarta-feira, 20 de março de 2013 09.50.22, Thiago Macieira wrote:
> We're feature-freezing 5.1. It's time to verify if any of the third-party
> libraries we include in Qt need updating to newer versions. I recommend
> updating all of them to their latest versions.
Actually, the merges are alre
>qtimageformats:
> libmng
> libtiff
libmng is some kind of obsolete, last release is 20030305.
I had two patches for libtiff, just not merged in before the BIG merge.
Resubmitted to stable branches already.
Regards,
Liang
___
Development m
> qtbase:
> Harfbuzz
Done.
Konstantin
2013/3/20 Thiago Macieira :
> Hello
>
> We're feature-freezing 5.1. It's time to verify if any of the third-party
> libraries we include in Qt need updating to newer versions. I recommend
> updating all of them to their latest versions.
>
> Do we have
Hello
We're feature-freezing 5.1. It's time to verify if any of the third-party
libraries we include in Qt need updating to newer versions. I recommend
updating all of them to their latest versions.
Do we have volunteers?
Listing of third-party libraries (high-priority items marked with *):
q
23 matches
Mail list logo
