Merge pull request #3823 from fengypants/patch-2

Update Stability Index blog post w/truncate tag
2020-12-22 18:07:48 +01:00
parent ee4a96e761 6ba936fa27
commit 0f5b6da51b
1 changed files with 2 additions and 0 deletions
@@ -8,6 +8,8 @@ authorURL: https://github.com/Rugvip

 ![Animation cycling between stability index scores](assets/2020-12-22/stability-index-hero.gif)

+<!--truncate-->
+
 Backstage has a great and growing community of users and contributors. With so much valuable feedback, this inevitably means that sometimes we will go back and revise design decisions that introduce breaking changes. Furthermore, as we continue to ship new features and systems, we’ll continue this cycle of iterating, gathering feedback, and iterating again before reaching a stable API.

 This rapid evolution can create uncertainty around which parts of the project are considered stable and which are not. Regardless of whether you're contributing to the project directly, setting up your own Backstage, or building plugins, you will be using various parts of the project that vary in stability. While many API surfaces of Backstage are reasonably solid and are unlikely to see any big breaking changes, others are more unstable or experimental.