What to do with non backports targeting a stable branch

What to do with non backports targeting a stable branch

[Loic Dachary]

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

Hi,

Sorry Nathan, I went AFK before answering:

<smithfarm_nb> one more question: why did you change the tracker from Bug to Backport on http://tracker.ceph.com/issues/11542 ?
<smithfarm_nb> I'm guessing it was because there was only one backport target (firefly)
<smithfarm_nb> it seems to me that, according to http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_schedule_an_issue_for_backporting you should have copied the issue from Bug to Backport tracker
<smithfarm_nb> but if there is only one backport target this shortcut makes sense

We did not write anything related to this and maybe we should. In theory, for unification purposes, I should have created an issue, link it to the master PR https://github.com/ceph/ceph/pull/1768 and created an issue for the backport. It's overkill for just one commit, but ... that happens very rarely (maybe once a month ?). Therefore I think we can tolerate the overkill administrative overhead. I shouldn't have tried to be creative.

Here is the missing issue : http://tracker.ceph.com/issues/12467

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


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