Documentation | eng: Update the release procedure (!62)

[Gedare Bloom (@gedare)]

Merge request https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62 was reviewed by Gedare Bloom

--
  
Gedare Bloom started a new discussion on eng/release-process.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113547

 > -be compatible with all releases and the release branch of the N series.
 > +``RTEMS_MAJOR``
 > +  The major version numnber. This number increments with each

typo: number

--
  
Gedare Bloom started a new discussion on eng/release-process.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113548

 > +  The minor version number is the branch release number and it
 > +  increments with each release made from a release branch. The minor
 > +  version number shall be ``0`` on all branches in the repository. The

This sentence seems wrong as the number should increment with each release made on that branch.

--
  
Gedare Bloom started a new discussion on eng/release-process.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113549

 > -  .. code-block:: none
 > +#. The release notes are generated from Issue and Merge Request data
 > +   in the RTEMS Project's Gitlab instance. A read only API key is need

s/need/needed


-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62
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/20241023/289e4dec/attachment.htm>