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_113564

 > +
 > + - ``6.0.0`` is the version number of the development main for the 6 series
 > +
 > +Release Label
 > +^^^^^^^^^^^^^
 > +
 > +The release label is a string that cabn be used to provide context
 > +specific information about a release. The default value for the
 > +release label shall be ``not-released``.
 > +
 > +The release can set the release label by:
 > +
 > +#. A ``VERSION`` file that sets the release label.
 > +
 > +#. No ``VERSION`` file and the sources resides in a valid version
 > +   controlled repository. The release label shall be a version control

I valid version controlled repository is one where the commands and tools used to access a repository can access it and report its status. The language is attempting to be non-specific as well as handling implementation issues like a users `git` commands are stuffed and do not work. In that case the release label is the default (`not-released`).

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113564
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/602de2f0/attachment.htm>