prepare v12.2.0-3

Author: ilg-ul

CHANGELOG.md

@@ -3,6 +3,10 @@
 
 Entries in this file are in reverse chronological order.
 
+## 2023-02-05
+
+* v12.2.0-3 prepared
+
 ## 2023-02-02
 
 * v12.2.0-2.1 published on npmjs.com

README-MAINTAINER.md

@@ -94,8 +94,8 @@ update the dependencies in `package.json`.
 
 ### Identify the main GCC version
 
-Determine the GCC version (like `12.1.0`) and update the `scripts/VERSION`
-file; the format is `12.2.0-2`. The fourth digit is the number of the
+Determine the GCC version (like `12.2.0`) and update the `scripts/VERSION`
+file; the format is `12.2.0-3`. The fourth digit is the number of the
 the xPack GNU RISC-V Embedded GCC release number of this version.
 
 ### Update versions in `README` files
@@ -109,7 +109,7 @@ Check GitHub issues and pull requests:
 
 - <https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/issues/>
 
-and fix them; assign them to a milestone (like `12.2.0-2`).
+and fix them; assign them to a milestone (like `12.2.0-3`).
 
 ### Check `README.md`
 
@@ -121,8 +121,8 @@ but in the version specific release page.
 
 - open the `CHANGELOG.md` file
 - check if all previous fixed issues are in
-- add a new entry like _* v12.2.0-2 prepared_
-- commit with a message like _prepare v12.2.0-2_
+- add a new entry like _* v12.2.0-3 prepared_
+- commit with a message like _prepare v12.2.0-3_
 
 ### Update the version specific code
 
@@ -234,8 +234,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/riscv-none-elf-gcc-xpack.git/build/darwin-x64/deploy
 total 197288
--rw-r--r--  1 ilg  staff  93798413 Feb  1 12:52 xpack-riscv-none-elf-gcc-12.2.0-2-darwin-x64.tar.gz
--rw-r--r--  1 ilg  staff       118 Feb  1 12:52 xpack-riscv-none-elf-gcc-12.2.0-2-darwin-x64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  93798413 Feb  1 12:52 xpack-riscv-none-elf-gcc-12.2.0-3-darwin-x64.tar.gz
+-rw-r--r--  1 ilg  staff       118 Feb  1 12:52 xpack-riscv-none-elf-gcc-12.2.0-3-darwin-x64.tar.gz.sha
 ```
 
 #### Apple Silicon macOS
@@ -267,8 +267,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/riscv-none-elf-gcc-xpack.git/build/darwin-arm64/deploy
 total 196792
--rw-r--r--  1 ilg  staff  90622384 Feb  1 12:11 xpack-riscv-none-elf-gcc-12.2.0-2-darwin-arm64.tar.gz
--rw-r--r--  1 ilg  staff       120 Feb  1 12:11 xpack-riscv-none-elf-gcc-12.2.0-2-darwin-arm64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  90622384 Feb  1 12:11 xpack-riscv-none-elf-gcc-12.2.0-3-darwin-arm64.tar.gz
+-rw-r--r--  1 ilg  staff       120 Feb  1 12:11 xpack-riscv-none-elf-gcc-12.2.0-3-darwin-arm64.tar.gz.sha
 ```
 
 #### Intel GNU/Linux
@@ -302,8 +302,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/riscv-none-elf-gcc-xpack.git/build/linux-x64/deploy
 total 102308
--rw-r--r-- 1 ilg ilg 104756842 Feb  1 10:19 xpack-riscv-none-elf-gcc-12.2.0-2-linux-x64.tar.gz
--rw-r--r-- 1 ilg ilg       117 Feb  1 10:19 xpack-riscv-none-elf-gcc-12.2.0-2-linux-x64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 104756842 Feb  1 10:19 xpack-riscv-none-elf-gcc-12.2.0-3-linux-x64.tar.gz
+-rw-r--r-- 1 ilg ilg       117 Feb  1 10:19 xpack-riscv-none-elf-gcc-12.2.0-3-linux-x64.tar.gz.sha
 ```
 
 ##### Build the Windows binaries
@@ -328,8 +328,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/riscv-none-elf-gcc-xpack.git/build/win32-x64/deploy
 total 109320
--rw-r--r-- 1 ilg ilg 111937715 Feb  1 10:48 xpack-riscv-none-elf-gcc-12.2.0-2-win32-x64.zip
--rw-r--r-- 1 ilg ilg       114 Feb  1 10:48 xpack-riscv-none-elf-gcc-12.2.0-2-win32-x64.zip.sha
+-rw-r--r-- 1 ilg ilg 111937715 Feb  1 10:48 xpack-riscv-none-elf-gcc-12.2.0-3-win32-x64.zip
+-rw-r--r-- 1 ilg ilg       114 Feb  1 10:48 xpack-riscv-none-elf-gcc-12.2.0-3-win32-x64.zip.sha
 ```
 
 #### Arm GNU/Linux 64-bit
