No "Backport" tracker for Orchestrator project?

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

 



Sebastian,

I tried to run the backport-create-issue script:

$ python3 src/script/backport-create-issue 44826
WARNING:root:Missing issues will be created in Backport tracker of the
relevant Redmine project
INFO:root:Redmine key was read from '~/.redmine_key'; using it
INFO:root:Processing issue list ->44826<-
INFO:root:Processing 1 issues with status Pending Backport
INFO:root:https://tracker.ceph.com/issues/44826 skipped because the
project Orchestrator does not have a Backport tracker
INFO:root:Processed 1 issues

and got the above error. It seems batch backports are being done
instead [1] manually. I couldn't find an explanation for this policy
in the email archives. Why is the orchestrator being treated
differently from the rest of the Ceph project?

[1] https://github.com/ceph/ceph/pull/34438

-- 
Patrick Donnelly, Ph.D.
He / Him / His
Senior Software Engineer
Red Hat Sunnyvale, CA
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
_______________________________________________
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