future plans for this repo / tagging / airflow versions / etc

[cloneluke]

Hi - even with managed airflow available on AWS, I still see a need for this repo. I have needs to customize around airflow that I can't do with managed airflow. I would like to start tagging releases in the repo with upgraded airflow versions. I would also like to do some other upgrades like pscopg2 instead of pygresql. Let me know if I can be a maintainer, I am happy to submit PRs without being a maintainer, but would want tagging as we advance this repo so people can always use older versions of the repo as they need to. (older airflow versions as an example)

[cloneluke]

#8

[thechaithanya]

As suggested here, I would recommend making changes in a new branch, as this branch was referred as part of blog post. Any changes to this branch may invalidate the blog post.

Let's add changes to the new branch and add a note or update ReadMe about the new branch.
As a best practice, we can include a CHANGELOG file in new branch, to update the users about changes happening as part of it.