Re: 5.7 Release Plan / Timeline?
pytorch and pytorch-cuda are in good shape now. I was looking into
the missing build dependencies for pytorch-rocm and then started
pushing 5.7.0 packages into experimental.
The packages in unstable is a little bit old. Pytorch upstream
build their nightly rocm packages against rocm 5.6.0, so I think
we will sooner or later bump the version as well.
Breadths: I'm still trying to catch up with the latest progress
for this stack. But my move will be predictable. I will go from
the bottom to to top along the dependency tree
https://salsa.debian.org/rocm-team/community/team-project
Every missing dependency for pytorch-rocm will be on my radar.
Planning: I plan first try to get MIOpen into experimental.
This path will require me to handle its dependencies as well.
pytorch-rocm does not build without miopen anyway.
Upgrading obstable: Yes. I'll need to figure them out in
experimental when upgrading the packages and catch up.
On Sun, 2023-09-17 at 18:54 +0200, Christian Kastner wrote:
> Hi Team,
>
> so the first 5.7 packages have already started to enter the archive,
> which I guess means we're skipping 5.6 (which I'm fine with).
>
> However, I think some discussion might be warranted first. For
> example,
> some things that have been on my mind are:
>
> * Breadth: what packages still missing from the stack?
>
> * Planning: we'll be repeating this process frequently, so we
> should
> at least take notes now, to streamline future upgrades. For
> example,
> process difficulty might vary by the order in which we upgrade
> packages.
>
> * Upgrading obstabcle, eg: [1]
>
> * Infrastructure: I was looking forward to seeing how this process
> runs through CI infra, to iron out the final bugs. To that end,
> it
> would help me if uploaders interact with the platform: what's not
> working for you, what's missing, etc.
>
> * etc.
>
> Best,
> Christian
>
> [1] https://lists.debian.org/debian-ai/2023/06/msg00108.html
>
Reply to: