Re: 7.2 in experimental; next steps?
On 2026-07-07 12:38, Talha Havadar wrote:
> I also agree with having documentation about the items you mentioned
> [1,4] where should we start putting those?
In the past, we used the team wiki for our release plans, see 5.7 and
6.1 pages of
https://salsa.debian.org/rocm-team/community/team-project/-/wikis/home
For a policy document though, I think a Markdown file in some team
repository would be better. There's a clearer history, cleaner
versioning, and most importantly changes can be proposed and discussed
through MR.
Or perhaps Christian B. has a better idea? He's our documentation pro :)
Best,
Christian
> Christian Kastner <ckk@debian.org <mailto:ckk@debian.org>>, 7 Tem 2026
> before I get into details, I'd like to propose that a policy document be
> created that documents at least the following:
>
> 1. Supported architecture lists
> 2. Updating the ROCm stack (experimental, unstable, Ubuntu)
> 3. Triggering/shipping changes to the supported architecture list
> 4. QA thresholds
Reply to: