This is an automated email from the ASF dual-hosted git repository.
potiuk 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 52a16bf332 Update description of release process to include options
for next RCs (#36506)
52a16bf332 is described below
commit 52a16bf332c6b3d39207a5467d504cb70403f820
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Sun Dec 31 17:28:31 2023 +0100
Update description of release process to include options for next RCs
(#36506)
* Update description of release process to include options for next RCs
Often we excluded individual providers from release and we have two
options how to handle them - either release them on their own with
an accelerated vote, or include the providers in the next wave of
providers.
This PR improves description of our process and email template to
explain it better and guide the release manager on what to do.
Also improved notification message
Co-authored-by: Hussein Awala <huss...@awala.fr>
---------
Co-authored-by: Hussein Awala <huss...@awala.fr>
---
dev/README_RELEASE_PROVIDER_PACKAGES.md | 61 ++++++++++++++++++++++-----------
1 file changed, 41 insertions(+), 20 deletions(-)
diff --git a/dev/README_RELEASE_PROVIDER_PACKAGES.md
b/dev/README_RELEASE_PROVIDER_PACKAGES.md
index 43d76d581c..c3129b01fd 100644
--- a/dev/README_RELEASE_PROVIDER_PACKAGES.md
+++ b/dev/README_RELEASE_PROVIDER_PACKAGES.md
@@ -992,27 +992,47 @@ that the Airflow works as you expected.
Once the vote has been passed, you will need to send a result vote to
d...@airflow.apache.org:
-Subject:
+In both subject and message update DATE OF RELEASE, FIRST/LAST NAMES and
numbers). In case
+some providers were excluded, explain why they were excluded and what is the
plan for them
+(otherwise remove the optional part of the message). There are two options for
releasing
+the next RC candidates:
+
+* They will be released as an ad-hoc release with accelerated vote
+ period on their own (when there are not many changes to other providers in
the meantime and when
+ we have a small bugfix for the providers that we want to release quickly.
+
+* They will be included together with the next wave of releases (our tooling
+ supports automated calculation of RC version for candidates for the next
wave of releases that
+ already had earlier RCs.
+
+Email subject:
```
[RESULT][VOTE] Airflow Providers - release of DATE OF RELEASE
```
-Message:
+Email content:
```
Hello,
-Apache Airflow Providers (based on RC1) have been accepted.
+Apache Airflow Providers prepared on DATE OF RELEASE have been accepted.
3 "+1" binding votes received:
-- Jarek Potiuk (binding)
-- Kaxil Naik (binding)
-- Tomasz Urbaszek (binding)
+- FIRST LAST NAME (binding)
+- FIRST LAST NAME (binding)
+- FIRST LAST NAME (binding)
+
+2 "+1" non-binding votes received:
+- FIRST LAST NAME
+- FIRST LAST NAME
+[optional] The providers PROVIDER, PROVIDER have been excluded from the
release.
+This is due to REASON HERE.
+The next RC candidates for those providers will be released [in the next wave
+of providers] or [as an ad-hoc release on their own with accelerated vote
period].
-Vote thread:
-https://lists.apache.org/thread.html/736404ca3d2b2143b296d0910630b9bd0f8b56a0c54e3a05f4c8b5fe@%3Cdev.airflow.apache.org%3E
+Vote thread: https://lists.apache.org/thread/cs6mcvpn2lk9w2p4oz43t20z3fg5nl7l
I'll continue with the release process, and the release announcement will
follow shortly.
@@ -1020,8 +1040,6 @@ Cheers,
<your name>
```
-
-
## Publish release to SVN
The best way of doing this is to svn cp between the two repos (this avoids
having to upload the binaries
@@ -1196,17 +1214,15 @@ the artifacts have been published.
Subject:
-[ANNOUNCE] Apache Airflow Providers prepared on <DATE OF CUT RC> are released
+[ANNOUNCE] Apache Airflow Providers prepared on DATE OF RELEASE are released
Body:
-```shell script
-cat <<EOF
+```
Dear Airflow community,
-I'm happy to announce that new versions of Airflow Providers packages were
just released.
-
-TODO: If there is just a few packages to release - paste the links to PyPI
packages. Otherwise delete this TODO (too many links make the message unclear).
+I'm happy to announce that new versions of Airflow Providers packages prepared
on DATE OF RELEASE
+were just released. Full list of PyPI packages released is added at the end of
the message.
The source release, as well as the binary releases, are available here:
@@ -1216,9 +1232,14 @@ You can install the providers via PyPI:
https://airflow.apache.org/docs/apache-a
The documentation is available at https://airflow.apache.org/docs/ and linked
from the PyPI packages.
+----
+
+Full list of released PyPI packages:
+
+TODO: Paste the list of packages here that you put on the side. Sort them
alphabetically.
+
Cheers,
<your name>
-EOF
```
Send the same email to annou...@apache.org, except change the opening line to
`Dear community,`.
@@ -1276,9 +1297,9 @@ Add the release data (version and date) at:
https://reporter.apache.org/addrelea
Don't forget to thank the folks who tested and close the issue tracking the
testing status.
-```shell script
-Thank you everyone.
-Providers are released
+```
+Thank you everyone. Providers are released.
+
I invite everyone to help improve providers for the next release, a list of
open issues can be found
[here](https://github.com/apache/airflow/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%3Aproviders).
```
