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: signature.asc
Description: OpenPGP digital signature

Reply via email to