|
1 | 1 | --- |
2 | | -title: "Beta and Experimental Releases" |
3 | | -url: /releasenotes/beta-features/ |
| 2 | +title: "Release Status" |
| 3 | +url: /releasenotes/release-status/ |
4 | 4 | weight: 55 |
| 5 | +aliases: |
| 6 | + - /releasenotes/beta-features/ |
5 | 7 | #layout: wide |
6 | 8 | --- |
7 | 9 |
|
8 | 10 | ## Introduction |
9 | 11 |
|
10 | | -Some Mendix Platform releases contain beta or experimental features or products that can be used and evaluated by early-adopter developers. |
| 12 | +Generally, the release status of a feature or product can go through the following phases: |
11 | 13 |
|
12 | | -Mendix releases beta versions in two circumstances: |
| 14 | +1. Private beta. |
| 15 | +2. Experimental. |
| 16 | +3. Public beta. |
| 17 | +4. Limited availability (LA). |
| 18 | +5. General availability (GA). |
| 19 | +6. Deprecated |
13 | 20 |
|
14 | | -* When a new product or product version is introduced and made available to early adopters so that they can try it |
15 | | -* When individual features are introduced within a non-beta product which are, in principle, production-ready but are either subject to change or need to be reviewed by a broader audience; these features are disabled by default |
| 21 | +This document outlines the purpose of each phase and what customers can expect from Mendix. |
16 | 22 |
|
17 | | -Mendix releases experimental versions when a new product or product version is introduced and can already provide value to the user, but Mendix cannot yet guarantee the stability or quality and may never release this as GA. |
| 23 | +Some of the phases are optional. The release status impacts the support level for the feature or product. More specifically, Limited or General Availability features or products are ready for production use and are covered by your Support Level Agreement, as opposed to Private Beta, Public Beta, or Experimental features. |
18 | 24 |
|
19 | | -Generally, the release status of a feature or product can follow this order: |
| 25 | +Next to release statuses, content available on Mendix Marketplace has a Support status (for example, Platform Supported or Deprecated). For more information, see the [Content Support Categories](/appstore/marketplace-content-support/#category) section in the *Marketplace Support Content*. |
20 | 26 |
|
21 | | -1. Private beta. |
22 | | -2. Experimental. |
23 | | -3. Public beta. |
24 | | -4. General availability (GA). |
| 27 | +## Private Beta, Experimental, and Public Beta Releases |
25 | 28 |
|
26 | | -We collect feedback on the implementation and use of these beta/experimental features and products so that we can improve them. We value any feedback, as it enables us to provide you with the best possible product. This also helps us prepare for the GA release. |
| 29 | +Mendix releases features or products labeled Private beta, Experimental, or Public beta in order to collect feedback on their implementation and use. We value any feedback, because feedback enables us to provide you with the best possible product. This also helps us prepare the feature or product for the GA release. |
27 | 30 |
|
28 | | -An example is a new major version of Mendix Studio Pro. We release this product in beta, as the feature sets may not be complete and developers may find gaps in functionality that Mendix is still working on. |
| 31 | +An example is a new major version of Mendix Studio Pro. Mendix releases this product in beta, as the features may not be complete and developers may find gaps in functionality that Mendix is still working on. |
29 | 32 |
|
30 | | -The availability of beta/experimental features and products is documented in the release notes for the release. Other documentation may be provided by Mendix. Please consult the release notes and the documentation for details on how to enable and use these features and products. |
| 33 | +### Availability of Beta Features |
31 | 34 |
|
32 | | -In the docs, pages about beta features are marked with a beta badge (<text class="badge badge-pill badge-beta" style="margin-left:0px">BETA</text>) on the left sidebar. |
| 35 | +Private beta features or products are available to selected customers only, whereas Experimental and Public beta features or products are available to all customers. |
| 36 | + |
| 37 | +### Typical Use Cases |
| 38 | + |
| 39 | +Mendix releases Private beta or Public beta features or products in two cases: |
| 40 | + |
| 41 | +* When a new product or a product version is introduced and made available to early adopters so that they can try it, with the aim to become GA in the future |
| 42 | +* When individual features are introduced within a non-beta product which are, in principle, production-ready but are either subject to change or need to be reviewed by a broader audience (these features are disabled by default) |
| 43 | + |
| 44 | +Mendix releases Experimental features or products when those features or products can already provide value to the user, but Mendix cannot yet guarantee the stability or quality and may never release this as GA. |
33 | 45 |
|
34 | | -## Testing Beta Releases |
| 46 | +### Testing Beta Releases |
35 | 47 |
|
36 | 48 | If you would like to test a beta feature or product, consider the following: |
37 | 49 |
|
38 | | -* Contact the responsible Mendix Product Manager (PM) who can assist you in your test app |
39 | | - * The PM can help you identify if your use case is a good fit for the particular beta feature or product |
40 | | - * Your Customer Success Manager (CSM) can introduce you |
41 | | -* Your CSM will also ensure the involvement of Mendix Expert Services if required in order to aid you in your test app and provide you with the required knowledge to successfully make use of the beta feature or product |
42 | | -* Feedback on the quality of the beta feature or product will be evaluated by the PM |
43 | | -* When there is a strong desire to take a beta feature or product into production, please contact your CSM to see if special arrangements are possible |
| 50 | +* Features or products labeled Public beta or Experimental are available for all customers. Your feedback on these features is welcome through your Customer Success Manager (CSM) and in the community forum. |
| 51 | +* For features or products labeled Private beta, our product team usually reaches out to you with an invitation to test the feature or products. They will be your point of contact for any feedback and will ensure the involvement of Mendix Expert Services if required to provide you with the required knowledge to successfully make use of the private beta feature or product. |
44 | 52 |
|
45 | | -## Limitations of Beta and Experimental Releases |
| 53 | +### Limitations of Beta and Experimental Releases |
46 | 54 |
|
47 | 55 | Please take note of the following limitations regarding beta/experimental features and products: |
48 | 56 |
|
49 | | -* Beta/experimental features and products should not be used for production applications |
50 | | - * We do not offer production support on beta/experimental features and products |
| 57 | +* These features and products should not be used for production applications |
| 58 | + * Mendix does not offer production support on beta/experimental features and products |
51 | 59 | * Beta/experimental features and products may contain bugs, which could potentially lead to data corruption |
52 | | -* Beta/experimental features and products are not covered by any SLA |
53 | | - * We value feedback, including tickets describing problems with beta/experimental features and products, but these tickets will not be handled according to your SLA |
54 | | - * We cannot guarantee timely fixes for any problems you encounter with beta/experimental features and products |
55 | | -* Beta/experimental features and products may introduce breaking changes |
| 60 | +* These features and products are not covered by any SLA |
| 61 | + * Mendix values feedback, including tickets describing problems with beta/experimental features and products, but these tickets will not be handled according to your SLA |
| 62 | + * Mendix cannot guarantee timely fixes for any problems you encounter with beta/experimental features and products |
| 63 | +* These features and products may introduce breaking changes |
56 | 64 | * Although we aim for backwards compatibility, Mendix cannot guarantee backwards compatibility between monthly releases for beta/experimental features and products |
57 | | -* Beta/experimental features and products may change in future releases, depending on the feedback |
58 | | -* Beta/experimental features and products may be incomplete |
| 65 | +* Their scope and functionality may change in future releases, depending on the feedback |
| 66 | +* Their scope may be incomplete |
59 | 67 | * Future releases may include more functionality to complete the feature or product |
60 | | -* Experimental features and products may be made available to a limited group of users |
61 | | -* Experimental features and products may be removed at any time from existing and future releases |
| 68 | + |
| 69 | +In addition, features or products labeled Experimental: |
| 70 | + |
| 71 | +* May be made available to a limited group of users only |
| 72 | +* May be removed at any time from existing and future releases |
| 73 | + |
| 74 | +### Documentation |
| 75 | + |
| 76 | +The availability of beta/experimental features and products is documented in the release notes for the release. Other documentation may be provided by Mendix. Please consult the release notes and the documentation for details on how to enable and use these features and products. |
| 77 | + |
| 78 | +In the docs, pages about beta features are marked with a beta badge (<text class="badge badge-pill badge-beta" style="margin-left:0px">BETA</text>) on the left sidebar. |
| 79 | + |
| 80 | +## Limited Availability |
| 81 | + |
| 82 | +Mendix releases features or products labeled Limited Availability to introduce the feature or product to the market in a controlled way. In this optional phase, specific groups or regions may get access to the feature or product for production use, while others may follow later. This can be due to regulatory or operational reasons. When there is a desire to take a Limited Availability feature or product into production, please contact your CSM to see which arrangements are possible. |
| 83 | + |
| 84 | +## General Availability |
| 85 | + |
| 86 | +Features or products labeled General Availability are available for all customers to use in production. |
0 commit comments