CI: deprecate releases

.github/ISSUE_TEMPLATE/bug_report.md

@@ -21,8 +21,7 @@ useful for layout problems in the PDF or HTML pages.
 
 **Our commitment**
 
-We will work to solve the bug report in time for the upcoming
-release. However, we would like to encourage you to submit the fix
-yourself, if possible. If you intend to do so and this is your first
-contribution, we recommend reading our [contribution
-guidelines](https://github.com/ARM-software/acle/blob/main/CONTRIBUTING.md).
+We will review the reported bug and prioritize it with other project work.
+However, you can also submit a fix. If you intend to do so and this is your
+first contribution, we recommend reading our
+[contribution guidelines](https://github.com/ARM-software/acle/blob/main/CONTRIBUTING.md).

.github/PULL_REQUEST_TEMPLATE.md

@@ -50,12 +50,11 @@ Checklist: (mark with ``X`` those which apply)
       patch will be automatically checked in the Actions of the pull
       request.
 * [ ] 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.
+      introduced in this PR in section **Changes for year 20xx** (this year)
+      of section **Preface**/**About this document**.
+      Create **Changes for year 20xx** 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

CONTRIBUTING.md

@@ -8,12 +8,11 @@ title: Contribution Guidelines
 
 # Thank you for considering contributing!
 
-Contributions are always welcome. We accept [bug fixes](#bugs),
-[proposals and new ideas](#proposals-for-new-content), or simply [editorial
-improvements](#editorial-improvements).
+Contributions are always welcome. We accept bug fixes, proposals and new ideas,
+or simply editorial improvements.
 
 By submitting a pull request you are implicitly adhering to the
-[contribution agreement](#contribution-agreement)
+contribution agreement below.
 
 ## Bugs
 
@@ -52,36 +51,23 @@ the specifications and stores them in the folder `pdfs`.
 
 # Continuous integration
 
-The continuous integration bot executes the script:
-
-```
- ./build_with_docker.sh
-```
-
-PDFs are generated automatically in response to a pull request. You
-can download the PDFs in the `Actions` tab of any pull request.
+The continuous integration bot executes the script and generates PDFs
+automatically in response to a pull request. You can download the PDFs in the
+`Actions` tab of any pull request.
 
 An additional step uses
 [``markdown-link-check```](https://github.com/tcort/markdown-link-check)
 to check that all the links in the markdown files are resolving
 correctly.
 
-# Branches and pull requests.
-
-The branch `latest-release` is the release branch, which contains the
-code used to build the PDFs of the [latest official
-release](https://github.com/ARM-software/acle/releases/latest). The
-branch `latest-release` is also used to build the [website of the ACLE
-project](https://arm-software.github.io/acle).
+# Branches and pull requests
 
-New development (bug-fixes, proposals, extensions, and so on) is
-committed on the `main` branch. Therefore, please submit your
-PR against the branch `main`.
+Use branch `main` for bug fixes, proposals, extensions, and other development
+work. Submit all pull requests against `main`.
 
-It is good practice to track changes. In the section `Changes for next
-release`, please list any changes that you have made to the
-document. For an example, see [this
-PR](https://github.com/ARM-software/acle/pull/19).
+It is good practice to track changes. In section `Changes for year 20xx`,
+please list any changes that you have made to the document. As an example, see
+[this PR](https://github.com/ARM-software/acle/pull/443/changes).
 
 # Contribution agreement
 

README.md

@@ -15,16 +15,29 @@
 This repository contains the source material from which the
 specifications for the Arm C Language Extensions (ACLE) are derived.
 
-The latest release of the specifications can be browsed online at
-[arm-software.github.io/acle/](https://arm-software.github.io/acle/).
+Browse the current specifications on the
+[ACLE website](https://arm-software.github.io/acle/).
 
-The PDF version of the documents can be retrieved from the [latest
-release](https://github.com/ARM-software/acle/releases/latest) page.
+## Versioning
 
-The development version is stored on the branch `main` at
-[github.com/ARM-software/acle/](https://github.com/ARM-software/acle/),
-while the latest released version is tracked by the branch
-`latest-release`.
+Arm no longer publishes quarterly specification releases. We publish the current
+specification after each reviewed change merges into branch `main`. This
+process gives users earlier access to new features, clarifications, and
+corrections.
+
+The PDF version of the documents can be retrieved from the
+[releases](https://github.com/ARM-software/acle/releases) page.
+
+Branch `main` contains the current ACLE specification and ongoing development.
+
+## Legacy releases
+
+The [releases](https://github.com/ARM-software/acle/releases) page also contains
+the legacy quarterly releases through 2026Q1.
+
+Pre-GitHub versions of the documents were previously released on
+[Arm Developer](https://developer.arm.com), and are also hosted in this
+repository, in [Legacy releases](legacyreleases/README.md).
 
 ## Contributing
 
@@ -43,19 +56,18 @@ an email to arm.acle@arm.com.
 
 ## List of documents
 
-HTML version                                                                                                  | PDF version
----                                                                                                           | ---
-[Arm C Language Extensions](https://arm-software.github.io/acle/main/)                                        | [download](https://github.com/ARM-software/acle/releases/latest)
-[Morello Supplement to the Arm C Language Extensions](https://arm-software.github.io/acle/morello/)           | [download](https://github.com/ARM-software/acle/releases/latest)
-[Arm MVE Intrinsics](https://arm-software.github.io/acle/mve_intrinsics/)                                     | [download](https://github.com/ARM-software/acle/releases/latest)
-[Arm Neon Intrinsics Reference](https://arm-software.github.io/acle/neon_intrinsics/)                         | [download](https://github.com/ARM-software/acle/releases/latest)
-[Arm®v8-M Security Extensions - Requirements on Development Tools](https://arm-software.github.io/acle/cmse/) | [download](https://github.com/ARM-software/acle/releases/latest)
+[Arm C Language Extensions](https://arm-software.github.io/acle/main/)
 
-## Legacy releases
+[Morello Supplement to the Arm C Language Extensions](https://arm-software.github.io/acle/morello/)
+
+[Arm MVE Intrinsics](https://arm-software.github.io/acle/mve_intrinsics/)
+
+[Arm Neon Intrinsics Reference](https://arm-software.github.io/acle/neon_intrinsics/)
+
+[Arm®v8-M Security Extensions - Requirements on Development Tools](https://arm-software.github.io/acle/cmse/)
 
-Legacy versions of the documents were released on [Arm Developer](https://developer.arm.com).
-They are now also hosted in this repository and are to be found in [Legacy releases](legacyreleases/README.md).
-They follow the same folder naming scheme as the main document folders.
+The PDF versions can be found in the latest GitHub
+[release](https://github.com/ARM-software/acle/releases/latest).
 
 # License