Due to the nature of the Crate Marketplace, and the many integrations that we support, we often have various stages of Crate deployment. This helps us make sure that Crates are thoroughly tested both internally and by our willing customers. To make this process as transparent as possible, we've created a state system for Crates.
You can determine a Crate's state by looking it up in Crate Marketplace and checking its color coded state label in the bottom right of that Crate tile. Similarly, the red number count on the bottom left corner of a Crate tile shows you the current count of fellow Rewsters that have unpacked and used the Crate. Click to expand and learn about each of our Crate states below.
Note that each Crate may differ in terms of requirements, setup time, and complexity.
We try to provide an estimate of the setup time for each Crate, whenever possible, but info may not be readily available for Crates in earlier stages.
Egg: Pre-alpha release
This is the initial state of a Crate. It is the equivalent of a pre-alpha release. It is generally not recommended to use these Crates in production.
We will often create Crates in this state to show what is actively being worked on, and to get feedback from our clients to make sure that we're working on the right things.
Hatchling: Alpha release
This is the first stage of a Crate that is ready for testing, but still considered alpha. It's not recommended to use these Crates in production.
This state will often be used when we are doing internal testing, or the Crate was made for a very specific purpose/requirement and is being tested directly with the requesting client.
Fledgling: Beta release
This is the second stage of a Crate that is ready for testing, and is the equivalent of a beta release.
At this stage, it is recommended to use client discretion when using these Crates in production.
This state will often be used when we have moved on from internal testing and believe that the Crate is ready for wider testing, but still needs to be tested in a production environment rather than our sandbox environments.
The ROC team will support this Crate in this state.
Nestling: Release candidate
This is the third stage of a Crate that is ready for production, and is the equivalent of a release candidate.
At this stage, it's still recommended to use discretion when using these Crates in production. However, they have gone through vigorous testing in various environments and are considered stable.
This state will often be used when we've moved on from a smaller range of clients testing the Crate, and are now ready to release it to a wider audience with potentially more complex environments.
The ROC team will support this Crate in this state.
Soaring: Full release
This is the final stage of a Crate that's ready for production, and is the equivalent of a full release.
At this stage, the Crate is considered stable and ready for production use.
The ROC team will support this Crate in this state.
Migrating: Updating to a new version
This is the state where a Crate has been updated to a new version, but the older version is still available for clients to use.
This state will often be used when we have made a breaking change to a Crate, and we want to ensure that clients have time to migrate to the new version before we remove the old version.
The ROC team will support this Crate in this state.
