Repository navigation
Conversation
Backport to the 0.64 release line. (cherry picked from commit 97afe81)
|
No dialect label was applied because the title does not name a SQL dialect. If this change targets one or more dialects, edit the title to Changed files touch PostgreSQL. |
|
LGTM, but I do not have the keys to the kingdom when it comes to backporting. cc @alamb do we have a procedure for it? |
|
I don't know if we have ever done a patch release from this repo. I would personally suggest we just do a new major release . Maybe we can move this one up The per-release overhead is the same either way |
|
If we are happy to do a new major release, I can put it on my list for next week |
i will make sure there are no other regressions for datafusion by then and do release prep |
I would say that we still have to finalize quite a few PRs before the next major. @blaginin does this PR constitute something that needs to be urgently fixed? If so proceeding with a cherrypicked fix as a patch may be the best way forward, and avoid a major release. Unrelated PS: my brain is really not appreciating the new scrambled PR UI |
What is waiting to be finalized and why? What if we made a release now (like next week) and in December?
Agreed it is taking some time to get used to |
Backport #3003 to the 0.64 release line.
(cherry picked from commit 97afe81)