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-44518: [R] Update NEWS for 18.0.0 #44520

Merged
merged 1 commit into from
Oct 26, 2024
Merged

Conversation

thisisnic
Copy link
Member

Rationale for this change

Update NEWS for release

What changes are included in this PR?

Update NEWS for release

Are these changes tested?

No

Are there any user-facing changes?

No

@thisisnic thisisnic requested a review from jonkeane as a code owner October 23, 2024 21:55
Copy link

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

@amoeba amoeba changed the title GH-44518: [R] Update NEWS for 18.0.0 GH-44518: [R] Update NEWS for 18.0.0 Oct 26, 2024
@amoeba amoeba merged commit a3c39ec into apache:main Oct 26, 2024
11 checks passed
@amoeba amoeba removed the awaiting committer review Awaiting committer review label Oct 26, 2024
@amoeba
Copy link
Member

amoeba commented Oct 26, 2024

Looks like we had the same list of changes. Merged your as-is. Thanks!

amoeba pushed a commit that referenced this pull request Oct 26, 2024
### Rationale for this change

Update NEWS for release

### What changes are included in this PR?

Update NEWS for release

### Are these changes tested?

No

### Are there any user-facing changes?

No
* GitHub Issue: #44518

Authored-by: Nic Crane <thisisnic@gmail.com>
Signed-off-by: Bryce Mecum <petridish@gmail.com>
Copy link

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

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 10 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants