Hi,
On 01/05/2017 07:17, Sean Harmer wrote:
Hi,
is there any documentation for the new configuration system please?
My specific issue is that I need a config test that uses different
library names on each platform and I can't see how to achieve this. On
windows I want the FBX config test in Qt
Hi,
Well, that's true: We have created initial ones for maintainers to start with
few previous releases. We can do the same for this time as well. Hoping already
tomorrow
br,
Jani
From: Simon Hausmann
Sent: tiistaina 2. toukokuuta 2017 17.09
To: Jani Heikkinen ; development@qt-project.org
Subj
Hi,
I'm a bit confused. The release team usually did the initial commit and
maintainers edited the content. I'm fine with doing it myself, but I'm just
wondering: Is there an intentional change in procedure?
Simon
From: Development on
behalf of Jani Heikki
On Tuesday, 2 May 2017 02:48:15 CDT René J. V. Bertin wrote:
> I'm aware of the direct reason. Apparently you're sure enough that the CI
> failure is without consequence to put the burden and responsibility of
> incorporating the patch on end-users. That's what I mean with getting an
> internal act
On Tuesday, 2 May 2017 06:32:48 CDT Thiago Macieira wrote:
> On Tuesday, 2 May 2017 02:48:15 CDT René J. V. Bertin wrote:
> > Thiago Macieira wrote:
> >
> > At the very least there should be alternative binaries (QtCore? QtDBus?)
> > available for download with the patch applied to which you can p
On Tuesday, 2 May 2017 02:48:15 CDT René J. V. Bertin wrote:
> Thiago Macieira wrote:
>
> At the very least there should be alternative binaries (QtCore? QtDBus?)
> available for download with the patch applied to which you can point people
> who report related issues, and the patch itself should
Hi all Maintainers!
Branching from '5.9' to '5.9.0' is now ongoing and it is time to start creating
change files for Qt 5.9.0. Please do the initial ones as soon as possible. And
if some important change is coming in after the initial ones are in change
owner can (& have to) update the change f
>The text duplication is silly, and I have seen several places where
>information was inadvertently added to only one of the overloads.
We still need a way to tell qdoc how to provide information that applies to one
overload, or to a subset of the \fn overloads in the list.
martin
__
Hi all,
Qt 5.9 beta3 is now available. Instructions how to get the release are here:
https://wiki.qt.io/How_to_get_snapshot_via_online_installer. Diff to second
beta can be found as an attachment.
Please test the release and report your effort via
https://wiki.qt.io/Qt59_release_testing. I hop
Hi all,
Qt 5.9 beta3 is available. As earlier you can update it at the top of your Qt
5.9 beta(2) online installation or do clean installation by using qt online
installer. Detailed instructions here:
https://wiki.qt.io/How_to_get_snapshot_via_online_installer
br,
Jani Heikkinen
Release Manage
Hi,
On 02/05/2017 09:25, Oswald Buddenhagen wrote:
On Mon, May 01, 2017 at 07:17:23AM +0100, Sean Harmer wrote:
is there any documentation for the new configuration system please?
the "documentation" is the vast amount of configure.json files which
actually use it.
Thanks, but that doesn't
On Mon, May 01, 2017 at 07:17:23AM +0100, Sean Harmer wrote:
> is there any documentation for the new configuration system please?
>
the "documentation" is the vast amount of configure.json files which
actually use it.
> My specific issue is that I need a config test that uses different
> library
On 28/04/2017 09:35, Marc Mutz wrote:
TL;DR: I propose to document overloaded functions with a single comment block,
containing multiple \fn's and a common documentation text, to be rendered as
one documentation block preceded by a listing of all the \fn's, instead of as
individual functions.
Thiago Macieira wrote:
At the very least there should be alternative binaries (QtCore? QtDBus?)
available for download with the patch applied to which you can point people who
report related issues, and the patch itself should be provided with the sources
(in the tarball or clearly listed on th
Hi,
On 01/05/2017 14:16, Thiago Macieira wrote:
On Monday, 1 May 2017 03:17:23 -03 Sean Harmer wrote:
Hi,
is there any documentation for the new configuration system please?
My specific issue is that I need a config test that uses different
library names on each platform and I can't see how t
Hi,
While I do agree that having a platform in CI and supporting it for those who
have purchased support are not 1:1, in case of dropping the 32-bit iOS from CI
for Qt 5.10 it also means that this configuration should no longer be used and
not be supported. I do not see much problems with that
16 matches
Mail list logo