Skip to content

Conversation

@zhongjiajie
Copy link
Member

@zhongjiajie zhongjiajie commented Feb 27, 2020


Issue link: AIRFLOW-6719

Make sure to mark the boxes below before creating PR: [x]

  • Description above provides context of the change
  • Commit message/PR title starts with [AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID*
  • Unit tests coverage for changes (not needed for documentation changes)
  • Commits follow "How to write a good git commit message"
  • Relevant documentation is updated including usage instructions.
  • I will engage committers as explained in Contribution Workflow Example.

* For document-only changes commit message can start with [AIRFLOW-XXXX].


In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

@boring-cyborg boring-cyborg bot added area:CLI area:dev-tools area:Scheduler including HA (high availability) scheduler k8s labels Feb 27, 2020
@zhongjiajie zhongjiajie changed the title Add pyupgrade [AIRFLOW-6719] Add pyupgrade Feb 27, 2020
@ashb
Copy link
Member

ashb commented Feb 27, 2020

Should we hold off on this PR until we are done with 1.10.x backports entirely, as that PR makes any future backports all but impossible.

@zhongjiajie
Copy link
Member Author

Related PR #7343

@zhongjiajie zhongjiajie changed the title [AIRFLOW-6719] Add pyupgrade [AIRFLOW-6719] Introduce pyupgrade to enforce latest syntax Feb 28, 2020
@zhongjiajie zhongjiajie changed the title [AIRFLOW-6719] Introduce pyupgrade to enforce latest syntax [AIRFLOW-6719][WIP] Introduce pyupgrade to enforce latest syntax Feb 28, 2020
@stale
Copy link

stale bot commented May 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label May 13, 2020
@zhongjiajie
Copy link
Member Author

not stale, wait until backport packages finish

@stale stale bot removed the stale Stale PRs per the .github/workflows/stale.yml policy file label May 13, 2020
@stale
Copy link

stale bot commented Jun 27, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@potiuk
Copy link
Member

potiuk commented Jun 27, 2020

@zhongjiajie -> backports are fiinished. You can proceed with that :)

@stale
Copy link

stale bot commented Aug 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Aug 15, 2020
@stale stale bot closed this Aug 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:CLI area:dev-tools area:Scheduler including HA (high availability) scheduler stale Stale PRs per the .github/workflows/stale.yml policy file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants