Difference between revisions of "ChangeSetsUpdated"

From GNU Radio
Jump to navigation Jump to search
Line 11: Line 11:
* MINOR version changes indicate new functionality, but maintain backward compatibility.
* MINOR version changes indicate new functionality, but maintain backward compatibility.
* PATCH version changes result in no externally visible changes (except bug fixes).
* PATCH version changes result in no externally visible changes (except bug fixes).
TBD: API could be referred to as MAJOR, since it implies more than just a library API version.


== For 3.8 ==
== For 3.8 ==

Revision as of 12:11, 26 February 2021

This content is a Work In Progress


Version Numbering

GNU Radio follows the Semantic Versioning specification. Version numbers are of the form API.MINOR.PATCH. These numbers communicate to external developers, packagers and users what level of change to expect when using a new version. Quick summary:

  • API version changes mean that developers and/or users may need to make modifications to their code/project.
  • MINOR version changes indicate new functionality, but maintain backward compatibility.
  • PATCH version changes result in no externally visible changes (except bug fixes).

TBD: API could be referred to as MAJOR, since it implies more than just a library API version.

For 3.8

GNU Radio previously used a four-number A.B.C.D system. A.B represented API (A has not changed for many years). D has not been incremented from 0 in 3.8. Version 3.8.2.0 is equivalent to (3.8).2.0.

In development versions (the next API), APIs and functionality may change at any time. Users of these versions are typically developers who accept this risk in order to take advantage of new functionality.

Maintenance Releases

The current and previous API releases will be maintained by the GNU Radio project. This does not preclude updates to previous versions.