ICU-22325 BRS74RC: Update version number to 74.1

[rp9-next]

Checklist

• Required: Issue filed: https://unicode-org.atlassian.net/browse/ICU-22325
• Required: The PR title must be prefixed with a JIRA Issue number.
• Required: The PR description must include the link to the Jira Issue, for example by completing the URL in the first checklist item
• Required: Each commit message must be prefixed with a JIRA Issue number.
• Issue accepted (done by Technical Committee after discussion)
• Tests included, if applicable
• API docs and/or User Guide docs changed or added, if applicable

[mihnita]

I just merged a PR that simplifies the versioning on the Java side (#2624)

It is easy to update all the pom versions:

mvn versions:set -DnewVersion=74.1.0 -DgenerateBackupPoms=false

But there are still places to update in 2 files:

• In icu4j/pom.xml the api.doc.version property.
  Maybe. It is now "${icu.major.version} Release Candidate", which makes it "74 Release Candidate".
  But will need updating for release.
  That is only used in the Javadoc.
• A few variables in icu4j/releases_tools/api_reports.sh
  • artifact_version
  • api_report_version
  • api_report_prev_version

[markusicu]

Thanks Mihai!
Could you please rebase this PR, make the additional changes for ICU4J and add a commit for those?

[echeran]

@mihnita @markusicu I added commits to update the relevant release process docs based on what I saw from Mihai's comments. Please review that I got it correct. Also, the version numbers have already been set correctly by Mihai's PR. I merged the latest from main into this branch to pick up those changes.

[mihnita]

I can't rebase / merge, it is grayed out.
And I can't see any pom.xml changes.

Also, the version numbers have already been set correctly by Mihai's PR.
I merged the latest from main into this branch to pick up those changes.

?
What I submitted still uses <version>74.0.1-SNAPSHOT</version>

[markusicu]

For reference:

• Equivalent PR in preparation of ICU 73rc: ICU-22220 BRS73RC Update version number and regenerate configure v73.1 #2375
  • removed "snapshot" but not "rc"
• Followed by the post-rc PR in preparation of the final 73 release: ICU-22221 BRS73GA: Update version number to 73.1 #2414

72:

• rc: ICU-21957 BRS72RC Update version number and regenerate configure v72.1 #2191
  • removed neither "snapshot" nor "rc"
• final: ICU-21958 BRS72GA Update version number #2227

Inconsistent, but my memory is that we have tried to move some of these changes forward to reduce work.
@yumaoka @pedberg-icu @richgillam FYI

[mihnita]

TBD: we might consider using the version directly instead of ${icu.major.version}.

That way one can change it from command line:

mvn versions:set-property -DnewVersion="75 Release Candidate" -Dproperty=api.doc.version

Or maybe remove "Release Candidate" completely.
"In my book" RC means: if there are no problems found then this is promoted to GA.

Using "Release Candidate" anywhere means that even if everything is perfect, one has to remove such and rebuild in order to release.

[mihnita]

Note: not actionable for this PR, of course.

[mihnita]

Thank you!

[markusicu]

lgtm tnx!

[markusicu]

tnx!

[jira-pull-request-webhook]

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot