Create a deprecation policy document

[incertum]

Create a formal deprecation policy document in addition to a page on the official Falco website.

@leogr

Tasks

Beta Give feedback

1. docs(proposal): 20231220-features-adoption-and-deprecation.md falco#2986
   approved area/proposals dco-signoff: yes kind/design kind/documentation lgtm release-note-none size/L +8
   

   

[incertum]

/assign @leogr

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

see falcosecurity/falco#2986

[leogr]

Since GitHub has no special feature for the deprecation policy (compared to other community-related docs like the contribution guide and the security policy), we will not get any benefit to duplicate the content under falcosecurity/.github. We should instead link the official policy (once it gets published on the website).

So
/close

Feel free to reopen this if you disagree!

[poiana]

@leogr: Closing this issue.

In response to this:

Since GitHub has no special feature for the deprecation policy (compared to other community-related docs like the contribution guide and the security policy), we will not get any benefit to duplicate the content under falcosecurity/.github. We should instead link the official policy (once it gets published on the website).

So
/close

Feel free to reopen this if you disagree!

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.