-Original Message-
> From: Development project.org> On Behalf Of Shawn Rutledge
> https://bugreports.qt.io/issues/?filter=16028 currently has 169 bugs in that
> state. Having that many is an obstacle: I don’t suppose this week’s triage
> team
> is going to get through all of those and
> -Original Message-
> From: Development project.org> On Behalf Of André Pönitz
...
> A possible solution would be some automated state transition off "Need more
> info" once any comment had been added. At least that is a good first
> approximation that is more often right than wrong. And
Hi all,
I’ve been from time to time getting questions around Coin, and why we started
developing our own CI system for Qt instead of using some available solution.
To understand it, we will probably need to go back a few years to the time when
we started developing it. At that point in time, w
On Mon, 19 Nov 2018 20:00:30 +, Volker Hilsheimer wrote:
> I understand that the “need more info” -> auto-closing bot workflow is
> to some degree a bit of a probe to see if someone still cares.
A bug is a bug and if the one who has reported it has lost the interest
in it months/years later
On Mon, 19 Nov 2018 at 22:41, Thiago Macieira wrote:
>
> On Monday, 19 November 2018 12:03:06 PST Ville Voutilainen wrote:
> > I personally tend to split such things after an opening parenthesis.
> > Getting back to allowing ctor-initializers to be written
> > with a comma starting a line, I think
On Monday, 19 November 2018 12:41:46 PST Thiago Macieira wrote:
> It is allowed, unless the maintainer objects to it.
>
> I object to it in QtCore.
I also insist that the opening brace in non-nested classes, enums and in any
functions be placed in a new line (unless the entire function is in one
On Monday, 19 November 2018 11:42:48 PST Lisandro Damián Nicanor Pérez Meyer
wrote:
> b) If at some point we can agree it has been decided, is there any way I
> could start contributing code in order to achieve this? Maybe I should just
> wait until the new build system is on stage? something else
On Monday, 19 November 2018 12:03:06 PST Ville Voutilainen wrote:
> I personally tend to split such things after an opening parenthesis.
> Getting back to allowing ctor-initializers to be written
> with a comma starting a line, I think we should just allow it; the
> benefit of not having noise in a
On Monday, 19 November 2018 12:06:30 PST Volker Hilsheimer wrote:
> > On 17 Nov 2018, at 22:18, Thiago Macieira
> > wrote:
> > On Saturday, 17 November 2018 12:58:10 PST Bernhard Lindner wrote:
> >
> >> Hi everybody!
> >>
> >> Are there any plans for Qt6' API to use standard types like size_t
> On 17 Nov 2018, at 22:18, Thiago Macieira wrote:
>
> On Saturday, 17 November 2018 12:58:10 PST Bernhard Lindner wrote:
>> Hi everybody!
>>
>> Are there any plans for Qt6' API to use standard types like size_t (or
>> special replacements like qsizetype) for return values and parameters that
>>
On Mon, 19 Nov 2018 at 18:37, Thiago Macieira wrote:
>
> On Monday, 19 November 2018 02:34:09 PST Edward Welbourne wrote:
> > I note a glaring exception to that: after the opening parenthesis of
> > a parameter list, if the line would otherwise be too long:
> >
> > auto variable =
> > QCharacter
> On 19 Nov 2018, at 16:09, Uwe Rathmann wrote:
> I guess my bugs are not the only ones and if you don't want to lose a lot
> of valuable reports this way better stop an revert this bulk changes.
I understand that the “need more info” -> auto-closing bot workflow is to some
degree a bit of a p
El martes, 13 de noviembre de 2018 23:58:28 -03 Thiago Macieira escribió:
> On Tuesday, 13 November 2018 18:43:03 PST Kevin Kofler wrote:
[snip]
> > I think it would be much safer to just version everything.
> >
> > Just remember Assistant in Qt 4, where early 4.x releases shipped an
> > Assistan
On Mon, Nov 19, 2018 at 04:36:45PM +, Shawn Rutledge wrote:
> [...]
> I suspect the reason people don’t hit that button is that it’s at the
> top, whereas when you add a normal comment, you press the comment
> button at the bottom. And if you are actually answering the question
> with your com
On Mon, 19 Nov 2018 16:01:32 +
Kai Koehne wrote:
> > -Original Message-
> > From: Development > project.org> On Behalf Of Uwe Rathmann
> > Sent: Monday, November 19, 2018 4:10 PM
> > To: development@qt-project.org
> > Subject: [Development] automated bulk change closing old issues
On Mon, 19 Nov 2018 16:36:45 +, Shawn Rutledge wrote:
> Also, every week we have a team of 2 people triaging bugs. Part of that
> job is to check all the bugs that are in “need more info” state, and
> decide whether the info is now sufficient.
In the case of my bugs: in one of them it is tot
Den mån 19 nov. 2018 kl 17:36 skrev Shawn Rutledge :
>
>
> > On 19 Nov 2018, at 16:09, Uwe Rathmann wrote:
> >
> > Hi all,
> >
> > I just received 2 messages about: automated bulk change closing old
> > issues in the "Need more info" state.
> >
> > - https://bugreports.qt.io/browse/QTBUG-68874
> >
On Monday, 19 November 2018 02:34:09 PST Edward Welbourne wrote:
> I note a glaring exception to that: after the opening parenthesis of
> a parameter list, if the line would otherwise be too long:
>
> auto variable =
> QCharacteristicallyVerboseClassName::characteristicallyLongFunctionName(
> fi
> On 19 Nov 2018, at 16:09, Uwe Rathmann wrote:
>
> Hi all,
>
> I just received 2 messages about: automated bulk change closing old
> issues in the "Need more info" state.
>
> - https://bugreports.qt.io/browse/QTBUG-68874
> - https://bugreports.qt.io/browse/QTBUG-66264
>
> I have no idea why
> -Original Message-
> From: Development project.org> On Behalf Of Uwe Rathmann
> Sent: Monday, November 19, 2018 4:10 PM
> To: development@qt-project.org
> Subject: [Development] automated bulk change closing old issues in the "Need
> more info" state
>
> Hi all,
>
> I just received 2 m
Hi all,
I just received 2 messages about: automated bulk change closing old
issues in the "Need more info" state.
- https://bugreports.qt.io/browse/QTBUG-68874
- https://bugreports.qt.io/browse/QTBUG-66264
I have no idea why they have been set to "Need more info" - actually one
of them has bee
On Sunday, 18 November 2018 05:30:26 PST Sze Howe Koh wrote:
>> I'd just like to know: Did the Qt Project ever reach a decision? If not,
>> how can we reach one?
(Linked to the discussion of constructor initializers like
MyClass(type param)
: MyBase(param)
, myMember(param)
using comma
22 matches
Mail list logo
