All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Abhishek L <abhishek.lekshmanan@gmail.com>,
	Nathan Cutler <ncutler@suse.cz>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Proposal for a Backport tracker
Date: Thu, 21 May 2015 17:27:37 +0200	[thread overview]
Message-ID: <555DF969.4020405@dachary.org> (raw)
In-Reply-To: <87r3qa6of7.fsf@gmail.com>

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



On 21/05/2015 15:38, Abhishek L wrote:
> Hi
> 
> Nathan Cutler writes:
> 
>>> * 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).
> 
> Agree with the idea of seperate subproject. 

Another (I mean in addition to what I wrote in reply to Nathan) against subprojects is that existing custom queries would no longer display the backport issues. For instance http://tracker.ceph.com/projects/ceph/issues?query_id=47 is frequently used and does *not* display subprojects because Ceph is the parent project of all other projects and it would display all their issues. If there was a subproject for backports, it would not show. And if I'm not mistaken there is no way to say : "display issues from these subprojects and ignore the others". 

> Though I'm not having a
> strong opinion on whether subprojects are needed for each version;
> probably for issues which have multiple backports ie. backports to both
> firefly & hammer for instance it might be a little bit more bookkeeping,
> though from a maintainer standpoint; it is easier having a seperate
> subproject, so either way is okay. 
> 
>> 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...
>>
> 
> Agree, from a scripting standpoint, we could develop some tools to ease
> out the process better, which should it make it easier in backports down
> the line.
> 

I think we can do that by creating a tracker. It would be in addition to the Bug, Fix, Documentation etc. trackers that are already in place.

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


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

  reply	other threads:[~2015-05-21 15:27 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 [this message]
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=555DF969.4020405@dachary.org \
    --to=loic@dachary.org \
    --cc=abhishek.lekshmanan@gmail.com \
    --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.