Chris Johns commented on a discussion on eng/release-process.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113557 > -N.2.0. > +A release number has the following fields separated by the dot (``.``) > +character: > > -The release branch will have the version number N.M.1 with M being the last > -minor release of this series. Tools will use N as the version number and > must > -be compatible with all releases and the release branch of the N series. > +``RTEMS_MAJOR`` > + The major version numnber. This number increments with each > + release. The value is updated after a release branch has been > + created. > + > +``RTEMS_MINOR`` > + 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 I have updated the sentence so I hope it is better. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113557 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
