Beta feature: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
Maxim@tygron.com (talk | contribs)
No edit summary
 
Line 1: Line 1:
A Beta feature describes a feature of the {{software}} which is new or experimental. Commonly, this means that the way the functionality has been implemented is simple, to allow [[User]]s to experiment with the feature and find how such a functionality could contribute to better implement their use-case.
A BETA feature describes a feature of the {{software}} which is new or experimental. This typically involves an initial implementation, allowing [[User]]s to experiment with the feature and determine how it can best support their use-cases.


Beta features are expected to be developed further if sufficient interest in the functionality exists among [[User]]s, and it becomes clearer exactly how the feature should be expanded upon to effectively contribute to the use-cases which can benefit from the feature.
BETA features are expected to be developed further if sufficient interest in the functionality exists among [[User]]s, and it becomes clearer exactly how the feature should be expanded upon to effectively contribute to the use-cases which can benefit from the feature.


When accessing a Beta feature, the software may prompt to the user to confirm that they wish to use the functionality with the following aspects taken into account:
When accessing a BETA feature, the software may prompt to the user to confirm that they wish to use the functionality with the following aspects taken into account:
* It has not been thoroughly tested.
 
* Documentation is very limited.
* Testing is currently ongoing.
* It is not officially supported.
* Documentation is under development.
* It is subject to change.
* It is not officially supported (see license agreement for more).
* It is subject to change or maybe deprecated.

Latest revision as of 07:47, 9 July 2026

A BETA feature describes a feature of the Tygron Platform which is new or experimental. This typically involves an initial implementation, allowing Users to experiment with the feature and determine how it can best support their use-cases.

BETA features are expected to be developed further if sufficient interest in the functionality exists among Users, and it becomes clearer exactly how the feature should be expanded upon to effectively contribute to the use-cases which can benefit from the feature.

When accessing a BETA feature, the software may prompt to the user to confirm that they wish to use the functionality with the following aspects taken into account:

  • Testing is currently ongoing.
  • Documentation is under development.
  • It is not officially supported (see license agreement for more).
  • It is subject to change or maybe deprecated.