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.

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

GH-44948: [Dev][Archery] Remove JIRA remnants from Archery #45091

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

raulcd
Copy link
Member

@raulcd raulcd commented Dec 20, 2024

Rationale for this change

We are not using JIRA as issue tracker anymore, we should remove it from archery.

What changes are included in this PR?

Remove Jira dependency from archery and related code mainly for release curate for release changelog generation.

Are these changes tested?

Yes, archery tests are still successful and I've validated that I can generate:
archery release curate 18.0.0 and archery release curate 19.0.0 successfully.
I haven't tested cherry-picking but there doesn't seem to be code involved and we have been able to cherry-pick during the last releases.

Are there any user-facing changes?

No

Copy link

⚠️ GitHub issue #44948 has been automatically assigned in GitHub to PR creator.

Copy link

⚠️ GitHub issue #44948 has no components, please add labels for components.

@github-actions github-actions bot added the awaiting committer review Awaiting committer review label Dec 20, 2024
@raulcd raulcd marked this pull request as ready for review December 20, 2024 17:51
Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@kou kou merged commit 5293379 into apache:main Dec 20, 2024
9 checks passed
@kou kou removed the awaiting committer review Awaiting committer review label Dec 20, 2024
@github-actions github-actions bot added the awaiting merge Awaiting merge label Dec 20, 2024
@raulcd raulcd deleted the GH-44948 branch December 23, 2024 08:23
Copy link

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 5293379.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting merge Awaiting merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants