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

Pin Curator dependencies to 5.3.0 util CURATOR-696 has been resolved #16444

Closed
wants to merge 1 commit into from
Closed

Pin Curator dependencies to 5.3.0 util CURATOR-696 has been resolved #16444

wants to merge 1 commit into from

Conversation

asdf2014
Copy link
Member

Description

We should pin Curator dependencies to 5.3.0 util CURATOR-696 has been resolved.

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@asdf2014 asdf2014 mentioned this pull request May 14, 2024
Merged
10 tasks
@cryptoe
Copy link
Contributor

cryptoe commented Jun 6, 2024 •
edited

Since we are already on the path for : #16528 closing this ticket

@cryptoe cryptoe closed this Jun 6, 2024
@asdf2014 asdf2014 deleted the pin-curator branch June 6, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Area - Dependencies Area - ZooKeeper/Curator GHA
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@asdf2014 @cryptoe