All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Loic Dachary <loic@dachary.org>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Proposal for a Backport tracker
Date: Thu, 21 May 2015 14:41:41 +0200	[thread overview]
Message-ID: <555DD285.3050204@suse.cz> (raw)
In-Reply-To: <555DC080.8050508@dachary.org>

> * a backport issue is created in the "Backport" tracker and is 
> "Related" to the original issue

Hi Loic:

I like the idea of having backport tickets in a separate Redmine
subproject/issue tracker. In fact, I would go even a step further and
have separate subprojects for each target version (hammer backports,
firefly backports).

Having all, e.g. hammer, backports in one place is advantageous in
pretty much every way I can think of: easier to see what has been
done, what needs to be done, easier to search, easier to automate,
less risk of munging something not related to backports...

It also has the effect of removing all the backport-related tickets
from the bug tracker(s).

Nathan

  reply	other threads:[~2015-05-21 12:41 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 [this message]
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
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=555DD285.3050204@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.