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_115906

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

It depends on your starting point. If you know you have to apply something to `main` and a release branch:

1. Create an epic
2. Add an issue to the epic for each branch being update
3. Set the milestone in each issue to the effected release version
4. Create MR for each branch and set the milestone referencing the appropriate issue

If you have an existing issue promote to be an epic and then follow steps 2 onward.

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