Documentation | Engineering Manual: Add release maintenance (!95)

[Sebastian Huber (@sebhub)]

Sebastian Huber started a new discussion on eng/release-maintenance.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115899

 > +   on more than one version of RTEMS. If the issue is for a single
 > +   version of RTEMS a single version label is required.
 > +
 > +Release Epics and Issues
 > +========================
 > +
 > +#. Management of an issue on more than one version of RTEMS shall use
 > +   an epic.
 > +
 > +#. A release branch epic is to be labelled ``backport``. This lets
 > +   us filter release branch epics.
 > +
 > +#. A release branch epic shall have a child issue for each version of
 > +   RTEMS it relates to. This includes the development branch
 > +   ``main``. Each issue shall have the milestone set to the verion of
 > +   RTEMS effected.

This is a bit abstract. It would be nice to have a step by step action list for what users and maintainers have to do for example to report and resolve an issue for RTEMS 7 and 6.1.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115899
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20241127/3902d96e/attachment-0001.htm>