On Friday, 20 September 2019 02:26:34 PDT Edward Welbourne wrote:
> The qtbase/tests/manual/corelib/ tests all date back to 2013 (aside from
> some copyright header updates).
Some of them are actually much older:
https://code.qt.io/cgit/qt/qt.git/tree/tests/manual
The whole point of a manual test
Hi,
Documentation is the authorative source. It is maintained and checked for each
Qt release. We should make sure the platform notes are correct and complete.
Misleading information in wiki should be deleted or marked as deprecated.
Similar activity has been done to other pages, sometimes we m
Asmo Saarela (20 September 2019 08:30)
> I would like to understand the content and the use of the manual test assets
> in the Qt modules.
> Could you provide a few examples of how you are using, maintaining, and
> developing those?
The qtbase/tests/manual/corelib/ tests all date back to 2013 (a
Il 20/09/19 07:53, Tuukka Turunen ha scritto:
Or remove the wiki entry and make sure platform notes in documentation are in
shape?
No need for duplicated info on these basic items.
It's a bigger problem -- the *same* wiki is used for official
information (e.g. releasing info; coding guidelin
On Fri, 20 Sep 2019 at 10:10, Allan Sandfeld Jensen wrote:
> I am pretty sure we strongly depend on some of those features now.
> Realistically I don't think we support any compiler older than what the CI
> tests for which I believe is GCC 4.9.
Close enough, 4.8.
> -Original Message-
> From: Development On Behalf Of
> Asmo Saarela
> Sent: Friday, 20 September 2019 8:30 AM
> To: development@qt-project.org
> Subject: [Development] Question about tests/manual folders
>
> Hi all,
>
>
>
> I would like to understand the content and the use of the man
On Friday, 20 September 2019 00:07:38 CEST Thiago Macieira wrote:
> On Thursday, 19 September 2019 03:17:12 PDT Giuseppe D'Angelo via
> Development
> wrote:
> > On 18/09/2019 17:33, Thiago Macieira wrote:
> > >>> We've never required C++11 Standard Library. We've only required the
> > >>> core
> >
