Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wip: new: Notice of Important Changes and Deprecations page #1176

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

incertum
Copy link
Contributor

@incertum incertum commented Oct 7, 2023

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

/kind event

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area community

What this PR does / why we need it:

Add a dedicated page to set expectations regarding significant project changes or deprecations.

@leogr

Official deprecation policies will be published separately by @leogr.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@poiana
Copy link

poiana commented Oct 7, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: incertum
Once this PR has been reviewed and has the lgtm label, please assign vjjmiras for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana poiana requested review from mstemm and vjjmiras October 7, 2023 03:09
@poiana poiana added the size/M label Oct 7, 2023
@leogr
Copy link
Member

leogr commented Nov 28, 2023

/assign

@leogr
Copy link
Member

leogr commented Jan 26, 2024

@mikegcoleman can you take a look at this please? 🙏

@incertum
Copy link
Contributor Author

incertum commented Jan 26, 2024

Let's hold until the formal deprecation policies are out? Subsequently rewrite / adjust so it matches the "Features Adoption and Deprecation Policies".

@leogr
Copy link
Member

leogr commented Jan 26, 2024

Let's hold until the formal deprecation policies are out? Subsequently rewrite / adjust so it matches the "Features Adoption and Deprecation Policies".

👍

/hold

@incertum incertum changed the title new: Notice of Important Changes and Deprecations page wip: new: Notice of Important Changes and Deprecations page Feb 21, 2024
@leogr
Copy link
Member

leogr commented Mar 26, 2024

cc @LucaGuerra

@leogr
Copy link
Member

leogr commented Mar 26, 2024

@poiana
Copy link

poiana commented Jun 24, 2024

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
Copy link
Member

leogr commented Jun 24, 2024

/remove-lifecycle stale

🤯 I totally lost track of this, sorry.

/assign

@incertum
Copy link
Contributor Author

Even I have to get back to it ... no worries.

@incertum
Copy link
Contributor Author

incertum commented Aug 8, 2024

Let's check on this in the fall, ok? Thanks.

@poiana
Copy link

poiana commented Nov 6, 2024

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
Copy link
Member

leogr commented Nov 6, 2024

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants