[AIRFLOW-7067] Pinned version of Apache Airflow

[potiuk]

---

Issue link: AIRFLOW-7067

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.

[codecov-io]

Codecov Report

Merging #7730 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7730      +/-   ##
==========================================
+ Coverage   86.88%   86.92%   +0.03%     
==========================================
  Files         924      924              
  Lines       44674    44792     +118     
==========================================
+ Hits        38816    38934     +118     
  Misses       5858     5858              

Impacted Files	Coverage Δ
airflow/bin/cli.py	97.66% <0.00%> (+2.87%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9ad1844...6a80f5f. Read the comment docs.

[potiuk]

BTW. I am going to simplify it even more - no need to store fixed requirements in setup.py

[potiuk]

All should be update and much nicer now @ashb !

[potiuk]

And all green!

[turbaszek]

Suggested change

	# [required] fetch the tarball and untar the source chnge into the directory that was untarred.
	# [required] fetch the tarball and untar the source, move into the directory that was untarred.

[turbaszek]

How should I know if I should use requirements or not?

[potiuk]

You do not have to - it's the recommended version of dependencies. This is just a hint that you can do it. I proposed to have "apache-airflow-pinned" package release separately. with clear purpose in mind "to have repeatable installation"

I agreed having the --constraint and having to know which version to install might be confusing - that was my point in the discussion - but there are different opinions. For now I just want to merge requirements.txt and it's maintenance mechanism so that we avoid further breakage. But the discussion continues here how to approach it:

https://lists.apache.org/thread.html/rf8b0ea9a7b93482734ae9e10e7d87f3c31679edb5eaf88496e733aa5%40%3Cdev.airflow.apache.org%3E

I invite you to take part in the discussion and propose some solutions/approach. I would really love to have yours (and others) opinions in the thread there.