potiuk edited a comment on pull request #13382: URL: https://github.com/apache/airflow/pull/13382#issuecomment-752570884
> Now we've released 2.0.0 we have in my mind already branched off, and only critical/major fixes will be in a 2.0.x - most other changes can wait to 2.1.0 I think it's just a matter of technicalities when it comes to branching but I agree with the principle. The only question is whether we should only cherry pick "critical fixes" and what "critical fixes" mean. I treat 2.0.1 mostly as "cleanup and stabilising" release. There are (and still will be some more) issues raised by first-time users, and while none of them are critical (well we have no definition of what it is), I think we already reached a critical mass of "bugfix" release (including some of the issues that still need diagnosing and fixes) and we have not added any "feature" yet. So for me pretty much every bugfix we have in 2.0 now an most of the "dev cleanup" should go there as well. So technically I think it will be easier to make sure there is no new feature added and move the branches and take "everything" in master to 2.0.1 (and refrain from merging any new features before we release 2.0.1). That will be IMHO better than cherry-picking all those changes needed because there will be quite a lot of them. And all the docs/dev tools changes should also go 2.0.1 I believe. Of course it also matters when we release 2.0.1 but looking at the number of issues and type of them, I'd say targetting 2.0.1 in the week 4-8 Jan might be a good idea. In which case just moving the branches might be much easier. ---------------------------------------------------------------- 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]
