From Fedora Project Wiki
(→‎Scope: Make more clear that we need to fix the packages first)
(adding release notes tracker)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
= RPM 4.20 =
= RPM 4.20 =


{{Change_Proposal_Banner}}


== Summary ==
== Summary ==
Line 15: Line 14:


== Current status ==
== Current status ==
[[Category:ChangeReadyForFesco]]
[[Category:ChangeAcceptedF41]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 34: Line 33:
* [https://discussion.fedoraproject.org/t/f41-change-proposal-rpm-4-20-system-wide/109573 Discussion thread]
* [https://discussion.fedoraproject.org/t/f41-change-proposal-rpm-4-20-system-wide/109573 Discussion thread]
* FESCo issue: [https://pagure.io/fesco/issue/3188 #3188]
* FESCo issue: [https://pagure.io/fesco/issue/3188 #3188]
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2276421 #2276421]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/107 #107]





Latest revision as of 16:51, 2 October 2024

RPM 4.20

Summary

Update RPM to the up coming 4.20 release.

Owner


Current status


Detailed Description

RPM 4.20 contains various improvements over previous versions.

The 4.20 alpha release is expected in late March/early April and the final release is expected in time for the Fedora 41 release cycle as usual.

Feedback

Benefit to Fedora

This release comes with many improvements. It opens the possibility for Fedora to adopt the new major features mentioned above.

Scope

  • Proposal owners:
    • Release RPM 4.20 alpha
    • Rebase RPM in rawhide
    • Assist with dealing with incompatibilities by working with a provenpackager to get the affected packages fixed before pushing the alpha release into rawhide.
  • Other developers:
    • Test new release, report issues and bugs
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

%patchN

The %patchN macro syntax (where N is a patch number) is now obsolete and will produce a build error (instead of an warning in 4.19). Use %patch N (or %patch -P N) instead.

This affects currently > 1000 spec files. They need to get fixed before pushing the alpha into rawhide. This compatibility issue probably needs to go into the release notes

How To Test

Rpm receives a thorough and constant testing via every single package build, system installs and updates. New features can be tested specifically as per their documentation.

User Experience

There are no major differences in the normal user experience.

Dependencies

Contingency Plan

  • Contingency mechanism: Revert back to RPM 4.19
  • Contingency deadline: Beta freeze
  • Blocks release? No

Documentation

Release notes at https://rpm.org/wiki/Releases/4.20.0 (still tbd) and reference manual at https://rpm-software-management.github.io/rpm/manual/


Release Notes