Changes/ZlibNG-2.2

Update Zlib-ng to version 2.2.x

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 Zlib-ng on Fedora 42 to version 2.2.x. Currently, Fedora distributes Zlib-ng 2.1.7.

Owner

• Name: Tulio Magno Quites Machado Filho, Lukas Javorsky
• Email: tuliom@redhat.com, ljavorsk@redhat.com

Current status

• Targeted release: Fedora Linux 42
• Last updated: 2024-09-24
• [Announced]
• [<will be assigned by the Wrangler> Discussion thread]
• FESCo issue: <will be assigned by the Wrangler>
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Update zlib-ng to the latest version from branch 2.2.x. Currently, that's version 2.2.2, but it could change until the release considering that updates on the same branch are expected to be API/ABI stable.

Benefit to Fedora

Major version 2.2.x provides new optimizations, rewrites deflate memory allocation and improves the buildsystem and tests.

More details are available in the following pages:

• https://github.com/zlib-ng/zlib-ng/releases/tag/2.2.0
• https://github.com/zlib-ng/zlib-ng/releases/tag/2.2.1
• https://github.com/zlib-ng/zlib-ng/releases/tag/2.2.2

Scope

• Proposal owners: New zlib-ng packages will be built. SONAME will not change.

• Other developers: Check if their packages continue to work as expected and report issues using Bugzilla.

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with the Fedora Strategy:

Upgrade/compatibility impact

Considering that API and ABI are expected to be kept the same, no impacts are expected.

Early Testing (Optional)

Do you require 'QA Blueprint' support? N

An initial test has already been executed on Copr.

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)