-
Notifications
You must be signed in to change notification settings - Fork 28
ug: el2g: add warning about deprecation #758
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
Conversation
Docs for 042c2a1 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2773/docs/artifacts/html/index.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is fine. i wouldn't even mind just deleting this - the next LmP could be months from now and we already don't support it.
My concern with deleting immediately is that folks won't know we stopped supporting this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor little tweaks suggested, but it LGTM.
source/user-guide/el2g.rst
Outdated
@@ -3,6 +3,10 @@ | |||
Integrating NXP EdgeLock 2GO | |||
============================ | |||
|
|||
.. warning:: | |||
|
|||
The content in this page is not supported in current LmP. This page will be deleted in the next LmP release (v96). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The content in this page is not supported in current LmP. This page will be deleted in the next LmP release (v96). | |
The content on this page is not supported by the current LmP. This page will be deleted with the next release (v96). |
@mike-scott @doanac @vanmaegima I think keeping this page with the added warning until v96 is wise. As mike-scott mentioned, it lets folks know it is no longer supported. I worry about someone googling it, and ending up being directed to a outdated version...not that this will prevent that, but perhaps will help reduce that from happening? Additionally, when we do delete this—or any feature page—we may want to add a redirect...perhaps to a generic, non-indexed page stating it was deprecated, and a link back to the home page? I can do this when it comes time, if we think it would be a good idea. |
This is not supported since Oct 1st 2024. Signed-off-by: Vanessa Maegima <vanessa.maegima@foundries.io>
042c2a1
to
b41dbbc
Compare
@kprosise I've addressed your comments |
Docs for b41dbbc are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2774/docs/artifacts/html/index.html |
This is not supported since Oct 1st 2024.
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness
Overview
Why merge this PR? What does it solve?
Checklist
make linkcheck
.-s, --signoff
).-S, --gpg-sign
).Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.