ICU-23175 Consistent names for the release artifacts

Author: mihnita

.github/workflows/icu4c.yml

@@ -459,9 +459,9 @@ jobs:
         $minorVersion = $icuVersion.Split('.')[1]
         # Determine the new file name based on the version
         if ($minorVersion -eq "0") {
-          $newZipName = "icu4c-${majorVersion}rc-${{ matrix.win_ver }}-MSVC2022"
+          $newZipName = "icu4c-${majorVersion}.1rc-${{ matrix.win_ver }}-MSVC2022"
         } else {
-          $newZipName = "icu4c-${majorVersion}_${minorVersion}-${{ matrix.win_ver }}-MSVC2022"
+          $newZipName = "icu4c-${majorVersion}.${minorVersion}-${{ matrix.win_ver }}-MSVC2022"
         }
         # Debugging: Print the new zip name
         Write-Host "New Zip Name: $newZipName"
@@ -929,21 +929,23 @@ jobs:
       - name: Zip
         run: |
           cd icu4c/source/icuexportdata
-          zip -r ../../../icuexportdata_${{ inputs.gitReleaseFilename }}.zip .
+          zip -r ../../../icu4x-exportdata_${{ inputs.gitReleaseFilename }}.zip .
       - name: Publish Artifact
         uses: actions/upload-artifact@v4
         with:
           name: icuexportdata_output
-          path: icuexportdata_*.zip
+          path: icu4x-exportdata_*.zip
       - name: Upload to release tag
         if: ${{ inputs.gitReleaseTag && startsWith(inputs.gitReleaseTag, 'release-') }}
         run: |
-          gh release upload ${{ inputs.gitReleaseTag }} icuexportdata_*.zip --clobber
+          zipVer=$(echo ${{ inputs.gitReleaseTag }} | sed 's/^release-//')
+          mv icu4x-exportdata_*.zip icu4x-exportdata-${zipVer}.zip
+          gh release upload ${{ inputs.gitReleaseTag }} icu4x-exportdata-*.zip --clobber
         env:
           GH_TOKEN: ${{ github.token }}
       - name: Upload to icu4x tag
         if: ${{ inputs.gitReleaseTag && startsWith(inputs.gitReleaseTag, 'icu4x/') }}
         run: |
-          gh release upload ${{ inputs.gitReleaseTag }} icuexportdata_*.zip --clobber
+          gh release upload ${{ inputs.gitReleaseTag }} icu4x-exportdata_*.zip --clobber
         env:
           GH_TOKEN: ${{ github.token }}

.github/workflows/release-check-sign.yml

@@ -44,13 +44,11 @@ jobs:
     - name: Checksums and sign
       run: |
         source icu4j/releases_tools/shared.sh
-        # Convert 76.1 to 76_1
-        underscore_version=$(echo $artifact_version | sed 's/\./_/g')
         pushd ${RELEASE_FOLDER}
         sha512sum -b icu4c*              > SHASUM512.txt
         md5sum -b *.jar                  > icu4j-${artifact_version}.md5
-        md5sum -b icu4c-*-data-bin-*.zip > icu4c-${underscore_version}-binary.md5
-        md5sum -b icu4c-*-src.*          > icu4c-${underscore_version}-sources.md5
+        md5sum -b icu4c-*-data-bin-*.zip > icu4c-${artifact_version}-binary.md5
+        md5sum -b icu4c-*-src.*          > icu4c-${artifact_version}-sources.md5
         find . -type f -name 'icu4c*' -exec gpg --no-tty --batch --pinentry-mode loopback --passphrase=$MAVEN_GPG_PASSPHRASE -a --output {}.asc --detach-sig {} \;
         gpg --no-tty --batch --pinentry-mode loopback --passphrase=$MAVEN_GPG_PASSPHRASE -a --output SHASUM512.txt.asc --detach-sig SHASUM512.txt
         popd

.github/workflows/release-icu4c-fedora.yml

@@ -64,10 +64,8 @@ jobs:
         source /etc/os-release
         # Get the ICU version in artifact_version
         source icu4j/releases_tools/shared.sh
-        # Convert 76.1 to 76_1
-        underscore_version=$(echo $artifact_version | sed 's/\./_/g')
         pushd ${RELEASE_FOLDER}
-        tar -czf icu4c-${underscore_version}-Fedora_Linux${VERSION_ID}-x64.tgz icu
+        tar -czf icu4c-${artifact_version}-Fedora_Linux${VERSION_ID}-x64.tgz icu
         rm -fr icu
         popd
 

.github/workflows/release-icu4c-ubuntu.yml

@@ -58,10 +58,8 @@ jobs:
         source /etc/os-release
         # Get the ICU version in artifact_version
         source icu4j/releases_tools/shared.sh
-        # Convert 77.1 to 77_1
-        underscore_version=$(echo $artifact_version | sed 's/\./_/g')
         pushd ${RELEASE_FOLDER}
-        tar -czf icu4c-${underscore_version}-Ubuntu${VERSION_ID}-x64.tgz icu
+        tar -czf icu4c-${artifact_version}-Ubuntu${VERSION_ID}-x64.tgz icu
         rm -fr icu
         popd
         mv icu4c/source/dist/icu4c-77_1-d*    ${RELEASE_FOLDER}

docs/processes/release/tasks/docs.md

@@ -326,7 +326,7 @@ javadoc files. Create icu4c-X_X_X-docs.zip
 3.  The generated API docs are in <path>/icu4c/source/doc/html/<br>
     `cd <path>/icu4c/source/doc/html/`
 4.  Create a zip file, e.g.,<br>
