Hi all,
I wanted to share transparency around the different component statuses and their usage. I also want to highlight some recent changes that we have made to enforce the correct usage, and ensure a minimum quality level via deployment restrictions. This is something we have been gradually rolling out over the last 6 months, but I wanted to note it on the community for transparency.
| A) | Our component statuses: |
|---|---|
| i. | WIP (Work in Progress) – Just saved work, but not considered finished yet. |
| ii. | NB (Nightly Build) – It might work but it is not tested or reviewed yet. It may not even be ‘‘finished’’. For this reason, NBs should NEVER be used in a production environment. |
| iii. | CTP (Customer technology preview) – it has been tested by the developer and is available to compose on a specific application. This should follow any quality process as defined by the development team; this can vary per team, however the end result should be that the developer has confidence that it works. Simply the developer has confidence that it should work, and is complete. |
| iv. | Beta – a component has passed the QA scanner. This should guarantee composability for all applications, and stabilise the sharing of content between companies. Note: this does not guarantee functionality: but does ensure that applications remain composable |
| v. | Baseline – a temporary status used during the transition period. It is only used by components that have been in productions for a long time and have proven to be ‘’above ctp’’. However future revisions should be put through the QA scanner to become Beta, slowly phasing this status out of use. |
| vi. | Stable – it has had a thorough manual QA check. |
Our aim is to gradually get all applications from the current NB/CTP level, towards the stable level. This will be done in several phases.
Phase 1 - Restricting the use of NBs in production and acceptance environments. Essentially meaning that only components with CTP or above can be used.
Phase 2 - Rolling out the QA scanner for usage, to ensure that all CTP components are validated for composability (amongst other things - such as missing release notes, previous manual-QA rejections, missing translations etc) and upgraded from CTP to a Beta status.
Phase 3 - Once an application is fully Beta. Deployment restrictions for that application will be increased from CTP to Beta or above.
Future phases will focus on getting from Beta to a stable level.
If you have any issues with future deployments because of this restriction; please contact us and we can provide advice on how to proceed.
