paweld/lazarus
1
0
Fork 0
mirror of https://gitlab.com/freepascal.org/lazarus/lazarus.git synced 2025-04-09 04:07:57 +02:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Fine tunes wording in version number topics.

Browse Source
This commit is contained in:
dsiders 2023-06-27 17:55:42 +01:00
parent f1aae18d4e
commit 50764d5fdf
2 changed files with 30 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
docs/xml/lazutils/lazversion.xml
View File

@ -24,13 +24,20 @@ significant. The release number will always be 0 (zero) starting with version
3.0.
</p>
<p>
In addition, an odd minor version number no longer indicates that it is a
development (or trunk) version. Instead, odd minor version numbers like 3.1 or
3.3 represent fixes releases. For example: 3.1 would contain bug fixes for the
3.0 release and would be used as the basis for the 3.2 release. Development
(or trunk) versions are always represented as minor version number 99; i.e.
3.99 is the development branch for future releases such as fixes in the 3.X
family and the future 4.0 release.
An even minor version number, like 3.0 or 3.2, represents a general
availability release. An odd minor version number no longer indicates that it
is a development (or trunk) version. Instead, an odd minor version number
like 3.1 or 3.3 represents a fixes branch. For example: 3.1 would contain bug
fixes for the 3.0 release and would be used as the basis for the 3.2
release. Development (or trunk) versions are always represented as minor
version number 99; i.e. 3.99 is the development branch for the future 4.0
release. Also, selected commits from this branch are cherry picked to the 3.X
family.
</p>
<p>
Patch numbers identify a release candidate or a general availability release.
For example: 3.0.0 RC1 has the the full version value of 3.0.0.1. RC2 has the
value 3.0.0.2, and the released product could be 3.0.0.3.
</p>
<p>
<file>lazversion.pas</file> is part of the <file>lazutils</file> package.
@ -76,13 +83,14 @@ For the Lazarus version number 2.3.0.42, the value in laz_minor is 3.
<p>
<b>Please note:</b> Starting with Lazarus version 3.0, laz_minor is
incremented by 1 for each new release or fixes branch. For example: 3.0, 3.1,
3.2, etc. In addition, an odd minor version number no longer
indicates that it is a development (or trunk) version. Instead, odd minor
version numbers like 3.1 or 3.3 are fixes releases. For example: 3.1
would contain bug fixes for the 3.0 release and would be used as the basis for
the 3.2 release. Development (or trunk) versions are always represented as
minor version number 99; i.e. 3.99 is the development branch for future
releases such as fixes in the 3.X family and the future 4.0 release.
3.2, etc. An even minor version number, like 3.0 or 3.2, represents a general
availability release. An odd minor version number no longer indicates that it
is a development (or trunk) version. Instead, an odd minor version number
like 3.1 or 3.3 represents a fixes branch. For example: 3.1 would contain bug
fixes for the 3.0 release and would be used as the basis for the 3.2 release.
Development (or trunk) versions are always represented as minor version number
99; i.e. 3.99 is the development branch for the future 4.0 release. Also,
selected commits from this branch are cherry picked to the 3.X family.
</p>
</descr>
<seealso/>

15
docs/xml/lcl/lclversion.xml
View File

@ -57,14 +57,15 @@ contains the second number (2).
</p>
<p>
<b>Please note:</b> Starting with LCL version 3.0, lcl_minor is incremented by
1 for each new release or fixes branch. For example: 3.0, 3.1, 3.2, etc. In
addition, an odd minor version number no longer indicates that it is a
development (or trunk) version. Instead, odd minor version numbers like 3.1 or
3.3 represent a fixes release. For example: 3.1 would contain bug fixes for
the 3.0 release and would be used as the basis for the 3.2 release.
1 for each new release or fixes branch. For example: 3.0, 3.1, 3.2, etc. An
even minor version number, like 3.0 or 3.2, represents a general availability
release. An odd minor version number no longer indicates that it is a
development (or trunk) version. Instead, an odd minor version number like 3.1
or 3.3 represents a fixes branch. For example: 3.1 would contain bug fixes
for the 3.0 release and would be used as the basis for the 3.2 release.
Development (or trunk) versions are always represented as minor version number
99; i.e. 3.99 is the development branch for future releases such as fixes in
the 3.X family and the future 4.0 release.
99; i.e. 3.99 is the development branch for the future 4.0 release. Also,
selected commits from this branch are cherry picked to the 3.X family.
</p>
</descr>
<seealso>lcl_version</seealso>