On 07/10/14 11:02, "Mark Gaiser" wrote:
>
>1. The download to the community version of Qt from
>http://www.qt.io/download/ links to http://www.qt.io/?p=323 which
>redirects to http://www.qt.io/download-open-source/ .. A bit weird.
>2. Again on http://www.qt.io/download/ the "Download" button for
Hi,
Thanks for your feedback related to qt.io opensource downloads page:
http://www.qt.io/download-open-source/
The page is now updated based on your comments - the major changes are:
1. Automatic download is now completely removed
* Recommended download is still highlighted and you can start dow
Hi,
As you probably are aware, there has been a long thread on interest
list about Qt dependency bloat. One of the most commented problems
has been Perl dependency, especially on Windows.
We have had similar feedback on commercial support channels.
One quite simple change what we could do alrea
Hi,
As you probably have noted, Qt-Project CI have had WEC7 ARM
build jobs running in a non-blocking mode for a while.
The jobs are build only, and don't execute any autotests.
Now that Björn Breitmeyer has been proposed as a maintainer for
Windows Embedded, and there have not been any objectio
Jason McDonald wrote:
> On Wed, Mar 13, 2013 at 2:42 AM, Thiago Macieira
> wrote:
>> On terça-feira, 12 de março de 2013 13.28.37, Motyka Rafal wrote:
>>> Hello,
>>>
>>> I want to suggest another change for JIRA: - A Reporter should be able
>>> to set the Priority starting from the Create Issue
Laszlo Papp wrote:
> To summarize the automated testing topic.
>
> 1) QtMock will not reach a usable state any soon, unfortunately.
>
> 2) I am not sure which construction of the aforementioned ones would fit
> the operation of the CI machines. Could anyone please comment on that
> with the rel
Sergio Ahumada wrote:
>
> I would like to nominate Iikka to be an approver in the Qt project.
>
> Iikka is one of the key persons responsible for all the releases made by
> Digia in the past and now together with the Qt Project.
>
> This includes both Qt 4.x and Qt 5.x releases in both the com
Koehne Kai wrote:
>>
>> [...] Below is list of failed autotests from already executed MinGW
>> stages:
>>
>> QtActiveQt_dev_Integration [1]
>>
>> === Failures:
>> ===
>> cmake
>> === Totals: 3 tests, 2 passes, 1 fail
>
Hi,
Before Christmas vacations I announced that configuration for MinGW
CI stage was added among the other new stages. Unfortunately there
was bug in CI scripts which prevented autotest execution on MinGW
builds. This bug has been fixed now and there are already some auto
test results available f
Hi,
There is now MinGW 4.7 (Win7 x86) and VS2012 (Win8 x64) stages added for
all CI projects. In addition there is OSX 10.8 stage currently added only for
Qt5_stable_integration CI project. We will add OSX 10.8 for all CI projects
later
on when more Mac capacity is available (hopefully in the b
Hi,
I had some concerns related to change that was introduced lately to
CI testconfigs:
https://codereview.qt-project.org/42954
https://codereview.qt-project.org/42955
In short the question is whether we should have forcesuccess and
qt.tests.insignificant configured on CI branch basis
Laszlo Papp wrote:
>> On Thu, Nov 29, 2012 at 8:03 AM, Knoll Lars wrote:
>>
>>
>> I know that branch naming is a possible topic for endless bike
>> shedding. You can always find arguments against a certain name here. In
>> the end it's not the most important thing whether it's called testing or
Hi,
I have been following discussion on this thread for a while now and here
are some comments from CI point of view. First I would like to list
existing CI configurations since there clearly are some misunderstandings:
Qt 4.8
linux-g++-32_Ubuntu_10.04_x86
linux-g++_developer-build_qtna
I thought it might be good idea to summarize what has been happening on CI
lately.
So here is summary about CI system changes and some status info from weeks
44-45:
1. OpenSSL installed to Windows CI testers
-> Auto-detection for configure time check is now true
-> SSL related auto test
Koehne Kai wrote:
> Now that the big thing (CI system migration) is done, I'm wondering whether
> we can get also MinGW into the CI system for Qt 5? It's a Tier 1 platform, so
> it should really be part of the CI testing. I understand that in the past we
> didn't do it because the outdated gcc in
Bornemann Joerg wrote:
> On 29/10/2012 14:29, Anttila Janne wrote:
>
>> 4. Marked flaky tst_qlocalsocket autotest insignificant:
>> https://codereview.qt-project.org/38137
>
> Could you please point me to a log that shows that this test is flaky in
> Qt 4.8? I ca
Hi,
There have been various problems on Qt 4.8 CI since we moved that project
from Nokia to Digia hosting - I'm sorry that those problems have been
preventing you to get anything in to Qt 4.8 since last Thursday.
Apparently I made wrong decision to move 4.8 CI from Nokia hosting to Digia
hosti
Hi,
Qt-Project CI system migration to Digia hosting has been completed.
The last three projects (QtBase_master_Integration,Qt_4.8_Integration
and Qt5_master_Integration) were migrated during this morning.
AFAIK migration for all expect one last project succeeded without any
problems. There we
Rohan McGovern wrote:
> In preparation for the transfer of remaining systems from Nokia to
> Digia, various projects covered by the Qt CI will soon be migrated from
> Nokia's Pulse infrastructure to a new Jenkins setup.
>
Transferring Qt CI projects from Nokia Pulse infra to a new Jenkins based
Hi,
Lars mentioned in "Digia acquisition closed" mail a while ago that we need to
change the copyright headers in all Qt source files from Nokia to Digia.
AFAIK: Iikka did that work for master branch in all Qt5 repositories. However
in some of the Qt5 repositories there are other branches as w
Lars Knoll wrote:
> In general I like the model. As Thiago said it's pretty close to what we've
> been
> discussing internally before we started Qt 5 development.
>
> I agree that we should kickstart the model after the beta release. Branch
> names should be more concrete and for outsiders to un
Hi,
Currently there are 3rdparty zlib sources in both qtbase and qtsvg
repositories, and in addition building zlib dependent imageformat plugins (mng,
tiff) are disabled in qtimageformats repo if platform does not have system zlib
available.
Already now zlib sources in qtbase and qtsvg have div
> -Original Message-
> From: development-bounces+janne.anttila=digia@qt-project.org
> [mailto:development-bounces+janne.anttila=digia@qt-project.org] On
> Behalf Of Oswald Buddenhagen
> Sent: 17. huhtikuuta 2012 12:44
> To: development@qt-project.org
> Subject: Re: [Development] M
Hi,
I started building Qt5 for WinCE and WEC7, and found that checksdk is not
currently build by configure and it has been moved to QtTools repo.
Checksdk.exe is an utility to read WinCE environment from Visual Studio
configuration file and it is used by setcepaths.bat. Setcepaths.bat is called
> From: Thiago Macieira
> On Monday, 19 de December de 2011 09.40.44, David Faure wrote:
> > > What should this do for something like 4.8.0c? Better to not confuse
> > > things
> > > and to leave the version number as it was. In practice, I'd be surprised
> > > if
> > > there was much confusion ca
25 matches
Mail list logo
