Feature Overview:

We are moving the responsibility for building “torch wheels” from the Accelerator Enablement team to the PyTorch team to remove some friction in that build process and speed up delivery.

Product(s) associated:

All uses of torch.

Goals:

• Place responsibility for building the set of wheels from the torch community on the team with the most expertise.
• Enable that team to use the best tool for the job.
• Continue to build for all accelerator variants supported in the product.

Requirements:

1. Builds must be compatible with other wheels built by AE and DP using the wheel builder image. (Build for RHEL, link against library versions in the base images, etc.)
2. We establish a process for the PyTorch team to recognize updated dependencies and make the AE and DP teams aware so they can perform updates.

Done - Acceptance Criteria:

1. Builds for tagged releases of torch are published to a package index visible to the rest of the wheel build pipelines for use in image builds.
2. Nightly build jobs try to build using the same tools and the HEAD of the most recent development branch of torch, with monitored notifications for failures.

Use Cases - i.e. User Experience & Workflow:
Include use case diagrams, main success scenarios, alternative flow scenarios.

Out of Scope:

• We will not move all accelerator-enabled builds to the torch team.
• We will work on making the upstream build tools provide hermetic over time.

Documentation Considerations :

N/A