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

Review and finalize the DNF vs DNF5 changes documentation page #1290

Open
2 of 3 tasks
jan-kolarik opened this issue Mar 4, 2024 · 2 comments
Open
2 of 3 tasks

Review and finalize the DNF vs DNF5 changes documentation page #1290

jan-kolarik opened this issue Mar 4, 2024 · 2 comments
Assignees
Labels
Priority: HIGH Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take
Milestone

Comments

@jan-kolarik
Copy link
Member

jan-kolarik commented Mar 4, 2024

Focusing mainly on the CLI part.

Doc pages here: https://dnf5.readthedocs.io/en/latest/changes.html.

@jan-kolarik jan-kolarik added the Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take label Mar 11, 2024
@jan-kolarik
Copy link
Member Author

Also we should think about generalizing the current dnf4 vs dnf5 changes doc section to include also details how the systems using dnf4 will migrate to dnf5, like explicitly describing if there are any manual steps they can take to preserve existing configuration or system state, what is done automatically, what is not supported, etc.

@jan-kolarik
Copy link
Member Author

Also we should think about generalizing the current dnf4 vs dnf5 changes doc section to include also details how the systems using dnf4 will migrate to dnf5, like explicitly describing if there are any manual steps they can take to preserve existing configuration or system state, what is done automatically, what is not supported, etc.

I have moved this to a separate ticket: #1739.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: HIGH Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take
Projects
Status: In Progress
Development

No branches or pull requests

1 participant