> On 18 Sep 2019, at 01:37, Thiago Macieira wrote:
>
> On Tuesday, 17 September 2019 16:05:34 PDT Giuseppe D'Angelo via Development
> wrote:
>> While I agree that at the moment it has virtually never happened, it
>> doesn't mean it couldn't happen in the future. Even today we have
>> compilers s
On Tuesday, 17 September 2019 16:05:34 PDT Giuseppe D'Angelo via Development
wrote:
> While I agree that at the moment it has virtually never happened, it
> doesn't mean it couldn't happen in the future. Even today we have
> compilers such as MSVC with "living on the edge" compile flags
> (/c++lat
Hi,
Il 09/09/19 14:44, Mutz, Marc via Development ha scritto:
3. The wider C++ community seems to settle for non-versioned checks if
the initial version is sufficient, which may mean that Qt introduces an
impedance mismatch for pre-standard values where Qt checks the version
and users and other
On Tue, Sep 17, 2019 at 12:39:01PM +, Simon Hausmann wrote:
Am 17.09.19 um 14:27 schrieb Oswald Buddenhagen:
for example, the information that a build with updated dependencies
is required can be stored as an annotation in the commit message
(that's exactly what zuul does, afaik), and the i
Am 17.09.19 um 14:27 schrieb Oswald Buddenhagen:
> On Tue, Sep 17, 2019 at 06:56:39AM +, Simon Hausmann wrote:
>> When the todo list is empty and there are no more pending updates,
>> the batch update is complete. If during that update there were no
>> failures, the Qt Module Updater will al
On Tue, Sep 17, 2019 at 06:56:39AM +, Simon Hausmann wrote:
When the todo list is empty and there are no more pending updates, the
batch update is complete. If during that update there were no failures,
the Qt Module Updater will also push a change to qt5.git with an update
to all submodule
Also, looks like old components can now be archived!
- Tor Arne
> On 17 Sep 2019, at 09:08, Alex Blasche wrote:
>
> Hi,
>
> The server will be upgraded from Jira version 7.13 to 8.2. If all goes well,
> the process should take about 1 hour.
>
> --
> Alex
> ___
On 17.09.19 11:27, Kevin Funk via Development wrote:
OT: Out of curiosity: Why was "dev" chosen over "master" as main development
branch in the first place? What's the benefit? This is also something which
might confuse new contributors easily, as it's not the Git standard
nomenclature.
If we ev
On Monday, 16 September 2019 14:10:51 CEST Lars Knoll wrote:
> On 16 Sep 2019, at 13:26, Albert Astals Cid via Development
> mailto:development@qt-project.org>> wrote:
> El dilluns, 16 de setembre de 2019, a les 13:22:22 CEST, Frederik Gladhorn
> va
escriure:
> On mandag 16. september 2019 12:22
I’d say yes, let’s merge those into dev as well. Those are all platforms we
don’t want to support in Qt 6.0. (tvOS, watchOS and Integrity might come back
at some point).
Cheers,
Lars
On 17 Sep 2019, at 09:56, Simon Hausmann
mailto:simon.hausm...@qt.io>> wrote:
I'm leaning towards the same.
I'm leaning towards the same.
Regarding the overall merge, there is one other change that needs to happen
before we can have a chance at building qtbase:
In the wip/qt6 branch in commit 5677a43a25a9dc1a3151e6b28cbf9fe015a1aff4 in
qt5.git, various platforms and configurations were removed from
Hi,
Great to get the wip/qt6 branches merged back into dev. I’d simply try to take
the dependencies.yaml into use at the same time instead of having to work
around the CI.
Cheers,
Lars
On 17 Sep 2019, at 09:05, Simon Hausmann
mailto:simon.hausm...@qt.io>> wrote:
Hi,
Now that the Qt 5.15 bra
Hi,
Now that the Qt 5.15 branches exist and dev is intended to become Qt 6.0.0, the
time has come to begin merging the wip/qt6 branches into dev. A wip/qt6 branch
has been created for pretty much all repositories in qt6.git that are active
(essential, addon, etc.) and two types of changes have
Hi,
The server will be upgraded from Jira version 7.13 to 8.2. If all goes well,
the process should take about 1 hour.
--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
14 matches
Mail list logo
