alamb commented on issue #19692: URL: https://github.com/apache/datafusion/issues/19692#issuecomment-4016155502
> > That's a really long time to leave `branch-53` open without a release, isn't it? Why can't we do both simultaneously? It's already tough backporting to both `branch-52` and `branch-53`. > > yeah, I was scratching my head on this matter. Maintaining 2 releases is complicated as you correctly said, prob it would be easier to restart release 53 once 52.3.0 is over? [@alamb](https://github.com/alamb) WDYT? I am not sure what you mean by "restarting release 53" -- if you mean resync `branch-53` to `main` we might want to review what has gone in since release-53 was branched (I am not sure if there are more API changes, for example). Also we would have to re-test a bunch of downstream crates If we have enough bandwidth to make both releases, I think doing two simultaneously is fine (I haven't been tracking 53 closely enough to know how much more we are waiting on) **My personal suggestion is that we just forge on with this release and shoot to get an RC ready on Monday** One thing I do think is important is to make sure that all the fixes we have [backported to 52.3.0](https://github.com/apache/datafusion/issues/20681) get into `branch-53` as well (so users don't see regressions when updating to 53) @AmeerAssi or @mbutrovich would you be willing to help this (aka look at the PRs that went into branch-52 and make a backport PR for any that need to get into branch-53 as well? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
