Create release-schedule.md

docs/release-schedule.md

@@ -0,0 +1,75 @@
+# Carbon Design System Release Schedule
+
+This is a living document outlining the plan for previous, current, and future
+major versions of the Carbon Design System.
+
+| Release | Status      | Initial release | Begin Active | Begin Maintenance | End of life |
+| ------- | ----------- | --------------- | ------------ | ----------------- | ----------- |
+| `main`  | unstable    | unstable        | unstable     | unstable          | unstable    |
+| v9      | End of life | 2018-06-04      | 2018-06-04   | 2019-03-29        | 2022-03-31  |
+| v10     | Maintenance | 2019-03-29      | 2019-03-29   | 2022-03-31        | 2024-09-31  |
+| v11     | Active      | 2021-08-06      | 2022-03-31   | 2025-03-31        | 2027-03-31  |
+| v12     | Unreleased  | 2024-08-01      | 2025-03-31   | 2027-03-31        | 2029-03-31  |
+
+> Dates are subject to change
+
+![schedule](https://github.com/carbon-design-system/carbon-website/assets/3360588/02d05990-200c-4380-8acd-82dfbc27483d)
+
+## Release phases
+
+### Prerelease
+
+The prerelease phase is intended to be the opportunity for early adopters,
+library authors, and other strategic ecosystem partners to begin to evaluate and
+integrate new changes into their codebases. For v11, this phase was eight months
+long and spanned four prerelease/beta releases. We hope to extend this timeframe
+even further for our next major.
+
+### Active
+
+Consuming projects should always aim to follow the Active release.
+
+A release in the Active phase receives biweekly minor releases containing new
+features and fixes. The work we deliver into `main` every day is considered
+unstable. Every two weeks we package up these changes into a new minor version
+that is published from `main` to the current Active major.
+
+For a look at what types of changes consitute patch, minor, or major version
+bumps, see the
+[versioning documentation](https://github.com/carbon-design-system/carbon/blob/main/docs/guides/versioning.md).
+
+For a look into the process the Carbon team uses to release packages contained
+within the monorepo, see the
+[release documentation](https://github.com/carbon-design-system/carbon/blob/main/docs/release.md).
+
+### Maintenance
+
+For a release in the Maintenance phase, patch releases are published containing
+security patches and critical bug fixes. When a version moves from Active to
+Maintenance, consuming projects should begin migrating to the new Active major
+version.  During Maintenance we also consider adding non-critical bug fixes on
+an ad hoc basis, by request only. To request a fix be back-ported to a
+Maintenance release, please
+[open an issue](https://github.com/carbon-design-system/carbon/issues/new?assignees=&labels=type%3A+bug+%F0%9F%90%9B&projects=&template=BUG_REPORT.yaml&title=%5BBug%5D%3A+).
+
+## Assets managed under this release schedule
+
+This plan covers the design and development assets under maintenance of the
+Carbon Design System core team. This includes the `@carbon/react` and
+`@carbon/styles` packages, as well as all other packages within the
+[`carbon` monorepo](https://github.com/carbon-design-system/carbon).
+
+This plan also includes all design guidance and design kit assets (figma, etc.)
+present in the
+[`carbon-website`](https://github.com/carbon-design-system/carbon-website) and
+[`design-kit`](https://github.com/carbon-design-system/carbon-design-kit)
+repositories.
+
+## Acknowledgements
+
+This document was heavily inspired by the work of the
+[NodeJS Release Working Group](https://github.com/nodejs/release).
+
+The schedule graph was generated using
+[our fork](https://github.com/carbon-design-system/lts-schedule) of
+[`nodejs/lts-schedule`](https://github.com/nodejs/lts-schedule)