-    `tar cvfz /tmp/icu4c72rc.tar.gz * # Note: label the file apropriately for the release.
+    `tar cvfz /tmp/icu4c78.1rc.tar.gz * # Note: label the file apropriately for the release.
 5.  Edit [README.md in icu-docs](https://github.com/unicode-org/icu-docs/blob/main/README.md).
 6.  Update the table under "API docs" at the top of README.md with the new version in column "C" in row "Dev" for the release candidate or "Released" for the final release.
 7.  Add the updated README.md to the pull request with the new API documentation.
@@ -346,8 +346,8 @@ javadoc files. Create icu4c-X_X_X-docs.zip
 
     d. Be sure that you are in the right directory. Then, remove all the files
         in this directory, e.g., `rm -rf *`. (Remember "git restore" is a good friend!)
-     
-    e. Unzip the tar file from above, replacing all documentation. Ex: `tar xvfz /tmp/icu4c72rc.tar.gz`
+
+    e. Unzip the tar file from above, replacing all documentation. Ex: `tar xvfz /tmp/icu4c-78.1rc.tar.gz`
 
     e. Remove the zip file if it's in the folder.
 

docs/processes/release/tasks/publish/index.md

@@ -102,7 +102,7 @@ Use the GitHub GUI to create both the "release" and the "tag" at the same time:
 
 <https://github.com/unicode-org/icu/releases/new>
 
-1. Fill in the tag name, such as `release-63-rc` or `release-63-1`, and make the
+1. Fill in the tag name, such as `release-63-1rc` or `release-63-1`, and make the
 target the "maint/maint-xx" branch (such as `maint/maint-63`).
 1. Set the title to `ICU 63 RC` or `ICU 63.1`.
 1. Fill in the description using the
@@ -320,9 +320,9 @@ That new flow overlaps with _"Using the output from the build bots"_ below.
         *   Navigate into the folder with the same name.
         *   Check and verify the names of the zip file are appropriate:
             *   Ex: The x64 zip for version 76.1 should be named
-                "icu4c-76_1-Win64-MSVC2022.zip"
+                "icu4c-76.1-Win64-MSVC2022.zip"
             *   Ex: The x86 zip for version 76.1 should be named
-                "icu4c-76_1-Win32-MSVC2022.zip"
+                "icu4c-76.1-Win32-MSVC2022.zip"
         *   Note: For RC releases the name looked like this:
             "icu4c-76rc-Win64-MSVC2022"
 *   ~~AIX Bin:~~ (AIX is broken and ignored for now.)

docs/processes/release/tasks/publish/release.md

@@ -62,7 +62,7 @@ Here you should use the release tag.
    * The icu4c data files (`icu4c-{icuver}-data.zip`,
      `icu4c-{icuver}-data-bin-b.zip`, `icu4c-{icuver}-data-bin-l.zip`)
    * The icu4c source archives (`icu4c-{icuver}-src.tgz` and `icu4c-{icuver}-src.zip`)
-   * The ICU4C documentation (`icu4c-76_1-docs.zip`) \
+   * The ICU4C documentation (`icu4c-{icuver}-docs.zip`) \
    **WARNING:** this is also the one to be published (unpacked) for web access
 
 1. **Release - ICU4J publish to Maven Central** (`release-icu4j-maven.yml`) \

docs/processes/release/tasks/versions.md

@@ -215,7 +215,7 @@ The command requires a version number string that follows the typical Java / Mav
 5. Update the following variables in `icu4j/releases_tools/shared.sh`
 
     * `artifact_version` - The version used in the Maven `pom.xml` files. You can alternatively produce this value by running `mvn help:evaluate -Dexpression=project.version -q -DforceStdout`.
-    * `github_rel_version` - The version used in the name of the GitHub downloadable artifacts. For example "73_2" or "74rc".
+    * `github_rel_version` - The version used in the name of the GitHub downloadable artifacts. For example "78.2" or "78.1rc".
     * `api_report_version` - The major version of the new version. Change during RC BRS.
     * `api_report_prev_version`  - The major version of the previous version. Change during RC BRS.
 
@@ -282,7 +282,7 @@ For updating ICU version numbers, follow the steps below.
         releases, use <2-digit major version> + "m" + <milestone number>, e.g.
         "55m1". For release candidate, use <2-digit major version> + "rc", e.g.
         54rc. For official releases, use full version numbers using under bar as the
-        separator, e.g. "54_1", "54_1_1".
+        separator, e.g. "54.1", "54.1.1".
     *   api.doc.version: The version displayed in API reference doc - use full
         version number such as "60.1" for official and RC releases, "60 Milestone 1" for
         milestone 1.

icu4j/releases_tools/shared.sh

@@ -6,7 +6,7 @@ export MAVEN_ARGS='--no-transfer-progress'
 
 # Version update!
 export artifact_version='78.0.1-SNAPSHOT'
-export github_rel_version='78_0_1'
+export github_rel_version='78.0.1'
 export api_report_version='78'
 export api_report_prev_version='77'
 export out_dir=target

tools/currency/.project

@@ -14,4 +14,15 @@
 	<natures>
 		<nature>org.eclipse.jdt.core.javanature</nature>
 	</natures>
+	<filteredResources>
+		<filter>
+			<id>1754600590952</id>
+			<name></name>
+			<type>30</type>
+			<matcher>
+				<id>org.eclipse.core.resources.regexFilterMatcher</id>
+				<arguments>node_modules|\.git|__CREATED_BY_JAVA_LANGUAGE_SERVER__</arguments>
+			</matcher>
+		</filter>
+	</filteredResources>
 </projectDescription>