Re: "Pending Backport" without "Backports" field

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

 



Hi,

There was a copy-paste issue - filled 'tags' field instead 'backport'. I was fix it now and backport tickets also created


k

> On 30 May 2022, at 11:01, Jan-Philipp Litza <jpl@xxxxxxxxx> wrote:
> 
> Hi everyone,
> 
> hope this is the right place to raise this issue.
> 
> I stumbled upon a tracker issue [1] that has been stuck in state
> "Pending Backport" for 11 months, without even a single backport issue
> created - unusually long in my (limited) experience.
> 
> Upon investigation, I found that according to the Tracker workflow [2],
> an issue that is pending backport should have its Backport field filled
> to be processed by the Backports team. This particular ticket doesn't
> have that field set. So presumably, that's why nobody created backport
> tickets.
> 
> A quick search turns up 24 other tickets [3] that are pending backport
> but didn't specify, whereto the backports should happen. Is there
> someone who could "sweep up" such tickets regularly? Or am I
> misunderstanding the process?

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux