feat(developermanual): move new and deprecated APIs to dedicated pages#14183
feat(developermanual): move new and deprecated APIs to dedicated pages#14183ChristophWurst wants to merge 1 commit intomasterfrom
Conversation
Signed-off-by: Christoph Wurst <1374172+ChristophWurst@users.noreply.github.com>
ChristophWurst
requested review from
DaphneMuller,
Rello,
artonge,
blizzz,
juliusknorr and
nickvergessen
| Deprecations | ||
| ============ | ||
|
|
||
| In order to improve our platform we are phasing out some APIs. Deprecated APIs are not removed before ???, |
There was a problem hiding this comment.
Right. That brings up the old discussion about what we promise as deprecation period. IIRC it was three years. Should I write it down or skip?
| .. _deprecated-apis: | ||
|
|
||
| ============ | ||
| Deprecations |
There was a problem hiding this comment.
Should also be a file per major for better linking?
There was a problem hiding this comment.
I don't like it. This will get messy quickly. It also makes it impossible to have a stable link as every major release will have the version embedded in the URL.
There was a problem hiding this comment.
We could collect all current deprecations on this page. First we list the new ones, then there's the rest. When a deprecation is finally removed, it's also removed from the page.
It's equally messy, but there is one stable URL for the page.
There was a problem hiding this comment.
it's also removed from the page.
Could have a second page then for those?
2 participants
This is the cleaned-up version of #14180.
I did not move the upgrade doc(s) yet as I'm a bit unsure how to do it without link breakage and how to only list the newest one and hide the old ones.
🖼️ Screenshots