CI: deprecate releases - #448
Conversation
rockdreamer
left a comment
rockdreamer
left a comment
There was a problem hiding this comment.
LGTM, but would be good to consider removing the branch altogether
rockdreamer
left a comment
rockdreamer
left a comment
There was a problem hiding this comment.
Nice, though it looks like you'll have to rebase 👍
| [**Beta** state](#support-levels) and the | ||
| specification for the rest of SME is in | ||
| [**Beta** state](#current-status-and-anticipated-changes). The | ||
| [**Beta** state](#support-levels). The |
There was a problem hiding this comment.
Can I ask you to clean-up this once this commit lands? This should be simplified and probably should also mention SME2p2 and SME2p3
There was a problem hiding this comment.
Yes, let's do a round of updates.
|
|
||
| The specification for B16B16 is in | ||
| [**Alpha** state](#current-status-and-anticipated-changes) and might change or be | ||
| [**Alpha** state](#support-levels) and might change or be |
There was a problem hiding this comment.
once this patch lands it is worth to check if this is still true, ACLE for B16B16 was defined some time ago so it probably can be bumped to beta
|
|
||
| This section is in | ||
| [**Alpha** state](#current-status-and-anticipated-changes) and might change or be | ||
| [**Alpha** state](#support-levels) and might change or be |
There was a problem hiding this comment.
same here worth to check if this can be bumped to beta once this patch landed
| #### Structured sparsity outer product intrinsics | ||
|
|
||
| The specification for SME is in | ||
| [**Alpha** state](#current-status-and-anticipated-changes) and may change or be |
There was a problem hiding this comment.
this should be changed after this patch lands, as the SME one and SME2 are for sure at beta level
|
|
||
| The specification for B16B16 is in | ||
| [**Alpha** state](#current-status-and-anticipated-changes) and might change or be | ||
| [**Alpha** state](#support-levels) and might change or be |
There was a problem hiding this comment.
worth to check if this can be bumped to beta once this patch landed
| process gives users earlier access to new features, clarifications, and | ||
| corrections. | ||
|
|
||
| The PDF version of the documents can be retrieved from the |
There was a problem hiding this comment.
does this refer to the current specification or the legacy releases? I thought that the pdf's for the current version will be accessible from https://arm-software.github.io/acle/ as it its today.
There was a problem hiding this comment.
Both. legacy releases will continue to exist in github's releases page, and every new commit will generate one entry there as well.
Also the pages will continue linking to the latest versions.
There was a problem hiding this comment.
What is the rationale behind keeping the rolling pdfs also on https://github.com/ARM-software/acle/releases ?
I was thinking that https://arm-software.github.io/acle/ would be enough am I missing something?
There was a problem hiding this comment.
That's just my understanding from the requirements and discussions. Keeping the artifacts in the releases page gets you quick access to any version, and the webpage also points to it.
| process gives users earlier access to new features, clarifications, and | ||
| corrections. | ||
|
|
||
| The PDF version of the documents can be retrieved from the |
There was a problem hiding this comment.
What is the rationale behind keeping the rolling pdfs also on https://github.com/ARM-software/acle/releases ?
I was thinking that https://arm-software.github.io/acle/ would be enough am I missing something?
| * Moved the [Future directions](#future-directions) chapter to the end. | ||
| * Added a description of support levels in [Current Status and | ||
| Anticipated Changes](#current-status-and-anticipated-changes). | ||
| * Added a description of #support-levels. |
There was a problem hiding this comment.
In the pdf this is rendered as "Added a description of #support-levels." I guess the intent was to have a redirection so it should perhaps be:
Added a description of [support levels](#support-levels).
| * Sorted the items in [References](#references). | ||
| * Changed the wording of **Beta** in [Current Status and Anticipated | ||
| Changes](#current-status-and-anticipated-changes). | ||
| * Changed the wording of **Beta** in #support-levels. |
There was a problem hiding this comment.
same as above, perhaps it should be
* Changed the wording of **Beta** in [support levels](#support-levels).
| intrinsics. | ||
| * Added [**Alpha**](#support-levels) | ||
| support for SVE2.3 (FEAT_SVE2p3) and SME2.3 shift right narrow intrinsics. | ||
| * Bumped armv9.6 intrinsics implementation to [**Beta**](#support-levels) |
There was a problem hiding this comment.
sorry for noticing it late, I guess "bumped" is fine to use in commits but probably not the best fit for specification, can this be changed to:
"Changed the support level for the Armv9.6 intrinsics implementation to Beta"
5 participants
Introduce wording of deprecation of quarterly releases in favor of continuously updated specifications.