Some food for thought for module maintainers.
Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
those issues had that priority set more than one year ago, 342 of those had
their priority set more than two years ago, and 175 of those more than
three years ago.
If an issue
On Tue, 3 Nov 2020 at 06:00, Oswald Buddenhagen
wrote:
> On Tue, Nov 03, 2020 at 12:00:27AM +1000, Jason McDonald wrote:
> >Is there some obscure reason behind the duplicate resolution or is it a
> >mistake as I suspect?
> >
> certainly a mistake.
>
> note that "Fixed" is redundant with "Done", a
On Tue, 3 Nov 2020 at 05:48, Oswald Buddenhagen
wrote:
> On Mon, Nov 02, 2020 at 08:01:13AM -0800, Thiago Macieira wrote:
> >On Monday, 2 November 2020 05:24:45 PST Jason McDonald wrote:
> >> There may be such a tool, but if there is it presumably isn't
> functioning
> >> anymore (unless it's def
> On 2 Nov 2020, at 20:03, Oswald Buddenhagen wrote:
>
> On Mon, Nov 02, 2020 at 10:26:31AM +, Shawn Rutledge wrote:
>> [stuff about changelogs]
>
> for completeness:
>
> some of your points re-iterate what has already been said in
> https://bugreports.qt.io/browse/QTQAINFRA-1960 (which p
On 2 Nov 2020, at 16:59, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
On Monday, 2 November 2020 02:26:31 PST Shawn Rutledge wrote:
So in practice, changelogs still require manual editing. Probably there is
someone who knows just what settings to use in just what editor to make it
On Tue, Nov 03, 2020 at 12:00:27AM +1000, Jason McDonald wrote:
Is there some obscure reason behind the duplicate resolution or is it a
mistake as I suspect?
certainly a mistake.
note that "Fixed" is redundant with "Done", and was introduced as an
unintended side effect of migrating issues fr
On Mon, Nov 02, 2020 at 08:01:13AM -0800, Thiago Macieira wrote:
On Monday, 2 November 2020 05:24:45 PST Jason McDonald wrote:
There may be such a tool, but if there is it presumably isn't functioning
anymore (unless it's definition of "too long" is more than two years).
I think it was suppose
Heads up,
As per https://codereview.qt-project.org/c/qt/qtbase/+/318749, the configure
script in qtbase (and thus qt5.git) will default to configuring Qt with CMake.
To configure Qt with qmake, pass -qmake
Cheers,
Volker
___
Development mailing li
On Mon, Nov 02, 2020 at 10:26:31AM +, Shawn Rutledge wrote:
[stuff about changelogs]
for completeness:
some of your points re-iterate what has already been said in
https://bugreports.qt.io/browse/QTQAINFRA-1960 (which presumably needs a
revision for the now used go program).
and the bi
On Monday, 2 November 2020 06:21:49 PST Shawn Rutledge wrote:
> Sorry for snipping so much, but it seems like all your arguments are about
> tools that are used to build software (qmake, moc etc.). And you have a
> point there.
> But I don’t see the point of renaming user-facing tools like assis
On Monday, 2 November 2020 06:15:57 PST David Jackson wrote:
> The Qt API needs a QTimer with nanosecond accuracy. I know what is actually
> provided by underlying platforms varies greatly. But instead of Qt
> introducing its own limitation, Qt needs to provide a way for what the
> underlying platf
On Monday, 2 November 2020 05:24:45 PST Jason McDonald wrote:
> There may be such a tool, but if there is it presumably isn't functioning
> anymore (unless it's definition of "too long" is more than two years).
I think it was supposed to be run manually every 6 months or so, closing
entries that
On Monday, 2 November 2020 02:26:31 PST Shawn Rutledge wrote:
> So in practice, changelogs still require manual editing. Probably there is
> someone who knows just what settings to use in just what editor to make it
> effortless, but for me it always involves a lot of tedious manual spacing,
> bec
On Monday, 2 November 2020 05:07:35 PST Lars Knoll wrote:
> I honestly don't think renaming all our binaries is an option, certainly not
> that late in the process. We’ve had Qt 4 and Qt 5 co-installed for a long
> time as well and while that might not be perfect it was working.
>
> And qtchooser
Hello!
Maybe QDeadlineTimer and QElapsedTimer covers your needs?
https://doc.qt.io/qt-5/qdeadlinetimer.html
https://doc.qt.io/qt-5/qelapsedtimer.html
Mårten
From: Development on behalf of David
Jackson
Sent: Monday, November 2, 2020 15:15
To: developm
> On 1 Nov 2020, at 01:19, Kevin Kofler via Development
> wrote:
>
> Really, it is this whole concept of the user choosing a version of Qt that
> is flawed. The right place to make this choice is the build system of the
> software using Qt.
Sorry for snipping so much, but it seems like all y
The Qt API needs a QTimer with nanosecond accuracy. I know what is actually
provided by underlying platforms varies greatly. But instead of Qt
introducing its own limitation, Qt needs to provide a way for what the
underlying platform can support to be accessed. If a platform does not
support nanose
Another oddity I can see in Jira is that there are currently 103 open
issues in components that are marked as "inactive" and "archived". Should
such issues be closed as "Won't Do" or is there a valid reason to keep them
open?
The relevant issues can be found with the following Jira query:
pro
Hi Giuseppe,
I agree that the current situation is somewhat complicated. But the approach
piloted at https://www.qt.io/blog/qt-6-additional-libraries-via-package-manager
hopefully will help to tell a more aligned story in the future, at the price of
(temporarily) adding yet another way of getti
It appears that on 29 March 2016 a custom "Unresolved" resolution was added
beside the built-in default. This might be causing some unresolved issues
to be hidden from queries.
I discovered the duplicate resolution when Jira's query auto-completer
showed me two Unresolved resolutions, one with do
On Mon, 2 Nov 2020 at 23:19, Lars Knoll wrote:
> Hi Jason,
>
> Welcome back!
>
> > On 2 Nov 2020, at 14:11, Jason McDonald wrote:
> >
> > While reacquainting myself with the Qt Bug Tracker after a long absence,
> I noticed that there are more than 900 issues languishing in the Needs More
> Info
Hi Jason,
Welcome back!
> On 2 Nov 2020, at 14:11, Jason McDonald wrote:
>
> While reacquainting myself with the Qt Bug Tracker after a long absence, I
> noticed that there are more than 900 issues languishing in the Needs More
> Info state. Digging a bit deeper, it appears that in mid-2018
While reacquainting myself with the Qt Bug Tracker after a long absence, I
noticed that there are more than 900 issues languishing in the Needs More
Info state. Digging a bit deeper, it appears that in mid-2018, whomever
was shepherding Needs More Info bugs stopped doing so and since then a
steady
I honestly don't think renaming all our binaries is an option, certainly not
that late in the process. We’ve had Qt 4 and Qt 5 co-installed for a long time
as well and while that might not be perfect it was working.
And qtchooser has been working nicely for me (Ubuntu at least uses it).
Cheers,
Just as a note we are using markdown for Qt Creator changelogs since a long
time too.
With the “right” heading styles it is also nicely readable in ASCII.
You can actually use ### as the third level of headings without compromising
readablility.
https://code.qt.io/cgit/qt-creator/qt-creator.git/
25 matches
Mail list logo
