Changes between Version 9 and Version 10 of Developer/Release


Ignore:
Timestamp:
May 14, 2015, 4:31:32 PM (4 years ago)
Author:
Gedare Bloom
Comment:

Fix the release branch and branch labels descriptions

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Release

    v9 v10  
    4343The RTEMS Release Number and Naming relates to all repositories and packages released. The version number has three (3) numbers and the numbers are `major.minor.release`.
    4444
    45  Major:: The ''major'' version number defines the ''release series''. A ''release series'' up to RTEMS 4 has traditionally reflected changes in the user ''Application Programming Interface'' (API) and has been slow moving. RTEMS Series 5 and higher uses the ''major'' number to better reflect major feature changes in '''RTEMS'''. '''RTEMS''' has shifted to support standards base interfaces for users and this means user API are stable and not changing.
     45 Major:: The ''major'' version number defines the ''release series''. A ''release series'' up to RTEMS 4 has traditionally reflected changes in the user ''Application Programming Interface'' (API) and has been slow moving. '''RTEMS''' has shifted to support standards base interfaces for users and this means user API are stable and not changing. Therefore, RTEMS Series 5 and higher uses the ''major'' number to better reflect major feature changes in '''RTEMS'''.
    4646
    47  Minor:: The ''minor'' version number changes for release branch created.
     47 Minor:: The ''minor'' version number changes when a release branch is created.
    4848
    49  Release:: The ''release'' version number change for release branch release created on a release branch after the branch has been created.
     49 Release:: The ''release'' version number changes for a release branch release, that is, when a release is created on that release branch. The first release version number is 0. This is sometimes called the dot release.
    5050
    5151=== RTEMS Branch Labels
    5252
    53 The '''RTEMS''' release branches are labelled with a prefix of `RTEMS_` followed by the major release number and minor release delimited with an underscore (`_`) and postfixed with `_BRANCH`. For example the release branch label for RTEMS 4.11 is `RTEMS_4_11_BRANCH`.
     53The '''RTEMS''' release branches are labelled by the major release number and minor release delimited with a period (`.`). For example the release branch label for RTEMS 4.11 is `4.11`.
    5454
    5555A development release is any code taken from the master branch of a repository.
     
    5959Release numbering for the Series 4 releases use the minor release dot number of ''.99'' for development releases. For example the development release numbering for RTEMS 4.11 is ''4.11.99''. This allows testing of any version number related code, processes and procedures to happen with correct minor version number.
    6060
    61 The release procedure requires the release's minor dot number to be set '0' before the release branch is created and it is used for the first branch release. Further branch releases increment the minor release number when a branch release is made.
     61The release procedure requires the release's minor dot number to be set to '0' before the release branch is created and it is used for the first branch release. Further branch releases increment the minor release number when a branch release is made.
    6262
    6363=== RTEMS Release 5 Series And Higher Numbering
    6464
    65 Release numbering for Series 5 and higher releases use even minor release numbers as development release and odd minor release number for releases. For example RTEMS 5.0 is a development release, that is any code taken from the master branch, and RTEMS 5.1 is an actual '''RTEMS''' release. The minor release dot number stays at ''0'' for all development releases.
     65Release numbering for Series 5 and higher releases use even minor release numbers as development releases and odd minor release numbers for releases. For example RTEMS 5.0 is a development release, that is any code taken from the master branch, and RTEMS 5.1 is an actual '''RTEMS''' release. The minor release dot number stays at ''0'' for all development releases.
    6666
    6767The release procedure requires the release's minor number is incremented to the next odd number then the release branch is created. The release minor dot number is incremented when a new release branch release is made.