o-nikolas commented on PR #30727:
URL: https://github.com/apache/airflow/pull/30727#issuecomment-1589877599

   Hey @pierrejeambrun, thanks for weighing in! Most of the items have been 
discussed above, but here are some quick replies:
   
   > We have no policy for optimisation PR but we had issues lately with some 
of them breaking things unexpectedly, I am definitely in favour of what has 
been said -> optimisation PR goes into minor release from now on.
   
   Yupp, I never from the beginning was trying to get this merged into a patch 
release. I think that was maybe assumed at some point but it was never my 
intention.
   BTW, can you link an Issue/Slack thread for the optimization issue you're 
referencing? I'm curious!
   
   > 
   > @o-nikolas if you experience many annoying conflicts while maintaining 
this open, this is exactly what will happen for the RM. So we can either do 
what Jarek suggest with PARKING it, but then the burden is on you and that’s 
not fun, OR we can merge this knowing that it “might” cause painful cherry 
picking, and if it does release 2.7.0 earlier. (That would go in favour of 
release more often and ease the pain).
   
   Yeah, as I said above, if I'm resolving conflicts anyway I'm more than happy 
to resolve any conflicts that RM encounter. In fact I'm more than happy to 
start doing releases altogether :smile: 
   
   > Is there a specific reason that we only do a few minor release during the 
year ? Can we just make one on a “necessary” basis ?
   
   +1 to release early and release often! (as long as we're sure they're stable 
releases for our users of course).


-- 
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]

Reply via email to