Cole Bowden

@Praveen2112 the template suggests there's another PR with docs for this change, but I can't find it. Could you link? Also, what section should the release note go into?

You're going to need to squash these later commits down into the proper original commits. Trino has a strict policy on commits being atomic, sensible units of change. Code review...

Trying something new with commits as release notes are curated throughout the week - going to use periodic commits for new notes and fixup commits to address feedback. It should...

@tangjiangling Do we want a release note for this change? And is there a plan/need to write docs related to this as a follow-up? cc @hashhar

Oops, somehow missed the release note in the PR description. And that sounds good to me.

@dain @losipiuk any chance we can get an initial pass at reviewing this relatively soon? From a look at git blame, it seems like you two are the most involved...

If this improves performance/reduces cost, it would be good to include it in the release notes. Could you please propose a potential release note? cc @arhimondr

Do we want to include a release note for this?

Is it worth documenting in the meantime, or should I just wait for it to be removed?

This PR has been inactive for 4 weeks. What's the status here - do we need it changed, or is it waiting on that other PR for direction? cc @ebyhr