From 20c84cba48ba7e888e673e9913c482cccbab23e2 Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Fri, 15 Sep 2023 13:40:14 +0200 Subject: [PATCH 01/10] add deprecation process document --- substrate/docs/deprecation-process.md | 59 +++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 substrate/docs/deprecation-process.md diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md new file mode 100644 index 000000000000..e26f0d2e0d2d --- /dev/null +++ b/substrate/docs/deprecation-process.md @@ -0,0 +1,59 @@ +# Deprecation Process + +This deprecation process makes sense while we don’t [SemVer](https://semver.org/), after that this process will most likely change. + +As deprecation and removal of existing features can happen on any release we need to be mindful that external builders can be impacted by the changes we make. + +This process tries to mitigate this impact, while still keeping the devex as smooth as possible. + +First of all we need to create a new issue with the label `I11-deprecation` and add it to the [Runtime / FRAME](https://github.com/orgs/paritytech/projects/40) project. This will make sure that the issue is added to the [Deprecation board](https://github.com/orgs/paritytech/projects/40/views/12) for correct tracking. + +These are the actions to take: + +### Hard deprecate by adding a warning message + +The warning message should include a removal month and year, which is suggested to be 6 months from the deprecation notice is released. This means that the feature will be removed in a release within that month (or after, but never before). Something on these lines: + +```rust +#[deprecated(note = "`GenesisConfig` is planned to be removed in December 2023. +Use `RuntimeGenesisConfig` instead.")] + +``` + +Some features cannot be label as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) or [dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159) for instance. On cases like that we can only make a visible enough comment, and make sure that we [announce the deprecation properly](#announce-the-deprecation-and-removal). + +### Remove usage of the deprecated feature in the code base + +Just make sure that we are not using the deprecated feature ourselves. If you added the deprecation warning from the previous step, this should be easy to get done. + +### Update examples and tutorials + +Make sure that the rust docs is updated. + +We also want [https://docs.substrate.io/](https://docs.substrate.io/) to be updated, you can open an issue on [https://github.com/substrate-developer-hub/substrate-docs](https://github.com/substrate-developer-hub/substrate-docs). + +### Announce the deprecation and removal + +**At minimum they should be noted in the release log.** +Sometimes the release note is not enough. Make sure you are as loud as you need to be for the magnitude of the breaking change. Some breaking changes have a bigger impact than others. + +### Removal version is planned + +Depending on the removal date indicated in the deprecation warning in the [first step](#hard-deprecate-by-adding-a-warning-message), the nature and the importance of the change, it might make sense to coordinate the release with other developers and with the Release team. + +### Deprecated feature is removed + +The deprecated feature gets finally removed. Don’t forget to [announce this accordingly](#announce-the-deprecation-and-removal). + +✅ In order to not forget any of these steps, consider using this template in your deprecation issue: +``` +### Tasks + +- [ ] Deprecate feature by adding a warning message +- [ ] Remove usage of the deprecated feature in the code base +- [ ] Update examples and tutorials +- [ ] Announce feature deprecation +- [ ] Plan removal version +- [ ] Announce feature removal +- [ ] Remove deprecated feature +``` \ No newline at end of file From 01bdc53a487bea4517ddaf59df63cc3757f787a0 Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Fri, 15 Sep 2023 13:45:24 +0200 Subject: [PATCH 02/10] add new line --- substrate/docs/deprecation-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md index e26f0d2e0d2d..1a8d1ee4dd6c 100644 --- a/substrate/docs/deprecation-process.md +++ b/substrate/docs/deprecation-process.md @@ -56,4 +56,4 @@ The deprecated feature gets finally removed. Don’t forget to [announce this ac - [ ] Plan removal version - [ ] Announce feature removal - [ ] Remove deprecated feature -``` \ No newline at end of file +``` From 46a7f526c7a88352293d2626e472b78728651418 Mon Sep 17 00:00:00 2001 From: Juan Date: Fri, 15 Sep 2023 15:13:12 +0200 Subject: [PATCH 03/10] Update substrate/docs/deprecation-process.md Co-authored-by: Francisco Aguirre --- substrate/docs/deprecation-process.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md index 1a8d1ee4dd6c..7c9dd95a8a63 100644 --- a/substrate/docs/deprecation-process.md +++ b/substrate/docs/deprecation-process.md @@ -1,6 +1,7 @@ # Deprecation Process -This deprecation process makes sense while we don’t [SemVer](https://semver.org/), after that this process will most likely change. +This deprecation process makes sense while we don’t use [SemVer](https://semver.org/). +After that, this process will most likely change. As deprecation and removal of existing features can happen on any release we need to be mindful that external builders can be impacted by the changes we make. From 2e38826c24806a0d299a44ed038e71d68ee97f79 Mon Sep 17 00:00:00 2001 From: Juan Date: Fri, 15 Sep 2023 15:16:53 +0200 Subject: [PATCH 04/10] Apply suggestions from code review Co-authored-by: Francisco Aguirre --- substrate/docs/deprecation-process.md | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md index 7c9dd95a8a63..16776ac2d1f3 100644 --- a/substrate/docs/deprecation-process.md +++ b/substrate/docs/deprecation-process.md @@ -2,18 +2,17 @@ This deprecation process makes sense while we don’t use [SemVer](https://semver.org/). After that, this process will most likely change. +As deprecation and removal of existing features can happen on any release, we need to be mindful that external builders could be impacted by the changes we make. +The deprecation process tries to mitigate this impact, while still keeping the developer experience, the DevEx, as smooth as possible. -As deprecation and removal of existing features can happen on any release we need to be mindful that external builders can be impacted by the changes we make. - -This process tries to mitigate this impact, while still keeping the devex as smooth as possible. - -First of all we need to create a new issue with the label `I11-deprecation` and add it to the [Runtime / FRAME](https://github.com/orgs/paritytech/projects/40) project. This will make sure that the issue is added to the [Deprecation board](https://github.com/orgs/paritytech/projects/40/views/12) for correct tracking. +First of all we, need to create a new issue with the label `I11-deprecation` and add it to the [Runtime / FRAME](https://github.com/orgs/paritytech/projects/40) project. This will make sure that the issue is added to the [Deprecation board](https://github.com/orgs/paritytech/projects/40/views/12) for correct tracking. These are the actions to take: ### Hard deprecate by adding a warning message -The warning message should include a removal month and year, which is suggested to be 6 months from the deprecation notice is released. This means that the feature will be removed in a release within that month (or after, but never before). Something on these lines: +The warning message should include a removal month and year, which is suggested to be 6 months after the deprecation notice is released. +This means that the feature will be removed in a release within that month (or after, but never before). Something along these lines: ```rust #[deprecated(note = "`GenesisConfig` is planned to be removed in December 2023. @@ -21,22 +20,24 @@ Use `RuntimeGenesisConfig` instead.")] ``` -Some features cannot be label as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) or [dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159) for instance. On cases like that we can only make a visible enough comment, and make sure that we [announce the deprecation properly](#announce-the-deprecation-and-removal). +Some features cannot be labeled as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) or [dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159), for instance. +On cases like that we can only make a visible enough comment, and make sure that we [announce the deprecation properly](#announce-the-deprecation-and-removal). ### Remove usage of the deprecated feature in the code base -Just make sure that we are not using the deprecated feature ourselves. If you added the deprecation warning from the previous step, this should be easy to get done. +Just make sure that we are not using the deprecated feature ourselves. +If you added the deprecation warning from the previous step, this can be done by making sure that warning is not shown when building the code. ### Update examples and tutorials -Make sure that the rust docs is updated. - +Make sure that the rust docs are updated. We also want [https://docs.substrate.io/](https://docs.substrate.io/) to be updated, you can open an issue on [https://github.com/substrate-developer-hub/substrate-docs](https://github.com/substrate-developer-hub/substrate-docs). ### Announce the deprecation and removal **At minimum they should be noted in the release log.** -Sometimes the release note is not enough. Make sure you are as loud as you need to be for the magnitude of the breaking change. Some breaking changes have a bigger impact than others. +Sometimes the release note is not enough. +Make sure you are as loud as you need to be for the magnitude of the breaking change. Some breaking changes have a bigger impact than others. ### Removal version is planned @@ -44,7 +45,8 @@ Depending on the removal date indicated in the deprecation warning in the [first ### Deprecated feature is removed -The deprecated feature gets finally removed. Don’t forget to [announce this accordingly](#announce-the-deprecation-and-removal). +The deprecated feature finally gets removed. +Don’t forget to [announce this accordingly](#announce-the-deprecation-and-removal). ✅ In order to not forget any of these steps, consider using this template in your deprecation issue: ``` From 00f4fc4b83503537934fc540519606508650f697 Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Fri, 15 Sep 2023 15:56:38 +0200 Subject: [PATCH 05/10] reformat markdown --- substrate/docs/deprecation-process.md | 60 +++++++++++++++------------ 1 file changed, 34 insertions(+), 26 deletions(-) diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md index 16776ac2d1f3..3aed0fd0530e 100644 --- a/substrate/docs/deprecation-process.md +++ b/substrate/docs/deprecation-process.md @@ -2,61 +2,69 @@ This deprecation process makes sense while we don’t use [SemVer](https://semver.org/). After that, this process will most likely change. -As deprecation and removal of existing features can happen on any release, we need to be mindful that external builders could be impacted by the changes we make. -The deprecation process tries to mitigate this impact, while still keeping the developer experience, the DevEx, as smooth as possible. +As deprecation and removal of existing features can happen on any release, we need to be mindful that external builders +could be impacted by the changes we make. +The deprecation process tries to mitigate this impact, while still keeping the developer experience, the DevEx, as +smooth as possible. -First of all we, need to create a new issue with the label `I11-deprecation` and add it to the [Runtime / FRAME](https://github.com/orgs/paritytech/projects/40) project. This will make sure that the issue is added to the [Deprecation board](https://github.com/orgs/paritytech/projects/40/views/12) for correct tracking. +To start a deprecation process a new issue with the label `I11-deprecation` needs to be created for correct tracking. +Then these are the actions to take: -These are the actions to take: +## Hard deprecate by adding a warning message -### Hard deprecate by adding a warning message - -The warning message should include a removal month and year, which is suggested to be 6 months after the deprecation notice is released. -This means that the feature will be removed in a release within that month (or after, but never before). Something along these lines: +The warning message shall include a removal month and year, which is suggested to be 6 months after the deprecation +notice is released. +This means that the feature will be removed in a release within that month (or after, but never before). Something +along these lines: ```rust #[deprecated(note = "`GenesisConfig` is planned to be removed in December 2023. Use `RuntimeGenesisConfig` instead.")] - ``` -Some features cannot be labeled as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) or [dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159), for instance. +Some features cannot be labeled as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) or +[dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159), for instance. On cases like that we can only make a visible enough comment, and make sure that we [announce the deprecation properly](#announce-the-deprecation-and-removal). -### Remove usage of the deprecated feature in the code base +## Remove usage of the deprecated feature in the code base Just make sure that we are not using the deprecated feature ourselves. -If you added the deprecation warning from the previous step, this can be done by making sure that warning is not shown when building the code. +If you added the deprecation warning from the previous step, this can be done by making sure that warning is not shown +when building the code. -### Update examples and tutorials +## Update examples and tutorials Make sure that the rust docs are updated. We also want [https://docs.substrate.io/](https://docs.substrate.io/) to be updated, you can open an issue on [https://github.com/substrate-developer-hub/substrate-docs](https://github.com/substrate-developer-hub/substrate-docs). -### Announce the deprecation and removal +## Announce the deprecation and removal **At minimum they should be noted in the release log.** Sometimes the release note is not enough. -Make sure you are as loud as you need to be for the magnitude of the breaking change. Some breaking changes have a bigger impact than others. +Make sure you are as loud as you need to be for the magnitude of the breaking change. Some breaking changes have a +bigger impact than others. -### Removal version is planned +## Removal version is planned -Depending on the removal date indicated in the deprecation warning in the [first step](#hard-deprecate-by-adding-a-warning-message), the nature and the importance of the change, it might make sense to coordinate the release with other developers and with the Release team. +Depending on the removal date indicated in the deprecation warning in the [first step](#hard-deprecate-by-adding-a-warning-message), +the nature and the importance of the change, it might make sense to coordinate the release with other developers and +with the Release team. -### Deprecated feature is removed +## Deprecated feature is removed The deprecated feature finally gets removed. Don’t forget to [announce this accordingly](#announce-the-deprecation-and-removal). ✅ In order to not forget any of these steps, consider using this template in your deprecation issue: -``` + +```markdown ### Tasks -- [ ] Deprecate feature by adding a warning message -- [ ] Remove usage of the deprecated feature in the code base -- [ ] Update examples and tutorials -- [ ] Announce feature deprecation -- [ ] Plan removal version -- [ ] Announce feature removal -- [ ] Remove deprecated feature +- [ ] Deprecate feature by adding a warning message +- [ ] Remove usage of the deprecated feature in the code base +- [ ] Update examples and tutorials +- [ ] Announce feature deprecation +- [ ] Plan removal version +- [ ] Announce feature removal +- [ ] Remove deprecated feature ``` From 93bbecc360ccfa923e4360fab1426d82c23b2975 Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Fri, 15 Sep 2023 17:25:22 +0200 Subject: [PATCH 06/10] replace "feature" by "code" and add link to documentation --- substrate/docs/deprecation-process.md | 30 +++++++++++++-------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md index 3aed0fd0530e..418a772f887e 100644 --- a/substrate/docs/deprecation-process.md +++ b/substrate/docs/deprecation-process.md @@ -2,7 +2,7 @@ This deprecation process makes sense while we don’t use [SemVer](https://semver.org/). After that, this process will most likely change. -As deprecation and removal of existing features can happen on any release, we need to be mindful that external builders +As deprecation and removal of existing code can happen on any release, we need to be mindful that external builders could be impacted by the changes we make. The deprecation process tries to mitigate this impact, while still keeping the developer experience, the DevEx, as smooth as possible. @@ -14,21 +14,21 @@ Then these are the actions to take: The warning message shall include a removal month and year, which is suggested to be 6 months after the deprecation notice is released. -This means that the feature will be removed in a release within that month (or after, but never before). Something -along these lines: +This means that the code will be removed in a release within that month (or after, but never before). Something along +these lines: ```rust #[deprecated(note = "`GenesisConfig` is planned to be removed in December 2023. Use `RuntimeGenesisConfig` instead.")] ``` -Some features cannot be labeled as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) or -[dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159), for instance. +Some pieces of code cannot be labeled as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) +or [dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159), for instance. On cases like that we can only make a visible enough comment, and make sure that we [announce the deprecation properly](#announce-the-deprecation-and-removal). -## Remove usage of the deprecated feature in the code base +## Remove usage of the deprecated code in the code base -Just make sure that we are not using the deprecated feature ourselves. +Just make sure that we are not using the deprecated code ourselves. If you added the deprecation warning from the previous step, this can be done by making sure that warning is not shown when building the code. @@ -39,7 +39,7 @@ We also want [https://docs.substrate.io/](https://docs.substrate.io/) to be upda ## Announce the deprecation and removal -**At minimum they should be noted in the release log.** +**At minimum they should be noted in the release log.** Please see how to document a PR [here](https://github.com/paritytech/polkadot-sdk/blob/master/docs/CONTRIBUTING.md#documentation). Sometimes the release note is not enough. Make sure you are as loud as you need to be for the magnitude of the breaking change. Some breaking changes have a bigger impact than others. @@ -50,9 +50,9 @@ Depending on the removal date indicated in the deprecation warning in the [first the nature and the importance of the change, it might make sense to coordinate the release with other developers and with the Release team. -## Deprecated feature is removed +## Deprecated code is removed -The deprecated feature finally gets removed. +The deprecated code finally gets removed. Don’t forget to [announce this accordingly](#announce-the-deprecation-and-removal). ✅ In order to not forget any of these steps, consider using this template in your deprecation issue: @@ -60,11 +60,11 @@ Don’t forget to [announce this accordingly](#announce-the-deprecation-and-remo ```markdown ### Tasks -- [ ] Deprecate feature by adding a warning message -- [ ] Remove usage of the deprecated feature in the code base +- [ ] Deprecate code by adding a warning message +- [ ] Remove usage of the deprecated code in the code base - [ ] Update examples and tutorials -- [ ] Announce feature deprecation +- [ ] Announce code deprecation - [ ] Plan removal version -- [ ] Announce feature removal -- [ ] Remove deprecated feature +- [ ] Announce code removal +- [ ] Remove deprecated code ``` From c477beaadb4aa01e9daedfee1b8bea411ae55520 Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Fri, 15 Sep 2023 17:35:53 +0200 Subject: [PATCH 07/10] add deprecation template --- substrate/docs/deprecation-process.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md index 418a772f887e..adfebde805ce 100644 --- a/substrate/docs/deprecation-process.md +++ b/substrate/docs/deprecation-process.md @@ -14,12 +14,17 @@ Then these are the actions to take: The warning message shall include a removal month and year, which is suggested to be 6 months after the deprecation notice is released. -This means that the code will be removed in a release within that month (or after, but never before). Something along -these lines: +This means that the code will be removed in a release within that month (or after, but never before). Please use this +template, doing so makes it easy to search through the code base: ```rust -#[deprecated(note = "`GenesisConfig` is planned to be removed in December 2023. -Use `RuntimeGenesisConfig` instead.")] +#[deprecated(note = "[DEPRECATED] will be removed after [DATE]. [ALTERNATIVE]")] +``` +`[ALTERNATIVE]` won't always be possible but offer it if it is. + +E.g. +```rust +#[deprecated(note = "`GenesisConfig` will be removed after December 2023. Use `RuntimeGenesisConfig` instead.")] ``` Some pieces of code cannot be labeled as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) From 752209b9efdaa7fbf224348e7d27f22a4fec9cfc Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Sat, 16 Sep 2023 10:23:37 +0200 Subject: [PATCH 08/10] add minor updates --- substrate/docs/deprecation-process.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/substrate/docs/deprecation-process.md b/substrate/docs/deprecation-process.md index adfebde805ce..e486495620d4 100644 --- a/substrate/docs/deprecation-process.md +++ b/substrate/docs/deprecation-process.md @@ -29,7 +29,7 @@ E.g. Some pieces of code cannot be labeled as deprecated, like [reexports](https://github.com/rust-lang/rust/issues/30827) or [dispatchables](https://github.com/paritytech/polkadot-sdk/issues/182#issuecomment-1691684159), for instance. -On cases like that we can only make a visible enough comment, and make sure that we [announce the deprecation properly](#announce-the-deprecation-and-removal). +In cases like that we can only make a visible enough comment, and make sure that we [announce the deprecation properly](#announce-the-deprecation-and-removal). ## Remove usage of the deprecated code in the code base @@ -40,7 +40,8 @@ when building the code. ## Update examples and tutorials Make sure that the rust docs are updated. -We also want [https://docs.substrate.io/](https://docs.substrate.io/) to be updated, you can open an issue on [https://github.com/substrate-developer-hub/substrate-docs](https://github.com/substrate-developer-hub/substrate-docs). +We also need [https://docs.substrate.io/](https://docs.substrate.io/) to be updated accordingly. The repo behind it is +[https://github.com/substrate-developer-hub/substrate-docs](https://github.com/substrate-developer-hub/substrate-docs). ## Announce the deprecation and removal From 1a1b74ff1861c2261be0775c88901b1c9c9f3fc6 Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Mon, 18 Sep 2023 16:46:13 +0100 Subject: [PATCH 09/10] move deprecation document --- .../DEPRECATION_CHECKLIST.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) rename substrate/docs/deprecation-process.md => docs/DEPRECATION_CHECKLIST.md (78%) diff --git a/substrate/docs/deprecation-process.md b/docs/DEPRECATION_CHECKLIST.md similarity index 78% rename from substrate/docs/deprecation-process.md rename to docs/DEPRECATION_CHECKLIST.md index e486495620d4..8ad18b32c189 100644 --- a/substrate/docs/deprecation-process.md +++ b/docs/DEPRECATION_CHECKLIST.md @@ -1,13 +1,13 @@ -# Deprecation Process +# Deprecation Checklist -This deprecation process makes sense while we don’t use [SemVer](https://semver.org/). -After that, this process will most likely change. +This deprecation checklist makes sense while we don’t use [SemVer](https://semver.org/). +After that, this document will most likely change. As deprecation and removal of existing code can happen on any release, we need to be mindful that external builders could be impacted by the changes we make. -The deprecation process tries to mitigate this impact, while still keeping the developer experience, the DevEx, as +The deprecation checklist tries to mitigate this impact, while still keeping the developer experience, the DevEx, as smooth as possible. -To start a deprecation process a new issue with the label `I11-deprecation` needs to be created for correct tracking. +To start a deprecation process, a new issue with the label `I11-deprecation` needs to be created for correct tracking. Then these are the actions to take: ## Hard deprecate by adding a warning message @@ -46,9 +46,12 @@ We also need [https://docs.substrate.io/](https://docs.substrate.io/) to be upda ## Announce the deprecation and removal **At minimum they should be noted in the release log.** Please see how to document a PR [here](https://github.com/paritytech/polkadot-sdk/blob/master/docs/CONTRIBUTING.md#documentation). -Sometimes the release note is not enough. -Make sure you are as loud as you need to be for the magnitude of the breaking change. Some breaking changes have a -bigger impact than others. +There you can give instructions based on the audience and tell them what they need to do to upgrade the code. + +Some breaking changes have a bigger impact than others. When the impact is big the release note is not enough, though +it should still be the primary place for the notice. You can link back to the changelog files in other channels if you +want to announce it somewhere else. +Make sure you are as loud as you need to be for the magnitude of the breaking change. ## Removal version is planned From 94f200aec040c14a3dfebf06f7818244eb62316e Mon Sep 17 00:00:00 2001 From: Juan Girini Date: Thu, 21 Sep 2023 16:46:11 +0200 Subject: [PATCH 10/10] update label name --- docs/DEPRECATION_CHECKLIST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/DEPRECATION_CHECKLIST.md b/docs/DEPRECATION_CHECKLIST.md index 8ad18b32c189..fccf93d22737 100644 --- a/docs/DEPRECATION_CHECKLIST.md +++ b/docs/DEPRECATION_CHECKLIST.md @@ -7,7 +7,7 @@ could be impacted by the changes we make. The deprecation checklist tries to mitigate this impact, while still keeping the developer experience, the DevEx, as smooth as possible. -To start a deprecation process, a new issue with the label `I11-deprecation` needs to be created for correct tracking. +To start a deprecation process, a new issue with the label `T15-deprecation` needs to be created for correct tracking. Then these are the actions to take: ## Hard deprecate by adding a warning message