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

Add Trino 463 release notes #23810

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Add Trino 463 release notes #23810

merged 1 commit into from
Oct 23, 2024

Conversation

mosabua
Copy link
Member

@mosabua mosabua commented Oct 16, 2024

Description

Assemble the release notes for the upcoming Trino 463 release.

Additional context and related issues

See https://github.com/trinodb/trino/pulls?q=is%3Apr+is%3Aclosed+milestone%3A463

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

Verification for each pull request

Format: PR/issue number, ✅ / ❌ rn ✅ / ❌ docs
✅ rn - release note added and verified, or assessed to be not necessary, set to ❌ rn before completion
✅ docs - need for docs assessed and merged, or assessed to be not necessary, set to ❌ docs before completion

16 Oct 2024

17 Oct 2024

18 Oct 2024

19 Oct 2024

20 Oct 2024

21 Oct 2024

22 Oct 2024

23 Oct 2024

@cla-bot cla-bot bot added the cla-signed label Oct 16, 2024
@wendigo wendigo changed the title Add Trino 462 release notes Add Trino 463 release notes Oct 17, 2024
@wendigo
Copy link
Contributor

wendigo commented Oct 17, 2024

@mosabua 463 ;)

@mosabua mosabua force-pushed the rn463 branch 2 times, most recently from fa3e663 to 62b2ea3 Compare October 17, 2024 17:33
@mosabua
Copy link
Member Author

mosabua commented Oct 17, 2024

@mosabua 463 ;)

I know .. haha

@mosabua mosabua force-pushed the rn463 branch 8 times, most recently from 3207bb6 to 56c502c Compare October 22, 2024 21:39

## General

* Enable HTTP/2 for internal communication by default. ({issue}`21793`)
Copy link
Member Author

Choose a reason for hiding this comment

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

@wendigo do we also want to add that HTTP/2 support for clients is there now? Also .. any config we need to add to the release notes as fallback or do we want to link somewhere?

Copy link
Member

Choose a reason for hiding this comment

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

Maybe just say "the previous behavior can be restored by setting xxx to yyy".

Copy link
Member Author

@mosabua mosabua Oct 23, 2024

Choose a reason for hiding this comment

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

Ok .. I will also send a docs PR. Ideally we get #23832 and #23833 merged as well so I can cleanly add a new page for internal communication properties.

@martint martint merged commit 38780dc into trinodb:master Oct 23, 2024
5 checks passed
@github-actions github-actions bot added this to the 463 milestone Oct 23, 2024
@mosabua mosabua deleted the rn463 branch October 23, 2024 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants