All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Proposal for a Backport tracker
Date: Fri, 22 May 2015 10:32:09 +0200	[thread overview]
Message-ID: <555EE989.5070009@suse.cz> (raw)
In-Reply-To: <555ED98F.8020402@dachary.org>

> 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.

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.

Nathan

  reply	other threads:[~2015-05-22  8:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 11:24 Proposal for a Backport tracker Loic Dachary
2015-05-21 12:41 ` Nathan Cutler
2015-05-21 13:38   ` Abhishek L
2015-05-21 15:27     ` Loic Dachary
2015-05-21 15:21   ` Loic Dachary
2015-05-21 15:46     ` Sage Weil
2015-05-21 19:05       ` Loic Dachary
2015-05-22  7:06 ` Nathan Cutler
2015-05-22  7:23   ` Loic Dachary
2015-05-22  8:32     ` Nathan Cutler [this message]
2015-05-22 10:36       ` Joao Eduardo Luis
2015-05-22 10:50         ` Loic Dachary
2015-05-22 17:38           ` Sage Weil
2015-05-22 10:45       ` Loic Dachary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=555EE989.5070009@suse.cz \
    --to=ncutler@suse.cz \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.