> * a backport issue is created in the "Backport" tracker and is > "Related" to the original issue
Hi Loic: I like the idea of having backport tickets in a separate Redmine subproject/issue tracker. In fact, I would go even a step further and have separate subprojects for each target version (hammer backports, firefly backports). Having all, e.g. hammer, backports in one place is advantageous in pretty much every way I can think of: easier to see what has been done, what needs to be done, easier to search, easier to automate, less risk of munging something not related to backports... It also has the effect of removing all the backport-related tickets from the bug tracker(s). Nathan -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