@@ -361,8 +361,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/riscv-none-elf-gcc-xpack.git/build/linux-arm64/deploy
 total 98020
--rw-r--r-- 1 ilg ilg 100361089 Feb  1 13:16 xpack-riscv-none-elf-gcc-12.2.0-2-linux-arm64.tar.gz
--rw-r--r-- 1 ilg ilg       119 Feb  1 13:16 xpack-riscv-none-elf-gcc-12.2.0-2-linux-arm64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 100361089 Feb  1 13:16 xpack-riscv-none-elf-gcc-12.2.0-3-linux-arm64.tar.gz
+-rw-r--r-- 1 ilg ilg       119 Feb  1 13:16 xpack-riscv-none-elf-gcc-12.2.0-3-linux-arm64.tar.gz.sha
 ```
 
 #### Arm GNU/Linux 32-bit
@@ -393,8 +393,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/riscv-none-elf-gcc-xpack.git/build/linux-arm/deploy
 total 92456
--rw-r--r-- 1 ilg ilg 94666972 Feb  1 13:04 xpack-riscv-none-elf-gcc-12.2.0-2-linux-arm.tar.gz
--rw-r--r-- 1 ilg ilg      117 Feb  1 13:04 xpack-riscv-none-elf-gcc-12.2.0-2-linux-arm.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 94666972 Feb  1 13:04 xpack-riscv-none-elf-gcc-12.2.0-3-linux-arm.tar.gz
+-rw-r--r-- 1 ilg ilg      117 Feb  1 13:04 xpack-riscv-none-elf-gcc-12.2.0-3-linux-arm.tar.gz.sha
 ```
 
 ### Files cache
@@ -647,7 +647,7 @@ git clone \
 
 ## Create a new GitHub pre-release draft
 
-- in `CHANGELOG.md`, add the release date and a message like _* v12.2.0-2 released_
+- in `CHANGELOG.md`, add the release date and a message like _* v12.2.0-3 released_
 - commit with _CHANGELOG update_
 - check and possibly update the `templates/body-github-release-liquid.md`
 - push the `xpack-develop` branch
@@ -658,8 +658,8 @@ The workflows results and logs are available from the
 
 The result is a
 [draft pre-release](https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases/)
-tagged like **v12.2.0-2** (mind the dash in the middle!) and
-named like **xPack GNU RISC-V Embedded GCC v12.2.0-2** (mind the dash),
+tagged like **v12.2.0-3** (mind the dash in the middle!) and
+named like **xPack GNU RISC-V Embedded GCC v12.2.0-3** (mind the dash),
 with all binaries attached.
 
 - edit the draft and attach it to the `xpack-develop` branch (important!)
@@ -682,7 +682,7 @@ If any, refer to closed
 ## Update the preview Web
 
 - commit the `develop` branch of `xpack/web-jekyll` GitHub repo;
-  use a message like _xPack GNU RISC-V Embedded GCC v12.2.0-2 released_
+  use a message like _xPack GNU RISC-V Embedded GCC v12.2.0-3 released_
 - push to GitHub
 - wait for the GitHub Pages build to complete
 - the preview web is <https://xpack.github.io/web-preview/news/>
@@ -724,18 +724,18 @@ watching this project.
 - compare the SHA sums with those shown by `cat *.sha`
 - check the executable names
 - commit all changes, use a message like
-  _package.json: update urls for 12.2.0-2 release_ (without _v_)
+  _package.json: update urls for 12.2.0-3 release_ (without _v_)
 
 ## Publish on the npmjs.com server
 
 - select the `xpack-develop` branch
 - check the latest commits `npm run git-log`
-- update `CHANGELOG.md`, add a line like _* v12.2.0-2.1 published on npmjs.com_
-- commit with a message like _CHANGELOG: publish npm v12.2.0-2.1_
+- update `CHANGELOG.md`, add a line like _* v12.2.0-3.1 published on npmjs.com_
+- commit with a message like _CHANGELOG: publish npm v12.2.0-3.1_
 - `npm pack` and check the content of the archive, which should list
   only the `package.json`, the `README.md`, `LICENSE` and `CHANGELOG.md`;
   possibly adjust `.npmignore`
