New Product - Chef Workstation #7661
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tas50
force-pushed
the
tas50/chef-workstation
branch
from
9c28d4e to
c0369fc
Compare
marcwrobel
force-pushed
the
tas50/chef-workstation
branch
from
c0369fc to
38ded31
Compare
marcwrobel
requested changes
Jul 6, 2025
There was a problem hiding this comment.
Thanks for this contribution @tas50. Here are my first comments.
products/chef-workstation.md
Outdated
|
|
||
| > [Chef Workstation](https://docs.chef.io/workstation/) gives you everything you need to get started with Chef - | ||
| > ad hoc remote execution, remote scanning, configuration tasks, cookbook creation tools as well as robust | ||
| > dependency and testing software - all in one easy-to-install package. |
There was a problem hiding this comment.
Could you add a description of the release / support policy (similar to https://endoflife.date/chef-infra-server for example) ?
products/chef-workstation.md
Outdated
|
|
||
| --- | ||
|
|
||
| > [Chef Workstation](https://docs.chef.io/workstation/) gives you everything you need to get started with Chef - |
There was a problem hiding this comment.
We try to avoid being too "commercial" and detailed in the description, could you provide a shorter and more neutral description. See https://github.com/endoflife-date/endoflife.date/wiki/Style-Guide#text for some guidelines.
There was a problem hiding this comment.
I took a stab at a more neutral version
Add Chef Workstation using release dates from https://discourse.chef.io/ and https://docs.chef.io/release_notes_workstation/ As an ex-PM and engineer on this project I think their states support structure is a bit of a lie, but it's what they claim. According to their site they fully support 2024 and 2025, but they only roll forward so any issue in 2024 (CVE or bug) is always going to be met with a support request that you upgrade to the latest. "Technically" 2024.x.x is in active support though so I marked it as such. Signed-off-by: Tim Smith <[email protected]>
tas50
force-pushed
the
tas50/chef-workstation
branch
from
38ded31 to
bf3614a
Compare
This should probably get added in the future, but it's not there now Signed-off-by: Tim Smith <[email protected]>
Signed-off-by: Tim Smith <[email protected]>
Signed-off-by: Tim Smith <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Chef Workstation using release dates from https://discourse.chef.io/ and https://docs.chef.io/release_notes_workstation/
Note: As an ex-PM and engineer on this project I think their stated support structure is a bit of a lie, but it's what they claim. According to their site they fully support both 2024 and 2025, but they only roll forward so any issue in 2024 (CVE or bug) is always going to be met with a support request that you upgrade to the latest. "Technically" 2024.x.x is in active support though so I marked it as such.