dstandish commented on PR #36767: URL: https://github.com/apache/airflow/pull/36767#issuecomment-1894091347
> > Otherwise the "public interface" is just unreasonably big. > > Might be but it does not limit us with providers. It doesn't cost us anything to make a major release for the sake of clarity. @eladkal it's a good point. I do see how the major release can be helpful with messaging that. However, I do also think it potentially dilutes the meaning of the major release. If we create a major release every time we rename some internal method, then user the major release is diminished as a signal of when there's an actual breaking change in behavior of the operator. So, in this way I think we can see a benefit to "reserving" the major release for chose behavior changes. It also does add a little friction when it comes to refactors and such when there's a method rename involved. All of that having been said, do you think this should go to the mailing list? -- 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]
