В Mon, 08 Apr 2024 22:36:56 -0500
Thiago Macieira пишет:
> On Monday 8 April 2024 17:17:04 CDT Ilya Fedin wrote:
> > 2. https://codereview.qt-project.org/c/qt/qtbase/+/444859 which is
> > 1.5 years old and no review
>
> Submitted during Christmas break and no changes since New Years. No
>
On Monday 8 April 2024 17:17:04 CDT Ilya Fedin wrote:
> 2. https://codereview.qt-project.org/c/qt/qtbase/+/444859 which is 1.5
> years old and no review
Submitted during Christmas break and no changes since New Years. No wonder it
was missed. You should have sent a "ping" during the second week
Hi,
I have no horse in these particular races, but I am going to throw my
2c in regardless:
In my opinion, 6 months or so delay on some reviews is fairly
acceptable (there can be higher-priority items which take attention,
it's understandable).
But beyond that, especially if the contributor is
I have multiple changes which hang for months and years which no idea
what to do to push them forward... I tried to write there asking for
review but reviewers seem to just ignore the messages...
1. The oldest change I have is
https://codereview.qt-project.org/c/qt/qtbase/+/343628 which is 3
On Monday 8 April 2024 09:57:55 CDT Volker Hilsheimer via Development wrote:
> - follow up on submodule updates and make necessary adjustments to Qt 3D to
> follow up on changes in other modules
> - decide if/how to “release” Qt 3D;
> branching and tagging and making it easy to build from source
I agree 100% with the sentiments below and in other emails to this list.
I'm not impacted by Qt3D, but as a user of Qt Widgets primarily, I'm starting
to worry that this too might get pulled or left to rot on the vine rather than
being extended and enhanced - we've put a lot of effort
The maintenance break is "over". We have a few loose threads to tie up
tomorrow, but things should eventually come up now that they have started.
With a lot of changes this time, we have to keep many eyes on the systems to
see that they work, but that's something for tomorrow.
Good luck with
Hi all,
I also want to backup these thoughts - even though our company has no cards in
the qt3d play, we had the same impact by being hit from abandoning QtWebKit
(in a minor release!!!) and QScriptEngine. Every product with a lifetime of
decades gets shaken in its foundations from such
Hi everyone,
Also a Qt3D user here, and I would like to echo Harald’s sentiments– and a big
thanks to Harald for saying my thoughts out loud.
I had already privately tried to communicate my thoughts to Tuukka on this
subject, but here is my public take…
As the Qt champion inside my
> On 13 Mar 2024, at 09:15, Eskil Abrahamsen Blomfeldt via Development
> wrote:
>
> Hi,
>
> I would like to nominate Hatem ElKharashy for maintainership of the Qt Svg
> module. This module currently does not have any active maintainer, but it has
> been part of my team's responsibility and
Gerrit is back online.
Main changes:
* version updated to 3.8.4
* Verified label taken into use. CI bots should use it instead of Code-Review
label
* Bug fix: Content of Integrating and Recently closed sections in Dashboard
will not mix anymore.
* CI queues are visible under CI Status
11 matches
Mail list logo
