[Development] New bot: LLM CI Failure Analysis

A couple months ago, I trialled a new proof-of-concept during a bugfix sprint to help reduce the investigation time required following failure of an integration in CI. This was met with a very good reception internally at TQtC, and so work continued to improve reliability-- The new CI Failure An

[Development] New keyword for Fixes bot "Reopens" and revert detection now live

Following feedback on the Reopens footer, it is now live an can be used in the commit message with the new behaviour: * Use Fixes normally to close an issue and as assign a fix version. * Use the Reopens footer to auto-reopen an issue when a change with the footer merges. For example, in

[Development] Introducing API Change Review Bot

Hi all, It's likely that you've already been introduced to QtAPIReviewBot, but in case you haven't, I think the Proof-of-Concept has settled enough to start a discussion about our API Review process which now includes this bot. In addition to the new bot commenting on changes, we still carry ou

[Development] RFC: New keyword for Fixes bot "Reopens" and revert detection

I'd like to open up a thread for discussion on the addition of a new commit message footer, "Reopens", related to Fixes/Task-Number. The proposed behaviour is: * Use of "Reopens: QTBUG1234" would trigger automatic reopening of the specified jira issue upon uploading a new change to codereview

[Development] Cherry-pick bot outage 08/09 April

Hi all, Yesterday and today, 08/09 April, there were a few brief cherry-pick bot outages which caused the bot to not receive events about merging changes. Root cause for this issue is was introduction of nonstandard branch naming in a repo, causing a crash in pickbot's pick-order logic. At thi

Re: [Development] HEADS-UP: Branching from 'dev' to '6.7' done

Hi, I've now run a post-branching script that will have cherry-pick bot warn you if you were targeting 6.6 for a Pick-to target from dev, but have not updated it to target 6.7 as well. Similarly, the bot has also removed +2 approvals from any dev change that does not already target 6.7. This i

Re: [Development] Changes to automatic cherry-picking

xists in a cherry-pick or the pick fails to integrate, so please try to take action on cherry-picks with issues ASAP. Best regards, -Daniel ____ From: Daniel Smith Sent: Friday, July 28, 2023 12:31 PM To: Tor Arne Vestbø Subject: Re: [Development] Changes to automa

Re: [Development] Changes to automatic cherry-picking

n for the subsequent cherry-picks. If you specify "Pick-to: 6.2 6.5 6.5.2", the bot will fill in 6.6 and 6.5.3 here and begin the waterfall process starting from 6.6. -Daniel From: Development on behalf of Daniel Smith via Development Sent: Monday, July

[Development] Changes to automatic cherry-picking

​**As a developer, you do not need to change how you use the "Pick-to:" footer.** You can stop reading here if you don't care too much about the details. ;) Over the past few years with the automatic cherry-picking, a common issue has emerged: lost and forgotten cherry-picks. When the cherry-pi

[Development] Jira Bot related email spam

Hi all, Earlier today, a new version of the Jira Bot was pushed to production with a bug that caused incorrect fix versions to be chosen for some issues since May 31. Unfortunately, the only way to correct this was to remove all fix versions on the affected issues and re-run the bot with the ho

[Development] Jira spam

Hi all, Sorry for the huge count of spam messages you may have received on some JIRA issues over the last day. This was due to a bug in a new Beta Jira bot which will more reliably guess fix versions when an issue is merged. The issue should now be resolved, and an improvement is being made to

Re: [Development] Orphaned Gerrit patchset

Ha, that’s amusing. Thankfully the change is irrelevant and isn’t actually consuming any CI resources. The change metadata appears to be corrupt as well so I have hard-deleted it. FYI, issues like this are better directed to gerrit-ad...@qt-project.org 😊 Tha

Re: [Development] Chief Maintainer election

The voting system is live at https://governancevoting.qt-project.org/voting and will open automatically at midnight on June 3. Voting is done by entering your codereview (gerrit) username and HTTP password (not your normal login password) which can be generated in your settings page here: https

Re: [Development] Using Git notes to reflect actual cherry-picks

This shouldn’t be too difficult to set up as a cron job on the gerrit server to run in all repos—I do agree with Tor Arne though that the notes should be namespaced if possible. Could you reupload the change to qt/qtqa/scripts/gerrit/cherrypick-git-notes ? -Daniel From: Development On Behalf

Re: [Development] Nominating David Skoland as approver

+1 From: Development On Behalf Of Morten Sørvig Sent: Thursday, April 21, 2022 2:01 PM To: development@qt-project.org Subject: [Development] Nominating David Skoland as approver I'd like to nominate David Skoland as approver for the Qt Project. David is employed by the Qt company has been cont

Re: [Development] requesting repository for qmake2cmake tool

This repo is now created and lives at https://codereview.qt-project.org/admin/repos/qt/qmake2cmake -Daniel -Original Message- From: Development On Behalf Of Jörg Bornemann Sent: Monday, March 7, 2022 1:44 PM To: Qt development mailing list Subject: [Development] requesting repository

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

+1! I also thought he had been an approver for quite some time. -Daniel -Original Message- From: Development On Behalf Of Volker Hilsheimer Sent: Wednesday, January 19, 2022 12:59 PM To: development@qt-project.org Subject: [Development] Nominating Dimitrios "Jimis" Apostolou as Approve

Re: [Development] QtPositioning and QtLocation split

Thanks for reporting the issues Thiago. Looks like the process for setting up the new repo wasn't fully completed. HEAD now points to dev correctly. Github mirror has been created and replicated. -Daniel From: Development On Behalf Of Ivan Solovev Sent: Thursday, October 28, 2021 9:49 AM To: M

Re: [Development] Formal voting procedure for Qt Project

something that can be considered as for future developments of the voting bot: On 04/10/21 13:08, Daniel Smith wrote: > If anyone wishes to verify that their personal vote has been recorded > correctly, they can email gerrit-ad...@qt-project.org to have an independent > party with database

Re: [Development] Formal voting procedure for Qt Project

The results of the voting bot are stored in a Heroku postgres database, to which only three or four people have access to at the moment, including myself. Logging from the bot and database records IP address, timestamps, usernames, and which general action the user took such as voting, updating

Re: [Development] Temporarily preventing changes being staged in the dev branch of qtquickcontrols2

> Can these cherry-picks be done automatically somehow? Is the manual process > the one we want / are stuck with? Unfortunately, I don't see how we can automate these cherry-picks, as the bot will have no viable way of identifying a change as part of the old qqc2 module. Further, in the event t

[Development] Cherry-picking model in testing on qt/qtquickcontrols2

e submit bug reports under QTQAINFRA. Be sure to tag all reports with "cherry-pick-bot" component so that they aren't missed. Daniel Smith The Qt Company, Oslo daniel.sm...@qt.io ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development