From Fedora Project Wiki
(submitting change to fesco)
(Link "We integrate programming language stack ecosystems" in "Alignment with Community Initiatives")
Line 78: Line 78:
* Trademark approval: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)


* Alignment with Community Initiatives: None
* Alignment with Community Initiatives: No Community Initiatives yet but several features (declarative build system support, dynamic spec generation and spec local dep generators) are relevant for [https://discussion.fedoraproject.org/t/objective-review-we-integrate-programming-language-stack-ecosystems/79289 Objective Review: We integrate programming language stack ecosystems]
<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->
<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->



Revision as of 07:50, 5 April 2024

RPM 4.20

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

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
  • 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

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