Release naming - Revision history

Tintinux: Text replacement - "{{#CustomTitle:" to "{{DISPLAYTITLE:"

2020-02-11T17:17:20Z

Text replacement - "{{#CustomTitle:" to "{{DISPLAYTITLE:"

Tintinux: /* Release candidates */

2019-12-11T08:39:14Z

Release candidates

Tintinux: /* Beta versions */

2019-12-11T08:38:19Z

Beta versions

Tintinux: /* Alpha versions */

2017-03-13T14:28:43Z

Alpha versions

Tintinux: /* Alpha versions */

2017-03-13T14:27:57Z

Alpha versions

Tintinux: /* Numbering */

2017-03-13T14:24:45Z

Numbering

Gastounet at 12:20, 20 November 2015

2015-11-20T12:20:53Z

Gastounet: Created page with "{{#CustomTitle:Naming and numbering of Gestinux versions}} = Numbering = We use only 2 digits, then a reliability level, and finally possibly a sequential number. Example :..."

2015-11-20T12:10:41Z

Created page with "{{#CustomTitle:Naming and numbering of Gestinux versions}} = Numbering = We use only 2 digits, then a reliability level, and finally possibly a sequential number. Example :..."

New page

{{#CustomTitle:Naming and numbering of Gestinux versions}}

= Numbering =

We use only 2 digits, then a reliability level, and finally possibly a sequential number.

Example :

* 1.2-Stable
* 1.1-Stable-1
* 1.2-Beta-2
* 1.2-Release-candidate-1
* 1.4-Alpha-1

In alpha versions, the last digit changes at least every time the structure of the database changes only after creation or modification of a table, a field, a constraint or any other object. In other versions, it changes in these cases and also every time a package of installation is published on SourceForge.

= Reliability level =

== Alpha versions ==

Versions in development, not finished, which can contain several severe bugs and possibly destroy datas.

They are still build with sources contained in the trunk branch. No binary installer will be uploaded on SourceForge for these versions.

Never use them for real management, only on a copy of a test database.

You can indicate anomalies, if you are developer and verified that the corresponding sources have not just been archived.

== Beta versions ==

They are versions at the end of development, possibly containing still bugs, and that must be tested. Normally, we do not add features at this level.

They are still build with sources contained in the trunk branch. Binary installation package of these versions are uploaded on SourceForge.

Do not use them for a real management, use them only on a copy of a database created and succesfully used with the last stable version.

Please, indicate any anomaly you found on the forum.

== Release candidates ==

They are almost totally debugged versions, requiring more tests. We do not add any new feature at this level.

You can use them carefully for a real management, but only after having made a backup of the database and being sure to know how you can restore in case of issues.

Naturally, indicate errors found on the forum. Improvements, will be processed only in the following version.

Binary installation packages of these versions are uploaded on SourceForge.

At the time of their publication, the Alpha level of the next version should be available, in order to validate the upgrade and the upward and downward compatibility between versions. A new branch will be created for the sources.

== Stable versions ==

After a sufficient period of test without important modifications, the last Release Candidate becomes stable.

You can use them for a real management. It remains useful to backup regularly your databases, especially if the version was released recently.

Binary installation packages of these versions are of course uploaded on SourceForge. They will be moved in "Old versions" folder after a new stable version is released, and will stay there as long as this site will allow it.

← Older revision		Revision as of 17:17, 11 February 2020
Line 1:		Line 1:
−	{{~~#CustomTitle~~:Naming and numbering of Gestinux versions}}	+	{{DISPLAYTITLE:Naming and numbering of Gestinux versions}}

	= Numbering =		= Numbering =

@@ Line 21: / Line 21: @@
 They are build with sources contained in the trunk branch. No binary installer will be uploaded on SourceForge for these versions.
-A new chrono is not always when the database structure is changed. In case you encounter errors, you must run a restructuration by checking the option during [[Gdatabase|database selection]].
+The chrono is not always incremented when the database structure is changed. In case you encounter errors, you must run a restructuration by checking the option during [[Gdatabase|database selection]].
 Never use them for real management, only on a copy of a test database.

← Older revision		Revision as of 12:20, 20 November 2015
Line 58:		Line 58:

	Binary installation packages of these versions are of course uploaded on SourceForge. They will be moved in "Old versions" folder after a new stable version is released, and will stay there as long as this site will allow it.		Binary installation packages of these versions are of course uploaded on SourceForge. They will be moved in "Old versions" folder after a new stable version is released, and will stay there as long as this site will allow it.
		+
		+	= Read also =
		+
		+	[[Installing\|Installation]]

@@ Line 45: / Line 45: @@
 Naturally, indicate errors found on the forum. Improvements, will be processed only in the following version.
-Binary installation packages of these versions are uploaded on SourceForge.
+Binary installation packages of these versions are uploaded on SourceForge, at least for Linux 64 bits and Windows.
 == Stable versions ==

@@ Line 29: / Line 29: @@
 == Beta versions ==
-They are versions at the end of development, possibly containing still bugs, and that must be tested. Normally, we do not add features at this level.
+They are versions at the end of development, possibly containing still bugs, and that must be tested. Normally, we add only very little features at this level.
-They are still build with sources contained in the trunk branch. Binary installation package of these versions are uploaded on SourceForge.
+They are still build with sources contained in the trunk branch. All binary installation package of these versions are not uploaded on SourceForge, you must use the building script to compile it when binary is not available.
-Do not use them for a real management, use them only on a copy of a database created and succesfully used with the last stable version.
+Never use them for a real management, use them only on a copy of a database created and succesfully used with the last stable version.
 Please, indicate any anomaly you found on the forum.
 == Release candidates ==

@@ Line 17: / Line 17: @@
 == Alpha versions ==
-Versions in development, not finished, which can contain several severe bugs and possibly destroy datas.
+Versions in development, not finished, which can contain several severe bugs and possibly destroy your data.
-They are still build with sources contained in the trunk branch. No binary installer will be uploaded on SourceForge for these versions.
+They are build with sources contained in the trunk branch. No binary installer will be uploaded on SourceForge for these versions.
 Never use them for real management, only on a copy of a test database.
 You can indicate anomalies, if you are developer and verified that the corresponding sources have not just been archived.
 == Beta versions ==

@@ Line 12: / Line 12: @@
 * 1.2-Release-candidate-1
 * 1.4-Alpha-1
 = Reliability level =