Changeset 50a8353 in rtems


Ignore:
Timestamp:
May 26, 2021, 7:39:13 AM (4 months ago)
Author:
Christian Mauderer <christian.mauderer@…>
Branches:
5
Children:
8d4382b
Parents:
06427c8d
git-author:
Christian Mauderer <christian.mauderer@…> (05/26/21 07:39:13)
git-committer:
Christian Mauderer <christian.mauderer@…> (05/28/21 06:24:05)
Message:

cpukit: Add description of release version numbers

The release version in the git sources doesn't change. Add a note why
that is the case.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • cpukit/include/rtems/version.h

    r06427c8d r50a8353  
    3030 * @brief The Version API provides functions to return the version or parts of
    3131 * the version of RTEMS you are using.
     32 *
     33 * A branch in the version control system will always fall back to a
     34 * NOT-RELEASED version number with a minor number of 0. Only the release
     35 * archives have a VERSION file with a final release number. That means for
     36 * example that the 5 development branch will still show a version 5.0.0 even
     37 * after the 5.1 release.
     38 *
     39 * The reason for that are the following:
     40 *
     41 * 1. All pre-release tests are performed with a specific git hash. A committed
     42 * VERSION file would need to be changed and committed afterwards for releasing
     43 * with the required release version causing the released version to have a
     44 * different git hash and the test results couldn't be linked to the released
     45 * version.
     46 *
     47 * 2. Users deploying RTEMS would need to commit a local change to a committed
     48 * VERSION file and that would clash with the project changes. Deployment can
     49 * use the project repos directly.
     50 *
     51 * 3. The VERSION file management and generation is the responsibility of the
     52 * release manager and the release process.
    3253 */
    3354/**@{**/
Note: See TracChangeset for help on using the changeset viewer.