功能生命周期
本页解释了 Storybook 团队如何使用四个生命周期标签对功能进行分类：实验性、预览版、稳定版和弃用版。
¥This page explains how the Storybook team classifies features using four lifecycle labels: Experimental, Preview, Stable, and Deprecated.
这些标签可帮助用户了解我们的承诺程度、预期质量、重大变更的可能性以及每个功能的预计时间表。通过使此过程透明化，我们旨在支持更好的采用决策，并建立对 Storybook 发展方式的信任。
¥These labels help users understand our level of commitment, the expected quality, likelihood of breaking changes, and anticipated timeline for each feature. By making this process transparent, we aim to support better adoption decisions and build trust in how Storybook evolves.
实验性
¥Experimental
此阶段标志着功能开发的开始，我们将在此阶段验证想法并确定方向。
¥This stage marks the beginning of a feature’s development, where we’re validating ideas and shaping direction.
实验性功能仍在开发中，并根据实际使用情况进行迭代。它们非常适合在原型或早期集成中进行尝试，但目前还不适合构建关键路径。每个实验性功能都附带一个 RFC，我们会在其中分享初步想法并报告进度。我们强烈建议你提供反馈，以指导后续步骤。
¥Experimental features are functional but still evolving, with room for iteration based on real-world use. They’re ideal for trying out in prototypes or early integrations, not yet something to build critical paths around. Each experimental feature comes with an RFC where we share the initial idea and report progress. We strongly encourage feedback to help guide the next steps.
在此阶段，我们致力于全面探索这一概念。因此，具体的实现细节在稳定之前可能会发生重大变化。
¥During this stage, we’re committed to fully exploring the concept. As such, specific implementation details may change significantly before stabilization.
预览版
¥Preview
预览功能已接近生产就绪状态，并且总体上可靠，文档齐全，大多数已知问题已得到解决。它们应该至少在一个受支持的框架中完全正常运行，但在其他框架中可能仍然不完整或不够完善。这些功能适用于实际项目，我们鼓励团队采用它们并分享反馈。
¥Preview features are nearly production-ready and generally reliable, with documentation in place and most known issues addressed. They should be fully functional for at least one supported framework, but may still be incomplete or less polished in others. These features are suitable for use in real projects, and we encourage teams to adopt them and share feedback.
虽然该功能的方向是稳定的，但我们可能会在小版本中引入一些微小的重大更改，以解决差距或改进行为。在这种情况下，我们尽可能提供自动迁移功能以简化迁移。我们的目标是在升级到稳定版本之前，收集反馈并迭代 1-2 个小版本。
¥While the feature is stable in direction, we may introduce minimal breaking changes in minor releases to address gaps or refine behavior. In those cases, we provide automigrations where possible to ease the transition. We aim to collect feedback and iterate for 1-2 minor releases before promoting to stable.
稳定版
¥Stable
稳定功能已完全支持，可安全用于所有项目的生产环境。它们有完善的文档，在我们所有核心框架中都经过了全面测试，并遵循 语义版本控制。用户可以期待长期支持，任何重大更改都将保留在主要版本中。
¥Stable features are fully supported and safe for production use across all projects. They are well-documented, thoroughly tested in all of our core frameworks, and follow semantic versioning. Users can expect long-term support, with any breaking changes reserved for major releases.
已弃用
¥Deprecated
已弃用的功能正在逐步淘汰，并将在即将发布的主要版本中移除。用户应尽快开始迁移到受支持的替代方案。这些功能不再进行主动开发或错误修复，并且其功能可能会随着时间的推移而退化。虽然它们可能仍然有效，但不应将它们用于新的开发。
¥Deprecated features are in the process of being phased out and will be removed in an upcoming major release. Users should begin migrating to supported alternatives as soon as possible. These features no longer receive active development or bug fixes, and their functionality may degrade over time. While they may still work, they should not be used for new development.
通常，弃用的功能会在下一个主要发布周期内移除（例如，如果在 8.x 中弃用，则预计在 9.0 中也会移除）。
¥Typically, a deprecated feature is removed within the next major release cycle (for example, if deprecated in 8.x, removal is expected in 9.0).