Gedare Bloom commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/329#note_115885 Yes the issue should be duplicated with a milestone set to 7.1 and your commits/MR should close it instead. We have newly defined the procedures for how to manage backporting. We haven't quite gotten the instructions finished, but the procedure is mostly in place. The issues should be linked to an epic that is created to help monitor the backport. This gives us issues/MRs for release notes, and helps us centralize in the epics how we check which releases got backport fixes. https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/329#note_115885 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
