Beta feature: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
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 | 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. | * It has not been thoroughly tested. | ||
* Documentation is very limited. | * Documentation is very limited. | ||
* It is not officially supported. | * It is not officially supported. | ||
Revision as of 15:05, 4 March 2021
A Beta feature describes a feature of the Tygron Platform which is new or experimental. Commonly, this means that the way the functionality has been implemented is simple, to allow Users to experiment with the feature and find how such a functionality could contribute to better implement their use-case.
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:
- It has not been thoroughly tested.
- Documentation is very limited.
- It is not officially supported.