Changes/PyTorch2.4

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

= Change Proposal Name = PyTorch 2.4

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 PyTorch to the latest upstream version 2.4

Owner

• Name: Tom Rix
• Email: trix@redhat.com

Current status

• Targeted release: Fedora Linux 41
• Last updated: 2024-07-17
• [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 the base Fedora PyTorch from 2.2 to the latest upstream 2.4. The big change for 2.4 is the integration with the ROCm stack to provide open accelerated AI on AMD GPU's.

Benefit to Fedora

Fedora AI is keeping pace with the fast moving AI by updating PyTorch to match what is evaluable *right now* in the upsteam with features needed to do real AI development for open source.

Scope

• Proposal owners:

Update base to 2.4 when upstream releases.

• Other developers:

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

Early Testing (Optional)

Do you require 'QA Blueprint' support? Y/N

How To Test

Requires AMD GPU Run the PyTorch examples and other package ex/ python-torchvision unit tests.

Contingency Plan

Fedora currently ships with the latest public 2.3 release with all of the accelerated features.

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