You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2024/07/14 09:10:38 UTC
(airflow) branch main updated: Clarify PMC members vs PMCs (#40777)
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 e30e1ee540 Clarify PMC members vs PMCs (#40777)
e30e1ee540 is described below
commit e30e1ee5401ab60e76eb34dd198385660a34faee
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Sun Jul 14 11:10:31 2024 +0200
Clarify PMC members vs PMCs (#40777)
* PMC - is Project Management Committee
* PMC member - is a person who is a member of the commitee
We should avoid naming PMC member "a PMC" - while convenient
shorthand, it's confusing. We have some historical references to
PMC members as PMCs and this PR corrects that.
---
COMMITTERS.rst | 2 +-
RELEASE_NOTES.rst | 3 ++-
airflow/reproducible_build.yaml | 4 ++--
chart/dockerfiles/README.md | 2 +-
contributing-docs/01_roles_in_airflow_project.rst | 2 +-
dev/README.md | 4 ++--
dev/README_RELEASE_AIRFLOW.md | 4 ++--
dev/README_RELEASE_HELM_CHART.md | 10 +++++-----
dev/README_RELEASE_PROVIDER_PACKAGES.md | 9 +++++----
dev/README_RELEASE_PYTHON_CLIENT.md | 2 +-
dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md | 2 +-
docs/apache-airflow/howto/set-up-database.rst | 2 +-
12 files changed, 24 insertions(+), 22 deletions(-)
diff --git a/COMMITTERS.rst b/COMMITTERS.rst
index e3104e63eb..a85808c6bf 100644
--- a/COMMITTERS.rst
+++ b/COMMITTERS.rst
@@ -181,7 +181,7 @@ can become the Mentor and guide the proposed candidates on how they can become a
1. Candidate Proposer
- This is the person who launches the DISCUSS thread & makes the case for a PMC promotion
+ This is the person who launches the DISCUSS thread & makes the case for a PMC member promotion
2. Candidate Mentor
diff --git a/RELEASE_NOTES.rst b/RELEASE_NOTES.rst
index d26e91d216..c6ba245a88 100644
--- a/RELEASE_NOTES.rst
+++ b/RELEASE_NOTES.rst
@@ -183,7 +183,8 @@ Support for Microsoft SQL-Server for Airflow Meta Database has been removed (#36
After `discussion <https://lists.apache.org/thread/r06j306hldg03g2my1pd4nyjxg78b3h4>`__
and a `voting process <https://lists.apache.org/thread/pgcgmhf6560k8jbsmz8nlyoxosvltph2>`__,
-the Airflow's PMC and Committers have reached a resolution to no longer maintain MsSQL as a supported Database Backend.
+the Airflow's PMC members and Committers have reached a resolution to no longer maintain MsSQL as a
+supported Database Backend.
As of Airflow 2.9.0 support of MsSQL has been removed for Airflow Database Backend.
diff --git a/airflow/reproducible_build.yaml b/airflow/reproducible_build.yaml
index b2c492eb13..d2f63b8c04 100644
--- a/airflow/reproducible_build.yaml
+++ b/airflow/reproducible_build.yaml
@@ -1,2 +1,2 @@
-release-notes-hash: 37953284e268ff0273e6ba4d8ce9db4f
-source-date-epoch: 1718019354
+release-notes-hash: 7eeb7c1acdacfe80b87269f1a70b592c
+source-date-epoch: 1720945319
diff --git a/chart/dockerfiles/README.md b/chart/dockerfiles/README.md
index 8e663a082e..cd2a1e2934 100644
--- a/chart/dockerfiles/README.md
+++ b/chart/dockerfiles/README.md
@@ -21,7 +21,7 @@ Those are images that are needed for the Helm Chart.
In each of the images you can find "build_and_push.sh" script that builds and pushes the image.
-You need to be a PMC with direct push access to "apache/airflow" DockerHub registry
+You need to be a PMC member with direct push access to "apache/airflow" DockerHub registry
to be able to push to the Airflow DockerHub registry.
You can set the DOCKERHUB_USER variable to push to your own DockerHub user if you want
diff --git a/contributing-docs/01_roles_in_airflow_project.rst b/contributing-docs/01_roles_in_airflow_project.rst
index 8a8206e8f6..28f3237ab1 100644
--- a/contributing-docs/01_roles_in_airflow_project.rst
+++ b/contributing-docs/01_roles_in_airflow_project.rst
@@ -30,7 +30,7 @@ PMC Member
The PMC (Project Management Committee) is a group of maintainers that drives changes in the way that
Airflow is managed as a project.
-Considering Apache, the role of the PMC is primarily to ensure that Airflow conforms to Apache's processes
+Considering Apache, the role of the PMC member is primarily to ensure that Airflow conforms to Apache's processes
and guidelines.
Committers/Maintainers
diff --git a/dev/README.md b/dev/README.md
index 9ffd0798cc..2d6b88ec8d 100644
--- a/dev/README.md
+++ b/dev/README.md
@@ -118,10 +118,10 @@ Source tree - without polluting your editable installation with installed provid
The person acting as release manager has to fulfill certain pre-requisites. More details and FAQs are
available in the [ASF Release Policy](http://www.apache.org/legal/release-policy.html) but here some important
-pre-requisites are listed below. Note that release manager does not have to be a PMC - it is enough
+pre-requisites are listed below. Note that release manager does not have to be a PMC member - it is enough
to be committer to assume the release manager role, but there are final steps in the process (uploading
final releases to SVN) that can only be done by PMC member. If needed, the release manager
-can ask PMC to perform that final step of release.
+can ask a PMC member to perform that final step of release.
## Upload Public keys to id.apache.org and GitHub
diff --git a/dev/README_RELEASE_AIRFLOW.md b/dev/README_RELEASE_AIRFLOW.md
index b265280ba7..102ed72025 100644
--- a/dev/README_RELEASE_AIRFLOW.md
+++ b/dev/README_RELEASE_AIRFLOW.md
@@ -533,7 +533,7 @@ The following files should be present (9 files):
* .tar.gz + .asc + .sha512
* -py3-none-any.whl + .asc + .sha512
-As a PMC you should be able to clone the SVN repository:
+As a PMC member, you should be able to clone the SVN repository:
```shell script
svn co https://dist.apache.org/repos/dist/dev/airflow
@@ -1007,7 +1007,7 @@ Announcement is done from official Apache-Airflow accounts.
* Fosstodon: https://fosstodon.org/@airflow
Make sure attach the release image generated with Figma to the post.
-If you don't have access to the account ask PMC to post.
+If you don't have access to the account ask a PMC member to post.
------------------------------------------------------------------------------------------------------------
diff --git a/dev/README_RELEASE_HELM_CHART.md b/dev/README_RELEASE_HELM_CHART.md
index 42e3367983..892c8f2eac 100644
--- a/dev/README_RELEASE_HELM_CHART.md
+++ b/dev/README_RELEASE_HELM_CHART.md
@@ -29,7 +29,7 @@
- [Build RC artifacts](#build-rc-artifacts)
- [Prepare issue for testing status of rc](#prepare-issue-for-testing-status-of-rc)
- [Prepare Vote email on the Apache Airflow release candidate](#prepare-vote-email-on-the-apache-airflow-release-candidate)
-- [Verify the release candidate by PMCs](#verify-the-release-candidate-by-pmcs)
+- [Verify the release candidate by PMC members](#verify-the-release-candidate-by-pmc-members)
- [SVN check](#svn-check)
- [Source tarball reproducibility check](#source-tarball-reproducibility-check)
- [Licence check](#licence-check)
@@ -376,9 +376,9 @@ Note, you need to update the `helm gpg verify` output and verify the end of the
Note, For RC2/3 you may refer to shorten vote period as agreed in mailing list [thread](https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm).
-# Verify the release candidate by PMCs
+# Verify the release candidate by PMC members
-The PMCs should verify the releases in order to make sure the release is following the
+The PMC members should verify the releases in order to make sure the release is following the
[Apache Legal Release Policy](http://www.apache.org/legal/release-policy.html).
At least 3 (+1) votes should be recorded in accordance to
@@ -402,7 +402,7 @@ The following files should be present (7 files):
* `airflow-{VERSION}.tgz` + .asc + .sha512
* `airflow-{VERSION}.tgz.prov`
-As a PMC you should be able to clone the SVN repository:
+As a PMC member, you should be able to clone the SVN repository:
```shell
svn co https://dist.apache.org/repos/dist/dev/airflow
@@ -842,7 +842,7 @@ Announcement is done from official Apache-Airflow accounts.
* Fosstodon: https://fosstodon.org/@airflow
Make sure attach the release image generated with Figma to the post.
-If you don't have access to the account ask PMC to post.
+If you don't have access to the account ask a PMC member to post.
------------------------------------------------------------------------------------------------------------
diff --git a/dev/README_RELEASE_PROVIDER_PACKAGES.md b/dev/README_RELEASE_PROVIDER_PACKAGES.md
index 26a1fecbc7..749f89e106 100644
--- a/dev/README_RELEASE_PROVIDER_PACKAGES.md
+++ b/dev/README_RELEASE_PROVIDER_PACKAGES.md
@@ -738,7 +738,7 @@ EOF
Due to the nature of packages, not all packages have to be released as convenience
packages in the final release. During the voting process
-the voting PMCs might decide to exclude certain packages from the release if some critical
+the voting PMC members might decide to exclude certain packages from the release if some critical
problems have been found in some packages.
Please modify the message above accordingly to clearly exclude those packages.
@@ -757,7 +757,7 @@ The following files should be present (6 files):
* .tar.gz + .asc + .sha512 (one set of files per provider)
* -py3-none-any.whl + .asc + .sha512 (one set of files per provider)
-As a PMC you should be able to clone the SVN repository:
+As a PMC member, you should be able to clone the SVN repository:
```shell script
svn co https://dist.apache.org/repos/dist/dev/airflow/
@@ -1345,7 +1345,8 @@ NOTE!
As a rule we announce only new providers that were added.
-If you believe there is a reason to announce in social media for another case consult with PMCs about it.
+If you believe there is a reason to announce in social media for another case consult with PMC
+members about it.
Example for special cases:
@@ -1361,7 +1362,7 @@ Announcement is done from official Apache-Airflow accounts.
* Fosstodon: https://fosstodon.org/@airflow
Make sure attach the release image generated with Figma to the post.
-If you don't have access to the account ask PMC to post.
+If you don't have access to the account ask a PMC member to post.
------------------------------------------------------------------------------------------------------------
diff --git a/dev/README_RELEASE_PYTHON_CLIENT.md b/dev/README_RELEASE_PYTHON_CLIENT.md
index 215cb714f6..1a2d29e764 100644
--- a/dev/README_RELEASE_PYTHON_CLIENT.md
+++ b/dev/README_RELEASE_PYTHON_CLIENT.md
@@ -294,7 +294,7 @@ The following files should be present (6 files):
* .tar.gz + .asc + .sha512
* -py3-none-any.whl + .asc + .sha512
-As a PMC you should be able to clone the SVN repository
+As a PMC member, you should be able to clone the SVN repository
```shell script
svn co https://dist.apache.org/repos/dist/dev/airflow/clients/python
diff --git a/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md b/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md
index aa1c621864..9454734a3d 100644
--- a/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md
+++ b/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md
@@ -76,7 +76,7 @@ We think so. The release manager's role is nicely described in
[Release manager chapter of release publishing ASF infra docs](https://infra.apache.org/release-publishing.html#releasemanager).
There is far more complete description here that describes the whole process
[Release management policy](https://www.apache.org/legal/release-policy.html#management) - also mentioning
-that it's the PMC's responsibility (and particularly PMC chair's) to adhere to the process.
+that it's the PMC member's responsibility (and particularly PMC chair's) to adhere to the process.
# What's the role of individual maintainers?
diff --git a/docs/apache-airflow/howto/set-up-database.rst b/docs/apache-airflow/howto/set-up-database.rst
index 462cdade68..1b371f2172 100644
--- a/docs/apache-airflow/howto/set-up-database.rst
+++ b/docs/apache-airflow/howto/set-up-database.rst
@@ -324,7 +324,7 @@ MsSQL Database
After `discussion <https://lists.apache.org/thread/r06j306hldg03g2my1pd4nyjxg78b3h4>`__
and a `voting process <https://lists.apache.org/thread/pgcgmhf6560k8jbsmz8nlyoxosvltph2>`__,
- the Airflow's PMC and Committers have reached a resolution to no longer maintain MsSQL as a supported Database Backend.
+ the Airflow's PMC members and Committers have reached a resolution to no longer maintain MsSQL as a supported Database Backend.
As of Airflow 2.9.0 support of MsSQL has been removed for Airflow Database Backend.
This does not affect the existing provider packages (operators and hooks), DAGs can still access and process data from MsSQL.