dnf5 icon indicating copy to clipboard operation
dnf5 copied to clipboard

Release dnf5-5.2.0.0

Open kontura opened this issue 1 year ago • 9 comments

Since we need to do API and ABI changes we will have to make a new major version release update.

This issue should track all the required/planned changes:

  • [x] https://github.com/rpm-software-management/dnf5/issues/1025
  • [x] https://github.com/rpm-software-management/dnf5/pull/1085
  • [x] https://github.com/rpm-software-management/dnf5/pull/1087
  • [x] https://github.com/rpm-software-management/dnf5/pull/1216
  • [x] https://github.com/rpm-software-management/dnf5/issues/1189
  • [x] https://github.com/rpm-software-management/dnf5/issues/1072
  • [x] Drop deprecated API
    • [x] https://github.com/rpm-software-management/dnf5/pull/1294
    • [x] https://github.com/rpm-software-management/dnf5/issues/1322

Follow-ups:

  • [x] https://github.com/rpm-software-management/dnf5/pull/1421

kontura avatar Dec 13 '23 08:12 kontura

"Dnf5-6.0.0" sorry, I can't help, but this won't stop fascinating me.

voxik avatar Dec 13 '23 16:12 voxik

I am proposing to add use_glob{true} to ResolveSpecSettings. Such a change will brake ABI.

j-mracek avatar Dec 14 '23 10:12 j-mracek

"Dnf5-6.0.0" sorry, I can't help, but this won't stop fascinating me.

We should have just renamed the old project to "dnf4" and kept calling this "dnf" but here we are. :)

Conan-Kudo avatar Jan 04 '24 13:01 Conan-Kudo

We are also considering changing the versioning to add one more number and keep the 5. So the new breaking version would be dnf5-5.2.0.0.

The nevras still do compare correctly: dnf5-5.2.0.0 > dnf5-5.1.0.

kontura avatar Jan 15 '24 12:01 kontura

OK, I believe we can proceed with merging this to main.

jan-kolarik avatar Apr 05 '24 11:04 jan-kolarik

Do you think we have sufficient API coverage for me to implement a PackageKit backend using libdnf5 based on what we have for the current dnf backend? https://github.com/PackageKit/PackageKit/tree/main/backends/dnf

Conan-Kudo avatar Apr 05 '24 12:04 Conan-Kudo

Do you think we have sufficient API coverage for me to implement a PackageKit backend using libdnf5 based on what we have for the current dnf backend? https://github.com/PackageKit/PackageKit/tree/main/backends/dnf

I believe so, but I'll try to go through it this week to verify. However, I'm curious and a bit confused because I thought PackageKit is already only in maintenance mode, and new plugins for package manager frontends like GNOME Software, KDE, dnfdragora, etc., are now being developed using the dnf5daemon API.

jan-kolarik avatar Apr 08 '24 08:04 jan-kolarik

Do you think we have sufficient API coverage for me to implement a PackageKit backend using libdnf5 based on what we have for the current dnf backend? https://github.com/PackageKit/PackageKit/tree/main/backends/dnf

So, I went through the existing PackageKit backend for dnf, and I didn't find any features lacking in dnf5. However, it's possible I overlooked something as the codebase is pretty extensive. In any case, if you encounter any challenges implementing specific use cases with the DNF5 API, don't hesitate to reach out. :slightly_smiling_face:

jan-kolarik avatar Apr 17 '24 12:04 jan-kolarik

However, I'm curious and a bit confused because I thought PackageKit is already only in maintenance mode

"Maintenance mode" doesn't mean nobody works on it. That doesn't mean it's dead. It means there are currently no new features planned (nobody has asked for any either).

new plugins for package manager frontends like GNOME Software, KDE, dnfdragora, etc., are now being developed using the dnf5daemon API.

Only dnfdragora is using dnf5daemon because it previously used dnfdaemon. Everyone else still uses PackageKit.

Conan-Kudo avatar Apr 17 '24 12:04 Conan-Kudo