Page History

...

• Sending an email to dev@airflow.incubator.apache.org (after registering, c.f. Contributors' Guide84806170)
  • Best way to get a committer to answer a question
• Asking a question on https://gitter.im/apache/incubator-airflow
  • Most often, another member of the community can guide you
  • Sometimes, a committer might pop in, but it's a bit too distracting for committers to closely monitor that channel today
  • Best way to get a quick response, but may not be from a committer
• Open a JIRA when a bug is found & propose a PR with a Fix
  • Only way to get PRs approved or to report bugs

...

Does Your Company Use Airflow?

...

Note that more information as to how to setup your environment and run tests locally and on Travis-CI is available on the CONTRIBUTING.md rst on Github. This document links to several other documents:

• LOCAL_VIRTUALENV.rst
• STATIC_CODE_CHECKS.rst
• BREEZE.rst
• TESTING.rst

You can follow the example workflow to learn how your workflow should look like

When filing PRs, remember to: 

• Create a JIRA for your bug fix/feature enhancement to 
• rebase your fork : http://stackoverflow.com/a/7244456/1110993
• squash your commitsCreate a JIRA for your bug fix/feature enhancement - point the JIRA "External Issue URL" to your PR URL
• Preface your commit's subject & PR's title with [AIRFLOW-XXXYYYY], where XXX YYYY is the JIRA number, and add a JIRA link in the PR description
  • Some folks only preface the PR title with [AIRFLOW-XXXYYYY], but we also need the commit message subject to contain the JIRA id. This is because we use the subject line in the commit messages when creating the release notes. 
• add an Apache License header to all new files (If you set-up pre-commit-hooks, this will be done automatically for you when you try to commit for the first time).
• & follow the 7 rules of good Git commits
  

...