Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

michael-o
Copy link
Member

This closes #137

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MCHECKSTYLE-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MCHECKSTYLE-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

asfgit pushed a commit that referenced this pull request May 31, 2024
@asfgit asfgit force-pushed the parent-42-maven-3.6.3 branch from 8363372 to 51f2acc Compare May 31, 2024 20:49
asfgit pushed a commit that referenced this pull request Jun 1, 2024
@asfgit asfgit force-pushed the parent-42-maven-3.6.3 branch from 51f2acc to 888f40a Compare June 1, 2024 11:57
asfgit pushed a commit that referenced this pull request Jun 2, 2024
@asfgit asfgit force-pushed the parent-42-maven-3.6.3 branch from 888f40a to ebf72bd Compare June 2, 2024 09:30
@asfgit asfgit force-pushed the parent-42-maven-3.6.3 branch from ebf72bd to e72bd83 Compare June 2, 2024 09:34
@michael-o
Copy link
Member Author

@slachiewicz, @slawekjaranowski, any objections?

@asfgit asfgit merged commit e72bd83 into master Jun 2, 2024
@michael-o michael-o deleted the parent-42-maven-3.6.3 branch June 2, 2024 14:44
@jira-importer
Copy link

Resolve #506

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

Successfully merging this pull request may close these issues.

4 participants