utkarsharma2 commented on issue #36384:
URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868425100

   >
   > I am not sure if there will be RC2 for Waeviate, but we can release a new
   > version right after this one gets released as well.
   >
   Thanks for your consideration, releasing a new version after this release
   also works for me.
   
   > I've been slightly improving the release process to make it possible (and
   > easy) to have a more-or-less continuous release process. I have one more
   > small things to fix but as I explained to @eladkal
   > <https://github.com/eladkal> in a separate discussion, basically we
   > should be able to start a new release process right after we release
   > previous wave - and continue doing it all the time - even if some providers
   > get removed from the previouse wave. This should streamline our release
   > process, where we should be able to make provider releases even more
   > frequently - maybe even once a week - especially if we also introduce more
   > "rotating" position of release manager, so maybe that's a good thing to try
   > it right away :).
   >
   As you can see - for example - in the past wave we had to withdraw google
   > and databricks, so while we are releasing new changes in other providers,
   > in this wave the google and databricks providers are also included (google
   > with RC3 and databricks with new - breaking - 6.0.0 version rc1). All this
   > is going to be pretty much fully automated after one more small thing I
   > will need to add and we should be able just carry-over such previous
   > providers to new wave, which means that no matter what the result of voting
   > is, we will be able to start new wave right after we release the previous
   > one.
   >
   > That will also make our release waves smaller.
   >
   Considering providers are the most changed code in airflow's codebase, this
   sounds like a real time saver for getting the code out quickly. :)
   
   On Sun, Dec 24, 2023 at 4:15 AM Adam B ***@***.***> wrote:
   
   > I won't get a chance to test the RC until late next week, but #36248
   > <https://github.com/apache/airflow/pull/36248> worked when I ran the
   > changes locally.
   >
   > —
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/airflow/issues/36384#issuecomment-1868383200>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/ADDLAHMSXM2MMUCRLFOFZ7DYK5NKPAVCNFSM6AAAAABBAO623CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGM4DGMRQGA>
   > .
   > You are receiving this because you were mentioned.Message ID:
   > ***@***.***>
   >
   


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