Update manpages for 8.0 #36447
Update manpages for 8.0 #36447
Conversation
ghost
added
|
This is targeted for 8.0.2xx, but the distros don't build that version, right? So if the distros want updated man pages we'd need this to target release/8.0.1xx? It's late in the cycle but we could try to get it in for GA or the first servicing of it was important to source-build partners. |
am11
force-pushed
the
feature/docs/manpage-update
branch
from
040608c to
307403d
Compare
|
@baronfel, I based off of latest branch of release/8 series, unaware of its purpose. :)
Perhaps @dotnet/distro-maintainers may know about the desired timeline? Note that changes for dotnet/docs repo pertaining to dotnet(1) and its commands are not too frequent, so it maybe alright to do it now (three weeks ahead of the release date). It would be great if this manpage update is somehow automated where we have source-build release tagging infra, so it is not forgotten. e.g. "one day before the scheduled release of next major version, dotnet bot to post this pull request in dotnet/sdk repo with changes produced by |
|
Getting this into 8.0 would be great. I don't think it's important/urgent enough to respin the GA if that's already been finalized, though. First servicing, for example, should be just fine. |
|
+1 on @omajid's response |
|
Thanks for the clarification, folks! Let's aim for first servicing then. |
This repo contains man pages. They are generated from another repo, and need to be updated manually. Generally, someone updates them once a year or so, and often it's too late for GA: - dotnet#36447 - dotnet#29032 So automate the update using GitHub Actions.
This repo contains man pages. They are generated from another repo, and need to be updated manually. Generally, someone updates them once a year or so, and often it's too late for GA: - dotnet#36447 - dotnet#29032 So automate the update using GitHub Actions.
This repo contains man pages. They are generated from another repo, and need to be updated manually. Generally, someone updates them once a year or so, and often it's too late for GA: - dotnet#36447 - dotnet#29032 So automate the update using GitHub Actions.
This repo contains man pages. They are generated from another repo, and need to be updated manually. Generally, someone updates them once a year or so, and often it's too late for GA: - dotnet#36447 - dotnet#29032 So automate the update using GitHub Actions.
This repo contains man pages. They are generated from another repo, and need to be updated manually. Generally, someone updates them once a year or so, and often it's too late for GA: - dotnet#36447 - dotnet#29032 So automate the update using GitHub Actions.
This repo contains man pages. They are generated from another repo, and need to be updated manually. Generally, someone updates them once a year or so, and often it's too late for GA: - dotnet#36447 - dotnet#29032 So automate the update using GitHub Actions.
7 participants
Used
documentation/manpages/tool/run_docker.shto sync manpages with latest dotnet/docs.Targeting
release/8.0.2xxrelease/8.0.1xx branch.Customer Impact
Linux packages will contain up-to-date manpages that align with the tools we actually shipped in the release.
Risk
Low, only updates documentation files, and these are updated from learn.ms.com.
Regression
No, but we may want to look into adding this to our release checklist prior to each quarterly/major release to prevent this brief lag.