Re: Proposal for a Backport tracker

[Loic Dachary <loic@dachary.org>]

[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]



On 22/05/2015 10:32, Nathan Cutler wrote:>> We can probably keep the original ticket in the "Pending Backport" status until all backports are resolved, as we currently do.
>>
>>> So the question is, what will the original ticket's status be changed to? Resolved?
>>
>> When all backports are resolved, then we can also resolve the original ticket. Do you forsee a problem with that ?
>>
> 
> Yes and no. It's a scripting problem, not a workflow problem. I'll try to describe the scenario I'm envisioning:
> 
> We have a simple script that loops over all tickets with status "Pending Backport". We run it once per week. The first week we run it, the script finds 3 such tickets. For each one it creates a ticket in the Backport tracker.
> 
> A week goes by, during which developers marked 4 more tickets "Pending Backport". It's time to run the script again. Since it is looping over all tickets marked "Pending Backport", it now finds 7 such tickets: 3 from last week and the 4 new ones. For each one it dutifully creates a new ticket in the Backport tracker. Now we have duplicate Backport tickets for 3 bugfixes.
> 
> But I guess it will be trivial to make the script check if a Backport ticket is already open and refrain from opening a new one in this case.

Yes, by investigating the "Related issues" and finding those that belong to the Backport tracker, we should be able to do that.

> 
> The same script could also check further: if Backport tickets already exist for the bugfix and all of them are marked Resolved, then automatically mark the original ticket Resolved as well.

Absolutely :-)

> 
> Nathan

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]