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

[Chris Johns (@chris)]

Chris Johns commented on a discussion on eng/release-process.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113563

 > + - ``6.1.0`` is the version number of the first RTEMS 6 release made
 > +   by the RTEMS project.
 >  
 > - - ``6.0.0`` is the version number of the development master for the 6 series
 > + - ``6.0.0.b45cf44489`` is a build of RTEMS without a ``VERSION`` file
 > +   and with the sources in a version controlled repository. The
 > +   identifer is the git commit hash.
 > +
 > + - ``6.0.0.b45cf44489-modified`` is the same build of source in the
 > +   previous example with a locally modified file.
 > +
 > + - ``6.3.0.rc1`` is the first release candidate from the second bug
 > +   fix release of RTEMS 6.
 > +
 > + - ``6.1.0.acme-corp`` is the vendor release from the fictional Acme
 > +   Corporation based on the RTEMS 6.1.0 release.

Yes a release label is a string and could be `joel-3.4.5.beta` creating a version string of `6.1.0-joel-3.4.5.beta` and for `rtems.git` it would be `6.1.0.joel-3.4.5.beta`.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113563
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/20241024/f2caafe3/attachment-0001.htm>