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

[Chris Johns (@chris)]

Chris Johns commented on a discussion on eng/release-maintenance.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115908

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

A coupe of other things:

1. You can search MRs at the top group level for a milestone and target branch. You can use this to make sure you have things correct assigned. It is easy to get wrong so checking is a good thing.
2. Check the Gitlab quick actions for things to help speed up the process. For example there is a clone issue quick action. Please provide documentation updates on what works or post on discord. We are all learning how to use Gitlab.

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