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

Docs: LCL, LazUtils. Corrects language in minor version number topics.

Browse Source
This commit is contained in:
dsiders 2023-06-26 15:43:44 +01:00
parent 946040a582
commit 414a258750
2 changed files with 21 additions and 19 deletions
docs/xml
lazutils
lazversion.xml
lcl
lclversion.xml

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

@ -24,12 +24,13 @@ significant. The release number will always be 0 (zero) starting with version
3.0.
</p>
<p>
In addition, an odd minor version numbers no longer indicate that it is a
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 branch. For example: 3.1 would contain bug fixes for the
3.0 branch and would be used as the basis for the first 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 version 3.X family.
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.
</p>
<p>
<file>lazversion.pas</file> is part of the <file>lazutils</file> package.
@ -75,13 +76,13 @@ 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, ad infinitum. In addition, an odd minor version number no longer
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 branch. For example: 3.1
would contain bug fixes for the 3.0 branch and would be used as the basis for
the first 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 version
3.X family.
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.
</p>
</descr>
<seealso/>
@ -104,7 +105,7 @@ For the Lazarus version number 2.3.0.42, the value in laz_release is 0.
<p>
<b>Please note:</b> Starting with Lazarus 3.0, the release number is no longer
used and will always contain 0 (zero). Releases are represented using the
major and minor version numbers: 3.0, 3.1, 3.2, ad infinitum.
major and minor version numbers: 3.0, 3.1, 3.2, etc.
</p>
</descr>
<seealso/>

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

@ -57,13 +57,14 @@ 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, ad
infinitum. In addition, odd minor version numbers no longer indicate that it
is a development (or trunk) version. Instead, odd minor version numbers like
3.1 or 3.3 represent a fixes branch. For example: 3.1 would contain bug fixes
for the 3.0 branch and would be used as the basis for the first 3.2 release.
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.
Development (or trunk) versions are always represented as minor version number
99; i.e. 3.99 is the development branch for the version 3.X family.
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.
</p>
</descr>
<seealso>lcl_version</seealso>
@ -79,7 +80,7 @@ contains the third number (4).
<p>
<b>Please note:</b> Starting with LCL 3.0, the release number is no longer
used and will always contain 0 (zero). Releases are represented using the
major and minor version numbers: 3.0, 3.1, 3.2, ad infinitum.
major and minor version numbers: 3.0, 3.1, 3.2, etc.
</p>
</descr>
<seealso>lcl_version</seealso>