Hi,
Since we often seem to struggle with populating the “What’s New” page in time
for the first packages:
As of https://codereview.qt-project.org/c/qt/qtdoc/+/417673 we now have a
whatsnew65.qdoc file in the qtdoc repo. You can add new features immediately
when got merged in the other
> Well, at least with qt positioning we need to handle all the cherry-picks to
> 5.15 manually
Which is probably fine for positioning, I don't expect there to be too many
patches getting
picked back. But for a given period I would say it's not unusual for half of the
patches going to Network to
On Mon, Jun 27, 2022 at 11:40:15AM +, Ivan Solovev wrote:
So, if we split network now, we will need to care about manually
picking to 6.4, 6.3, 6.2 and 5.15.
or just make the bot recognize a syntax like `qtbase(6.4 6.3 6.2 5.15)`?
fwiw, qtrepotools//bin/git-qt-cherry-pick should be
> If it can be done with little effort, including cherry-picking fixes
> backwards,
> even to 5.15, then it might be something to be investigated.
Well, at least with qt positioning we need to handle all the cherry-picks to
5.15 manually,
because the cherry-pick bot obviously does not detect
> On 26 Jun 2022, at 17:35, Thiago Macieira wrote:
>
> On Sunday, 26 June 2022 06:38:30 PDT Volker Hilsheimer wrote:
>> (*) As for the UNC stuff - it seems that we are testing only string parsing
>> code. We are not taking care of any of the actual network traffic or SMB
>> protocol. So do we
Hello!
While I don't necessarily object to splitting network out on a fundamental
level, I also find it to be questionable given the effort. If it can be done
with
little effort, including cherry-picking fixes backwards, even to 5.15, then
it might be something to be investigated.
Off the top
> On 26. Jun 2022, at 15:38, Volker Hilsheimer wrote:
>
> Whereas making sccache fault tolerant
I proposed a simple approach to get rid of sccache failures here
+1
Leena
Date: Mon, 27 Jun 2022 07:31:39 +
From: Topi Reini?
To: "Development@qt-project.org"
Subject: Re: [Development] Nominating Andreas Eliasson as Approver
Message-ID:
Content-Type: text/plain; charset="utf-8"
+1
Andreas has proved himself to be a valuable contributor
+1
Disclaimer: Colleague of mine.
From: Development on behalf of Kai Köhne
Sent: Friday, June 24, 2022 5:07 PM
To: development@qt-project.org
Subject: [Development] Nominating Andreas Eliasson as Approver
Hi,
I'd like to propose Andreas Eliasson as an Qt
+1
Andreas has proved himself to be a valuable contributor and reviewer of
documentation changes across multiple modules, I'm confident he'd be a good
approver.
Disclaimer: Andreas is a colleague of mine.
-Topi
--
Topi Reiniö, Principal Documentation Engineer | The Qt Company
10 matches
Mail list logo
