From: Loic Dachary <loic@dachary.org>
To: Nathan Cutler <ncutler@suse.cz>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Proposal for a Backport tracker
Date: Fri, 22 May 2015 09:23:59 +0200 [thread overview]
Message-ID: <555ED98F.8020402@dachary.org> (raw)
In-Reply-To: <555ED569.2090604@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Hi Nathan,
On 22/05/2015 09:06, Nathan Cutler wrote:> Hi Loic:
>
> As I understand the new backport workflow, the process of creating tickets in the Backport tracker will be automated. This raises a question:
>
> As the automation script loops over each Pending Backport ticket, it will first create a corresponding ticket (or tickets) in the Backport tracker. After that, I'm thinking it will need to change the status of the original ticket from Pending Backport to something else (so it doesn't pick up the same ticket again the next time the script is run).
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 ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-05-22 7:24 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 [this message]
2015-05-22 8:32 ` Nathan Cutler
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=555ED98F.8020402@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ncutler@suse.cz \
/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.