[Development] Closing issues automatically with new keyword

[Jani Heikkinen]

>________________________________________
>From: Development <development-bounces+jani.heikkinen=qt.io at qt-project.org> on behalf of Frederik Gladhorn <frederik.gladhorn at qt.io>
>Sent: Tuesday, August 7, 2018 12:46 PM
>To: development at qt-project.org
>Subject: [Development] Closing issues automatically with new keyword
>
>Hi all,
>
>I've spend a bit of time writing a script that monitors gerrit and the git
>repositories to update JIRA statuses. It's not quite done yet, but getting
>there.
>Basically it should be able to set the fixed version and close tasks
>automatically.
>
>Assuming there is no major protest, I'll use "Fixes: QTBUG-123" as the keyword
>to trigger this.
>
>The plan is to update the fix versions and close the task as done when a line
>in the commit message starts with "Fixes:".
>If the issue is already closed (e.g. cherry-pick) it can add an additional fix
>version (e.g. 5.9.7).
>
>Note: Task-number will be used as before as "this is related to the issue in
>some way".
>
>Cheers,
>Frederik

Hi,

I see at least one problem there: If bug is affecting to several branches it will be closed when fix for first branch is done even in that case it shouldn't be closed until every branch has a fix...

Another concern or question is that in which phase we should close the bug; is it done immediately when fix is in or should it be done when fix is in the packages and someone can verify that fix is there and really fixes the problem... 

br,
Jani


_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development