deprecated and removed features

[eedugon]

hi team!

When certain feature / page is deprecated for example in 7.16.0 and removed in 9.0.0 it would be great to show it using the applies section of the frontmatter.

Something like:

  stack: deprecated 7.16.0
  stack: removed 9.0.0

What do you think?

I don't think we always follow the rule about a deprecated feature being removed in the next major, but I could be wrong.

[shainaraskas]

I think we need to support one tag per "state" - e.g. you couldn't have two deprecated stack tags but you could have a deprecated and an unavailable

[eedugon]

Yes, that might be an option.

About the naming (unavailable vs removed), unavailable might mean that something doesn't exist in certain deployment type or version, and removed would indicate that before version X existed, and after it doesn't.

But maybe that doesn't add much benefit.

[lcawl]

IMO we don't need to add the v8 and earlier deprecation details to the current content set (since that information still exists in the old docs). But I agree that going forward it'll be useful to show both when something became deprecated and when it was removed (for as long as both those versions are still in support).