Backports only to nautilus do not require tracker issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all, there seems to be some confusion concerning the backport tracker.

The purpose of the backport tracker is to track backports of fixes that need to
go into multiple stable branches, so they don't "fall through the cracks".

If you need to backport something from master *only* to nautilus *and no
farther*, there is no need to create tracker issues for backporting purposes.
Just open your nautilus PR with the cherry-pick [1].

(If there is already a master tracker issue, you can just mention the URL of the
nautilus backport in a comment on the tracker. You don't need to change the
status to Pending Backport or fill in the Backport field.)

Hope this helps,
Nathan

[1] of course, follow the cherry-picking rules
https://github.com/ceph/ceph/blob/master/SubmittingPatches-backports.rst#cherry-picking-rules

-- 
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx



[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux