Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ICU-22606 Create an (almost) full release from CI #3222

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

ICU-22606 Create an (almost) full release from CI #3222

wants to merge 4 commits into from
+440 −30

Conversation

mihnita
Copy link
Contributor

@mihnita mihnita commented Sep 30, 2024

Automates most of the tasks required for release.

There is no need to build on Windows / Ubuntu / Fedora, there (almost) no need to upload files by hand to the GitHub Release, there is no need for PGP signing, keys, etc.

Not final, close enough.

Checklist

  • Required: Issue filed: https://unicode-org.atlassian.net/browse/ICU-22606
    • For minor changes you can use one of the following per-release tickets:
    • ICU 77 code warnings/version updates: ICU-22920 — Fix compiler warnings. Update versions of code-related dependencies (e.g., dependabot).
    • ICU 77 docs minor fixes: ICU-22921 — User Guide & API docs typos etc., and version updates (e.g., dependabot for User Guide)
  • Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • 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. Example: "ICU-1234 Fix xyz"
  • 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
ICU-22606 Create full release from CI - rename
773015f
@mihnita
ICU-22606 Create full release from CI - workflow files
bef5b77 
The Ubuntu and Fedora files are very similar.
But I am not sure (yet) what is the best way to share.

The files uploaded to the GitHub Release use the exact same names as before.
The .jar files are binary identical to the ones that go to Maven (checked).

The Fedora Docker image should be built and uploaded from a dev machine.
There is a workflow (from GitHub) doing that, but has a warning that:
> This workflow uses actions that are not certified by GitHub.
> They are provided by a third-party and are governed by
> separate terms of service, privacy policy, and support documentation.
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • docs/processes/release/tasks/publish/release.md is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@echeran echeran Awaiting requested review from echeran

@markusicu markusicu Awaiting requested review from markusicu

At least 1 approving review is required to merge this pull request.

Assignees

@echeran echeran

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@mihnita @echeran