Re: Documentation | Engineering Manual: Add release maintenance (!95)
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. ___ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
Re: Documentation | Engineering Manual: Add release maintenance (!95)
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. ___ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
Re: Documentation | Engineering Manual: Add release maintenance (!95)
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. ___ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
Re: Documentation | Engineering Manual: Add release maintenance (!95)
Chris Johns commented on a discussion on eng/release-maintenance.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115904 > + 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. The first step is define what is required. I would welcome a step-by-step process but I do not currently have the time to do this. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115904 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
Re: Documentation | Engineering Manual: Add release maintenance (!95)
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. ___ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
Re: Documentation | Engineering Manual: Add release maintenance (!95)
Merge request !95 was merged Merge request URL: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 Project:Branches: chris/rtems-docs:eng-release-maintenance to rtems/docs/rtems-docs:main Author: Chris Johns Assignee: Chris Johns Reviewer: Gedare Bloom -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 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
Re: Documentation | Engineering Manual: Add release maintenance (!95)
Gedare Bloom commented: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115879 This is consistent with my thinking. We'll need to add a bit more instruction to it (HOWTO) but overall I like the definition of the policy. It seems to be clear enough to move it forward. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95#note_115879 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
Re: Documentation | Engineering Manual: Add release maintenance (!95)
Gedare Bloom pushed new commits to merge request !95 Merge request URL: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 * 3668e367 - eng: fix typos in release-maintenance.rst -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 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
Re: Documentation | Engineering Manual: Add release maintenance (!95)
Gedare Bloom was added as a reviewer. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 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
Re: Documentation | Engineering Manual: Add release maintenance (!95)
Chris Johns pushed new commits to merge request !95 Merge request URL: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 * bc697d9f - 1 commit from branch `main` * a8755300 - eng: Add release maintenance -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 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
Re: Documentation | Engineering Manual: Add release maintenance (!95)
Reassigned merge request 95 https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 Chris Johns was added as an assignee. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/95 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