-- `npm version 12.2.0-2.1`; the first 4 numbers are the same as the
+- `npm version 12.2.0-3.1`; the first 4 numbers are the same as the
   GitHub release; the fifth number is the npm specific version
 - the commits and the tag should have been pushed by the `postversion` script;
   if not, push them with `git push origin --tags`
@@ -764,12 +764,12 @@ The tests results are available from the
 When the release is considered stable, promote it as `latest`:
 
 - `npm dist-tag ls @xpack-dev-tools/riscv-none-elf-gcc`
-- `npm dist-tag add @xpack-dev-tools/[email protected]2.1 latest`
+- `npm dist-tag add @xpack-dev-tools/[email protected]3.1 latest`
 - `npm dist-tag ls @xpack-dev-tools/riscv-none-elf-gcc`
 
 In case the previous version is not functional and needs to be unpublished:
 
-- `npm unpublish @xpack-dev-tools/[email protected]2.1`
+- `npm unpublish @xpack-dev-tools/[email protected]3.1`
 
 ## Update the Web
 
@@ -791,7 +791,7 @@ In case the previous version is not functional and needs to be unpublished:
 
 - in a separate browser windows, open [TweetDeck](https://tweetdeck.twitter.com/)
 - using the `@xpack_project` account
-- paste the release name like **xPack GNU RISC-V Embedded GCC v12.2.0-2 released**
+- paste the release name like **xPack GNU RISC-V Embedded GCC v12.2.0-3 released**
 - paste the link to the Web page
   [release](https://xpack.github.io/riscv-none-elf-gcc/releases/)
 - click the **Tweet** button
@@ -815,9 +815,9 @@ Add a new topic in the **Announcements** category of the
 [RISC-V forums]<https://groups.google.com/a/groups.riscv.org/g/sw-dev>).
 
 ```console
-Subject: xPack GNU RISC-V Embedded GCC v12.2.0-2 released
+Subject: xPack GNU RISC-V Embedded GCC v12.2.0-3 released
 
-Version 12.2.0-2 is a new release of the xPack GNU RISC-V Embedded GCC; it follows the GNU GCC release.
+Version 12.2.0-3 is a new release of the xPack GNU RISC-V Embedded GCC; it follows the GNU GCC release.
 
 https://xpack.github.io/blog/2022/05/14/riscv-none-elf-gcc-v11-3-0-1-released/
 ```

README.md

@@ -103,8 +103,8 @@ After install, the package should create a structure like this (only the
 first two depth levels are shown):
 
 ```console
-$ tree -L 2 /Users/ilg/Library/xPacks/\@xpack-dev-tools/riscv-none-elf-gcc/12.2.0-2/.content/
-/Users/ilg/Library/xPacks/\@xpack-dev-tools/riscv-none-elf-gcc/12.2.0-2/.content/
+$ tree -L 2 /Users/ilg/Library/xPacks/\@xpack-dev-tools/riscv-none-elf-gcc/12.2.0-3/.content/
+/Users/ilg/Library/xPacks/\@xpack-dev-tools/riscv-none-elf-gcc/12.2.0-3/.content/
 ├── README.md
 ├── bin
 │   ├── riscv-none-elf-addr2line
@@ -222,16 +222,16 @@ For more details please read the
 ### Versioning
 
 The version strings used by the GCC project are three number strings
-like `12.1.0`; to this string the xPack distribution adds a four number,
+like `12.2.0`; to this string the xPack distribution adds a four number,
 but since semver allows only three numbers, all additional ones can
 be added only as pre-release strings, separated by a dash,
-like `12.2.0-2`.
+like `12.2.0-3`.
 When published as a npm package, the version gets
-a fifth number, like `12.2.0-2.1`.
+a fifth number, like `12.2.0-3.1`.
 
 Since adherence of third party packages to semver is not guaranteed,
-it is recommended to use semver expressions like `^12.1.0` and `~12.1.0`
-with caution, and prefer exact matches, like `12.2.0-2.1`.
+it is recommended to use semver expressions like `^12.2.0` and `~12.2.0`
+with caution, and prefer exact matches, like `12.2.0-3.1`.
 
 ## Maintainer info
 

scripts/VERSION

@@ -1 +1 @@
-12.2.0-2
+12.2.0-3