[new product] chef-infra-client

[nperez60]

add new product chef-client

[nperez60]

Seems good to me

[tas50]

Glad to see someone adding this project. As a past Chef developer and later the PM for the client I would call out that the project name hasn't been Chef Client for a number of years. This should be updated to be Chef Infra Client, which is the name of the project currently. Other than that it looks great.

[nperez60]

@tas50 thanks for your feedback, I updated the PR

[marcwrobel]

Still draft or ready for review ?

[nperez60]

@marcwrobel, I am waiting to have some time to work on #4425
I will put this PR in ready for review when I find a solution for the other one

[tas50]

There's a lot of release dates here that still need to get updated. I think some of this is confusion on how Chef's version numbers work. When I used to do these releases we would cutover master/main to the new version sometime in January to start prepping things for our yearly April release. The first commit afer this bump will become say 17.0.0 and every release after this continues to bump the minor version. This was done as each commit builds a package that users can download from the current build repo. When we were happy with things and wanted to do the release we'd just tag a build "stable" and ship it. That means for something like 16.0 the first released version is actually 16.0.275 in May when the 16.0.0 tag is all the way back in Jan. TLDR: Don't trust the github tags.

[nperez60]

@tas50 thanks for the feedback / sources
@marcwrobel do I need to update each release manually or we agree that the script in endoflife-date/release-data#328 will update each release if needed ?

[nperez60]

Hi, let me know if any modifications are needed

[usta]

@marcwrobel is everthing ok for this PR ? is it ready to land or not ?