[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

Hi all, I'll be going live today with these changes to the automatic cherry-pick processes. I'll be monitoring the systems for the next few days at least to catch any issues. If you experience any oddities or unexpected behavior, please contact me at daniel.sm...@qt.io directly with a report.

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