kaxil commented on pull request #13382: URL: https://github.com/apache/airflow/pull/13382#issuecomment-752488920
> Question: @kaxil - how are we going to proceed with the master changes to be released in 2.0.1 - my impression is that so far (and I thought until 2.0.1) everything in master will be part of 2.0.1 and then we 'actually' branch off and start cherry-picking. So far this is what we've done (and I think that was @ashb approach that we limit the need of cherry-picking to v2_0* branches. > > Is the assumption (with this change) that we will be now manually cherry-picking the the master changes to v2_0_test * branch as we did for v1_10_test and that we should mark all the PRs that are worth cherry-picking with 2.0.1 milestone? > > I would love to clarify it :). I have a number of changes in master that I might have missed marking with '2.0.1' milestone over the last couple of days and they for sure should be part of 2.0.1 That assumption still stands correct :) -- We will rebase v2-0-test on top of Master but just remove this commit. At any point from now to future, we should **_try hard_** not diverge from Master and even if we need to -- try and stay as close as possible. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
