You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by je...@apache.org on 2022/12/30 20:51:47 UTC
[airflow] branch main updated: Update providers release instructions (#28657)
This is an automated email from the ASF dual-hosted git repository.
jedcunningham pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new a4b86dc087 Update providers release instructions (#28657)
a4b86dc087 is described below
commit a4b86dc08714a31931dc7b73c3b148b057dc0425
Author: eladkal <45...@users.noreply.github.com>
AuthorDate: Fri Dec 30 22:51:39 2022 +0200
Update providers release instructions (#28657)
---
dev/README_RELEASE_PROVIDER_PACKAGES.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/dev/README_RELEASE_PROVIDER_PACKAGES.md b/dev/README_RELEASE_PROVIDER_PACKAGES.md
index 29bdda0364..7acbf77689 100644
--- a/dev/README_RELEASE_PROVIDER_PACKAGES.md
+++ b/dev/README_RELEASE_PROVIDER_PACKAGES.md
@@ -27,6 +27,7 @@
- [Prepare Regular Provider packages (RC)](#prepare-regular-provider-packages-rc)
- [Increasing version number](#increasing-version-number)
- [Generate release notes](#generate-release-notes)
+ - [Open PR with suggested version releases](#open-pr-with-suggested-version-releases)
- [Build provider packages for SVN apache upload](#build-provider-packages-for-svn-apache-upload)
- [Build and sign the source and convenience packages](#build-and-sign-the-source-and-convenience-packages)
- [Commit the source packages to Apache SVN repo](#commit-the-source-packages-to-apache-svn-repo)
@@ -161,6 +162,15 @@ breeze release-management prepare-provider-documentation \
--base-branch provider-cncf-kubernetes/v4-4 cncf.kubernetes
```
+## Open PR with suggested version releases
+
+At this point you should have providers yaml files and changelog updated.
+You should go over the change log and place changes in their relevant section (breaking change, feature, bugs, etc...)
+Once finished you should raise a PR : Prepare docs for MM YYYY wave of Providers
+In the PR we will verify if we want to release a specific package or if the versions chosen are right.
+Only after PR is merged you should proceed to next steps.
+
+
## Build provider packages for SVN apache upload
Those packages might get promoted to "final" packages by just renaming the files, so internally they