ephraimbuddy commented on PR #41067: URL: https://github.com/apache/airflow/pull/41067#issuecomment-2293698324
> > @potiuk good to merge or still hold this back? > > I am struggling with it a bit - because it will likely make it more difficult for contributors to add their tests to main - while we are anyhow targetting the AIP-44 to be ripped off from Airflow 3 eventually. > > Looking at the kind of issues we had to go through, it will be a bit of a pain to merge that one to `main` - only to remove it afterwards, so I'd rather cherry-pick and merge that one to v2-10-test, however technically speaking this is a "new" feature enabled there, so if we folow it literally, it should go to 2.11.0. Probably the same kind of issue that @uranusjr mentioned in the `[RESULT][VOTE]` discussion: https://lists.apache.org/thread/56b7bdrzszkqtd6kgy360okw72568ld2 > > So I **think** maybe we should have a v2-11-test branch already created and we should start cherry-picking thing there that do not belong to 2.10.0 (and periodically rebasing it - or use cherry-picker to simultaneously cherry-pick things to both v2-10-test and v2-11-test when cherrypicking stuff to v2-10-test. > > @utkarsharma2 @ephraimbuddy @kaxil @uranusjr @jscheffl - would love to hear your thoughts about it. Yeah. This is a concern. Should we have a branch called v2-dev where all airflow 2 PRs will go into, then the release manager would cherry-pick to v2-10-test when releasing? I think that having v2-11-test might make us miss PRs or having multiple places to PR to -- 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]
