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

[Sebastian Huber (@sebhub)]

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

 > +   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.

I fully understand the not having time issue. Without a step by step procedure it is quite difficult for me to figure out what to do. I guess users are in a similar situation. It is unlikely that they even read this stuff. They will probably just open an issue and leave the rest to the maintainers.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115905
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/e1591ca1/attachment.htm>