Re: [Development] [Releasing] [Interest] download.qt.io is down

[Tuukka Turunen]

Hi,

Status update of the problem with open-source downloads: Last night we finally 
got a disk big enough for the packages from the service provider. Most of the 
data has been transferred throughout the night with a few last things still 
being uploaded to the new virtual server. After the data transfer is complete 
we start testing and validation of the data and the system. Target is to enable 
first the online installer, then the offline packages and finally the achieve 
of old releases.

Yours,

Tuukka

From: Development 
Date: Thursday, 21. January 2021 at 18.08
To: Qt Project Development 
Subject: Re: [Development] [Releasing] [Interest] download.qt.io is down
Hi,

Status update on the open-source distribution topic is that we are still 
waiting for the cloud service provider. Today they been able to provide us with 
new virtual machines for the distribution, but not yet big enough disk space 
for the release data. As soon as we have the disk available, we can start 
transferring the release packages to it, test that everything works and put the 
system back online.

Yours,

Tuukka


From: Sze Howe Koh 
Date: Wednesday, 20. January 2021 at 16.09
To: Tuukka Turunen 
Cc: Qt Project Development 
Subject: Re: [Releasing] [Interest] download.qt.io is down
Thank you for clarifying, Tuukka.

I am (along with many others, I'm sure) delighted to hear about the
upcoming ability to officially select mirrors, and look forward to an
improved download experience going forward. MirrorBrain does not
always pick the best source. [1]

Best of luck with setting up an alternative file server.


Regards,
Sze-Howe

[1] https://lists.qt-project.org/pipermail/development/2018-April/032461.html


On Wed, 20 Jan 2021 at 18:35, Tuukka Turunen  wrote:
>
> Hi,
>
>
>
> To explain a bit why I was mistaken about the online in the mail I sent last 
> night. We have a development feature that allows selecting the mirror 
> manually. I thought it could be used, but it turned out we had not released 
> that version of the installer. Would have been handy, but since it is not 
> already released, the best approach is to re-create the master. We are doing 
> that now. We will also have this feature in the installer released (after we 
> can again make releases), because it is sometimes handy to tell explicitly 
> what server to download from.
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
> From: Development 
> Date: Wednesday, 20. January 2021 at 8.06
> To: Sze Howe Koh 
> Cc: development@qt-project.org , 
> releas...@qt-project.org , Interests Qt 
> 
> Subject: Re: [Development] [Releasing] [Interest] download.qt.io is down
>
> Hi,
>
>
>
> Yes, this is correct.
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
> From: Sze Howe Koh 
> Date: Wednesday, 20. January 2021 at 0.10
> To: Tuukka Turunen 
> Cc: Mark Long , development@qt-project.org 
> , Interests Qt , 
> releas...@qt-project.org 
> Subject: Re: [Releasing] [Interest] download.qt.io is down
>
> On Wed, 20 Jan 2021 at 04:10, Tuukka Turunen  wrote:
> >
> >
> > Hi,
> >
> > There are multiple mirrors, try for example:
> >
> >
> >
> > https://qt-mirror.dannhauer.de/
> >
> > https://www.funet.fi/pub/mirrors/download.qt-project.org/
> >
> > https://ftp.fau.de/qtproject/
> >
> >
> >
> > ...or just use the online installer, which picks mirrors automatically.
> >
> > Yours,
> >
> > Tuukka
>
> Hi Tuuka,
>
> The Online installer downloads files in 2 phases:
>
> 1. Retrieve metadata from download.qt.io
> 2. Retrieve actual binaries from the auto-selected mirror
>
> Since Step #1 is blocked, it can't proceed to Step #2.
>
>
> Regards,
> Sze-Howe
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Repository request: qlitehtml

[Kai Pastor, DG0YT via Development]

Am 21.01.21 um 12:04 schrieb Jaroslaw Kobus:

+1

This may be potentially easily reused in e.g. standalone assistant.


I would like to see qlitehtml integrated into QTextBrowser. This, or a 
source-compatible replacement, would make it available for Qt Assistant, 
too.


Kai Pastor


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt modules, API changes and Qt 6

[Tor Arne Vestbø]

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 incremental propagation of the dependencies can be done 
in a "shadow" branch of the qt5 repository (technically, that could be a single 
gerrit change that gets progressively updated).

Yeah, I was also thinking of using git notes perhaps for storing the 
information separately. (Doesn't seem to be enabled in our Gerrit? Hopefully 
I'm wrong :).

i don't think using git notes is particularly useful here. the number of 
affected commits would be rather low, so having an additional commit message 
footer would not hurt. extracting that information would also be rather easy 
(git log from the last reference point).

Do I understand your proposals correctly:

Let’s say I make a change in qtdeclarative that depends on a merged change 
‘shaA' in qtbase and on ’shaB’ in qtsvg, then I add something like

dependencies: qtbase:shaA qtsvg:shaB

(or whatever syntax we want) to my qtdeclarative commit message?

This information does not belong in the commit message.

It belongs in dependencies.yaml, and a git-merge-driver for dependencies.yaml 
should be able to resolve those to a compatible set for each integration, or 
report back if the dependencies can not be satisfied. This would also avoid the 
dance we have have (had) where a submodule update needs to be carefully staged 
with other changes that depend on it or fix something as a result of the update.

Tor Arne
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt modules, API changes and Qt 6

[Volker Hilsheimer]

Reviving this thread as a follow up to the discussion in the “Qt6 repo” thread 
at

https://lists.qt-project.org/pipermail/development/2021-January/040902.html

> On 17 Sep 2019, at 14:51, Oswald Buddenhagen  
> wrote:
> 
> 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 incremental propagation of the 
>>> dependencies can be done in a "shadow" branch of the qt5 repository 
>>> (technically, that could be a single gerrit change that gets progressively 
>>> updated).
>>> 
>> Yeah, I was also thinking of using git notes perhaps for storing the 
>> information separately. (Doesn't seem to be enabled in our Gerrit? Hopefully 
>> I'm wrong :).
>> 
> i don't think using git notes is particularly useful here. the number of 
> affected commits would be rather low, so having an additional commit message 
> footer would not hurt. extracting that information would also be rather easy 
> (git log from the last reference point).

Do I understand your proposals correctly:

Let’s say I make a change in qtdeclarative that depends on a merged change 
‘shaA' in qtbase and on ’shaB’ in qtsvg, then I add something like

dependencies: qtbase:shaA qtsvg:shaB

(or whatever syntax we want) to my qtdeclarative commit message?

As for the shadow branch(es) in qt5.git or progressively moving gerrit 
change(es):

* change shaX in qtbase merges, breaks qtdeclarative
* bot updates shadow-branch's .gitmodules to point at qtbase:shaX; it’s now 
inconsistent (qtdeclarative doesn’t build or pass tests)
* coin keeps testing qtdeclarative changes against qtbase:shaX~1 (as per 
upstream .gitmodules), changes that don’t depend on shaX merge
* follow-up change shaY in qtdeclarative is staged, with above annotation 
asking for qtbase:shaX
* coin tests qtdeclarative with shaY against qtbase:shaX, as per the shadow 
branch’s .gitmodules. Tests pass, shaY merges, .gitmodules in shadow branch is 
updated to point at qtdeclarative:shaY

Once the round is complete for all sub modules, the existing git submodule 
update process updates .gitmodules in the proper branch, and reset the 
shadow-branch (I suppose).

Was that the idea, Ossi? It puts some extra burden on contributors and 
reviewers (add commit footer with correct sha1, which will need some extra care 
when cherry-picking), but it might be possible for Coin to try to move things 
forward automatically, just as we do now with the dependency update bot.


Volker





___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] [Releasing] [Interest] download.qt.io is down

[Tuukka Turunen]

Hi,

Status update on the open-source distribution topic is that we are still 
waiting for the cloud service provider. Today they been able to provide us with 
new virtual machines for the distribution, but not yet big enough disk space 
for the release data. As soon as we have the disk available, we can start 
transferring the release packages to it, test that everything works and put the 
system back online.

Yours,

Tuukka


From: Sze Howe Koh 
Date: Wednesday, 20. January 2021 at 16.09
To: Tuukka Turunen 
Cc: Qt Project Development 
Subject: Re: [Releasing] [Interest] download.qt.io is down
Thank you for clarifying, Tuukka.

I am (along with many others, I'm sure) delighted to hear about the
upcoming ability to officially select mirrors, and look forward to an
improved download experience going forward. MirrorBrain does not
always pick the best source. [1]

Best of luck with setting up an alternative file server.


Regards,
Sze-Howe

[1] https://lists.qt-project.org/pipermail/development/2018-April/032461.html


On Wed, 20 Jan 2021 at 18:35, Tuukka Turunen  wrote:
>
> Hi,
>
>
>
> To explain a bit why I was mistaken about the online in the mail I sent last 
> night. We have a development feature that allows selecting the mirror 
> manually. I thought it could be used, but it turned out we had not released 
> that version of the installer. Would have been handy, but since it is not 
> already released, the best approach is to re-create the master. We are doing 
> that now. We will also have this feature in the installer released (after we 
> can again make releases), because it is sometimes handy to tell explicitly 
> what server to download from.
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
> From: Development 
> Date: Wednesday, 20. January 2021 at 8.06
> To: Sze Howe Koh 
> Cc: development@qt-project.org , 
> releas...@qt-project.org , Interests Qt 
> 
> Subject: Re: [Development] [Releasing] [Interest] download.qt.io is down
>
> Hi,
>
>
>
> Yes, this is correct.
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
> From: Sze Howe Koh 
> Date: Wednesday, 20. January 2021 at 0.10
> To: Tuukka Turunen 
> Cc: Mark Long , development@qt-project.org 
> , Interests Qt , 
> releas...@qt-project.org 
> Subject: Re: [Releasing] [Interest] download.qt.io is down
>
> On Wed, 20 Jan 2021 at 04:10, Tuukka Turunen  wrote:
> >
> >
> > Hi,
> >
> > There are multiple mirrors, try for example:
> >
> >
> >
> > https://qt-mirror.dannhauer.de/
> >
> > https://www.funet.fi/pub/mirrors/download.qt-project.org/
> >
> > https://ftp.fau.de/qtproject/
> >
> >
> >
> > ...or just use the online installer, which picks mirrors automatically.
> >
> > Yours,
> >
> > Tuukka
>
> Hi Tuuka,
>
> The Online installer downloads files in 2 phases:
>
> 1. Retrieve metadata from download.qt.io
> 2. Retrieve actual binaries from the auto-selected mirror
>
> Since Step #1 is blocked, it can't proceed to Step #2.
>
>
> Regards,
> Sze-Howe
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Request to rename module qtscxml to qtstatemachine

[Ulf Hermann]

with Qt6 we removed the QtStateMachine implementation  from qtbase and 
moved it into qtscxml. While the name was ok when the module contained 
only SCXML releated code, it contains now both state machine 
implementations. Hence I would like to propose/request to rename the 
module to qtstatemachine to reflect the widened code base. Jira task: 
QTBUG-89837 


Indeed, that's a much better name. +1
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Request to rename module qtscxml to qtstatemachine

[Jaroslaw Kobus]

+1

The new name reflects the content of the module much better.

Regards

Jarek


From: Development  on behalf of Edward 
Welbourne 
Sent: Thursday, January 21, 2021 11:14 AM
To: Karsten Heimrich
Cc: development@qt-project.org
Subject: Re: [Development] Request to rename module qtscxml to qtstatemachine

Karsten Heimrich (21 January 2021 10:49) wrote:
> [...] I would like to propose/request to rename the module to
> qtstatemachine to reflect the widened code base. Jira task:
> QTBUG-89837

Sounds like a more accessible name to me - I'd have had to look up SCXML
to find out what it means, where the proposed name gives me a fairly
good clue to what it means.  So

+1

Eddy.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Repository request: qlitehtml

[Jaroslaw Kobus]

+1

This may be potentially easily reused in e.g. standalone assistant.

Jarek


From: Development  on behalf of Eike Ziller 

Sent: Tuesday, January 19, 2021 5:01 PM
To: development@qt-project.org
Subject: Re: [Development] Repository request: qlitehtml


> On Jan 19, 2021, at 16:30, Eike Ziller  wrote:
>
> Hi,
>
> I’d like to request a new repository on codereview.qt-project.org
>
> Name and description: qlitehtml - Lightweight HTML/CSS viewer for Qt, using 
> litehtml (https://github.com/litehtml/litehtml)
> Responsible person: Eike Ziller (eike.zil...@qt.io)
> Desired repository name: playground/qlitehtml
> URL of existing code:
>
> https://git.qt.io/eiziller/qlitehtml
>
> This is extracted from the code that so far lives within the Qt Creator 
> repository at 
> https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/help/qlitehtml
>  , with the goal of making it more easily shareable.

And the corresponding JIRA task here
https://bugreports.qt.io/browse/QTQAINFRA-4201

--
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Request to rename module qtscxml to qtstatemachine

[Lars Knoll]

> On 21 Jan 2021, at 11:14, Edward Welbourne  wrote:
> 
> Karsten Heimrich (21 January 2021 10:49) wrote:
>> [...] I would like to propose/request to rename the module to
>> qtstatemachine to reflect the widened code base. Jira task:
>> QTBUG-89837
> 
> Sounds like a more accessible name to me - I'd have had to look up SCXML
> to find out what it means, where the proposed name gives me a fairly
> good clue to what it means.  So
> 
> +1

Another +1.

Cheers,
Lars

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Request to rename module qtscxml to qtstatemachine

[Edward Welbourne]

Karsten Heimrich (21 January 2021 10:49) wrote:
> [...] I would like to propose/request to rename the module to
> qtstatemachine to reflect the widened code base. Jira task:
> QTBUG-89837

Sounds like a more accessible name to me - I'd have had to look up SCXML
to find out what it means, where the proposed name gives me a fairly
good clue to what it means.  So

+1

Eddy.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Request to rename module qtscxml to qtstatemachine

[Karsten Heimrich]

Hi,

with Qt6 we removed the QtStateMachine implementation  from qtbase and moved it 
into qtscxml. While the name was ok when the module contained only SCXML 
releated code, it contains now both state machine implementations. Hence I 
would like to propose/request to rename the module to qtstatemachine to reflect 
the widened code base. Jira task: 
QTBUG-89837

Are there any objections/ comments or suggestions?

-- Karsten
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development