All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: "Shu, Xinxin" <xinxin.shu@intel.com>,
	Abhishek L <abhishek.lekshmanan@gmail.com>,
	Nathan Cutler <ncutler@suse.cz>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Backport tracker migration complete
Date: Fri, 22 May 2015 12:31:01 +0200	[thread overview]
Message-ID: <555F0565.6010704@dachary.org> (raw)
In-Reply-To: <555EEC40.3040106@dachary.org>

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



On 22/05/2015 10:43, Loic Dachary wrote:
> Hi,
> 
> The Backport tracker should now be fully populated. There are new custom queries for:
> 
>   hammer backports http://tracker.ceph.com/projects/ceph/issues?query_id=78
>   firefly backports http://tracker.ceph.com/projects/ceph/issues?query_id=79
> 
> and you can quickly see which one are assigned or not, scheduled for the next point release or not etc. 
> 
> To see all issues that are Pending Backport, the former queries still work:
> 
>   hammer http://tracker.ceph.com/projects/ceph/issues?query_id=77
>   firefly http://tracker.ceph.com/projects/ceph/issues?query_id=75
> 
> but you can now see links to the corresponding backports in the "Related issues" column. It makes it convenient to visually check which issues have been backported to all desired targets: there related issues are closed.
> 
> I'll update the documentation at http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO accordingly.
> 

The backporter manual has been updated at http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO and deserves proofreading. The most significant changes are at:

HOWTO schedule an issue for backporting http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_schedule_an_issue_for_backporting in which there now is the part where we need to create additional issues. It won't burden the developer but I think we'll get tired of it quickly and we'll need a snippet to do it for us ;-)

HOWTO backport commits http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_backport_commits changes very little: instead of adding a link to the pull request as a comment to the original issue, we set the URL as the description of the issue, in the same way we set the URL to the issue in the description of the pull request.

HOWTO resolve issues that are Pending Backport http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_resolve_issues_that_are_Pending_Backport is the step that benefits most from the change. It was tedious and is could now trivially be automated via a snippet.

> Cheers
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

      reply	other threads:[~2015-05-22 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  8:43 Backport tracker migration complete Loic Dachary
2015-05-22 10:31 ` Loic Dachary [this message]

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=555F0565.6010704@dachary.org \
    --to=loic@dachary.org \
    --cc=abhishek.lekshmanan@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ncutler@suse.cz \
    --cc=xinxin.shu@intel.com \
    /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.