potiuk commented on code in PR #33439:
URL: https://github.com/apache/airflow/pull/33439#discussion_r1295904336


##########
dev/breeze/src/airflow_breeze/provider_issue_TEMPLATE.md.jinja2:
##########
@@ -1,6 +1,10 @@
 I have a kind request for all the contributors to the latest provider packages 
release.
 Could you please help us to test the RC versions of the providers?
 
+The guidelines on how to test providers can be found in
+
+[Verify providers by 
contributors](https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors)

Review Comment:
   @eladkal -> What would you suggest ? This is unrelated and should be 
separate PR but  I agree 👍 
   
   `NOTE! You should Ctrl-C and restart the connections to restart airflow 
components and make sure new provider packages is used.` 
   
   is quite wrong . 
   
   The idea is that you need to restart the components to run it. Maybe you can 
phrase it well?
   



##########
dev/breeze/src/airflow_breeze/provider_issue_TEMPLATE.md.jinja2:
##########
@@ -1,6 +1,10 @@
 I have a kind request for all the contributors to the latest provider packages 
release.
 Could you please help us to test the RC versions of the providers?
 
+The guidelines on how to test providers can be found in
+
+[Verify providers by 
contributors](https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors)

Review Comment:
   @eladkal -> What would you suggest ? This is unrelated and should be 
separate PR but  I agree 👍 
   
   `NOTE! You should Ctrl-C and restart the connections to restart airflow 
components and make sure new provider packages is used.` 
   
   is quite wrong . 
   
   The idea is that you need to restart the components to run it. Maybe you can 
phrase it well?
   



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