CI: deprecate releases by rgwott · Pull Request #448 · ARM-software/acle

rgwott · 2026-07-20T10:35:11Z

Introduce wording of deprecation of quarterly releases in favor of rolling releases.

name: Pull request
about: CI reorganization.

Thank you for submitting a pull request!

If this PR is about a bugfix:

Please use the bugfix label and make sure to go through the checklist below.

If this PR is about a proposal:

We are looking forward to evaluate your proposal, and if possible to
make it part of the Arm C Language Extension (ACLE) specifications.

We would like to encourage you reading through the contribution
guidelines, in particular the section on submitting
a proposal.

Please use the proposal label.

As for any pull request, please make sure to go through the below
checklist.

Checklist: (mark with X those which apply)

If an issue reporting the bug exists, I have mentioned it in the
PR (do not bother creating the issue if all you want to do is
fixing the bug yourself).
[Should be resolved with the other PRs] I have added/updated the SPDX-FileCopyrightText lines on top
of any file I have edited. Format is SPDX-FileCopyrightText: Copyright {year} {entity or name} <{contact informations}>
(Please update existing copyright lines if applicable. You can
specify year ranges with hyphen , as in 2017-2019, and use
commas to separate gaps, as in 2018-2020, 2022).
[Should be resolved with the other PRs] I have updated the Copyright section of the sources of the
specification I have edited (this will show up in the text
rendered in the PDF and other output format supported). The
format is the same described in the previous item.
I have run the CI scripts (if applicable, as they might be
tricky to set up on non-*nix machines). The sequence can be
found in the contribution
guidelines. Don't
worry if you cannot run these scripts on your machine, your
patch will be automatically checked in the Actions of the pull
request.
X ] I have added an item that describes the changes I have
introduced in this PR in the section Changes for next
release of the section Change Control/Document history
of the document. Create Changes for next release if it does
not exist. Notice that changes that are not modifying the
content and rendering of the specifications (both HTML and PDF)
do not need to be listed.
When modifying content and/or its rendering, I have checked the
correctness of the result in the PDF output (please refer to the
instructions on how to build the PDFs
locally).
[Removed in the other PR] The variable draftversion is set to true in the YAML header
of the sources of the specifications I have modified.
Please DO NOT add my GitHub profile to the list of contributors
in the README page of the project.

CarolineConcatto · 2026-07-20T15:48:52Z

+| M                | 21 February 2025  | 2024Q4                                            |
+| N                | 06 June 2025      | 2025Q2                                            |
+| O                | 15 May 2026       | 2026Q1                                            |
+| O                | 15 May 2026       | 2026Q1                                            |


is this repeated?

Maybe we should do something like this:

O 15 May 2026 2026Q1 Final quarterly release

After the table, add a short section:

Continuous publication

Beginning after 2026Q1, this specification is published continuously from the
main branch. Each published version is identified by its Git commit hash and
commit date.

See Changes after 2026Q1 for subsequent changes.

Yes, the template and "final" md file are both in the repo :/

@rockdreamer I guess she meant the duplicate line in the table.
Fixed.

CarolineConcatto · 2026-07-20T16:10:54Z

+| N                | 06 June 2025      | 2025Q2                                            |
+| O                | 15 May 2026       | 2026Q1                                            |
+| O                | 15 May 2026       | 2026Q1                                            |
+| Rolling releases | Every commit      | See [Changes after 2026Q1](#changes-after-2026q1) |


Maybe we should do something like this:

O 15 May 2026 2026Q1 Final quarterly release

After the table, add a short section:

Continuous publication

Beginning after 2026Q1, this specification is published continuously from the
main branch. Each published version is identified by its Git commit hash and
commit date.

See Changes after 2026Q1 for subsequent changes.

Final quarterly release

We can dot it, but I would rather not, because the structure of this same table is different in the other files.

Oh, just saw this. See also my proposal in main/acle.md
Happy with either this wording or mine above for the short section, but I'd rather not add a table row.

rockdreamer

LGTM, but would be good to consider removing the branch altogether

mgabka · 2026-07-22T13:57:09Z

-      introduced in this PR in the section **Changes for next
-      release** of the section **Change Control**/**Document history**
-      of the document. Create **Changes for next release** if it does
+      introduced in this PR in the section **Changes after ACLE Q1 2026**


The section "Changes after ACLE Q1 2026" is a temporary workaround, to unblock further development, I am not sure we want to keep it like that.
We should perhaps sort this problem first before merging this PR.

Sure, I am open to suggestions in phrasing.

"Changes in the current year" section that we rename to "Changes during 20xx" and re-add at the bottom of the changelog roughly once a year?

mgabka · 2026-07-22T14:01:58Z

+| 2025Q2           | 06 June 2025      | Arm    | See [Changes between ACLE Q4 2024 and ACLE Q2 2025](#changes-between-acle-q4-2024-and-acle-q2-2025)                  |
+| 2025Q3           | 14 November 2025  | Arm    | See [Changes between ACLE Q2 2025 and ACLE Q3 2025](#changes-between-acle-q2-2025-and-acle-q3-2025)                  |
+| 2026Q1           | 15 May 2026       | Arm    | See [Changes between ACLE Q3 2025 and ACLE Q1 2026](#changes-between-acle-q3-2025-and-acle-q1-2026)                  |
+| Rolling releases | Every commit      | Arm    | See [Changes after ACLE Q1 2026](#changes-after-acle-q1-2026)                                                        |


We are not aiming for more releases, so perhaps "Single current version" is a good phrase to use?

Do you mean in place of "Rolling releases"?

Rather than add a line in the table, how about adding a separate line stating: "After the 2026Q1 release, the project has moved to a rolling release model with the state of the main branch being authoritative.".
No need to add a link to the changelog.
Likewise for the tables below.

mgabka · 2026-07-22T14:05:30Z


 By submitting a pull request you are implicitly adhering to the
-[contribution agreement](#contribution-agreement)
+contribution agreement below.


why this needs to be changed? seems to not be related to the legacy releases?

The HTML anchor was broken. There are also others, but this was a low-hanging fruit for this PR.

rgwott added 3 commits July 20, 2026 10:52

Introduce phrasing informing of rolling releases

9b3f454

Fix document history tables for the remaining docs

d08d5fd

Remove "release date" info from acle and neon docs

9907dba

CarolineConcatto requested review from CarolineConcatto, mgabka, rockdreamer and vhscampos July 20, 2026 10:54

CarolineConcatto reviewed Jul 20, 2026

View reviewed changes

rockdreamer reviewed Jul 20, 2026

View reviewed changes

Comment thread CONTRIBUTING.md Outdated

rgwott added 3 commits July 21, 2026 10:39

Fix duplicate entry in tables

8bd474f

Fix PR template for new changelog section/phrasing

8763605

Remove reference to branch latest-release (to be deleted)

677bff5

mgabka reviewed Jul 22, 2026

View reviewed changes

Uh oh!

Conversation

rgwott commented Jul 20, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Continuous publication

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Continuous publication

Uh oh!

rgwott Jul 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rockdreamer left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

rgwott Jul 21, 2026 •

edited

Loading