Opened on 08/13/20 at 03:12:13
Last modified on 11/29/22 at 23:08:40
#4050 new defect
Change verson details to be version.revision
Reported by: | Chris Johns | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 7.1 |
Component: | build | Version: | 7 |
Severity: | blocker | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
The RTEMS version code expects major.minor.revision
to support __RTEMS_MAJOR__
, __RTEMS_MINOR__
, and __RTEMS_REVISION__
. These labels are now misleading as they do not match the version numbering we have. RTEMS's version number is version.revision
.
Change History (2)
comment:1 Changed on 12/21/21 at 15:12:41 by Joel Sherrill
comment:2 Changed on 11/29/22 at 23:08:40 by Chris Johns
Milestone: | 6.1 → 7.1 |
---|---|
Version: | 6 → 7 |
Across the RTEMS code base and ecosystem we need to make the versioning consistent. At the moment is it not.
Do we keep major.minor.revision
with revision
always 0
and the leave things as they are or do we change it? There needs to be a policy established first.
Is this better handled in 7?
Note: See
TracTickets for help on using
tickets.
What specifically is "RTEMS version code" and where is it all? What needs fixing?