MrBounty commented on PR #36797: URL: https://github.com/apache/airflow/pull/36797#issuecomment-1966281156
> > Would it be possible to access the feature by creating a branch from my version of Airflow that includes your changes? I'm still learning the ropes of Git, so any guidance on the feasibility of this would be greatly appreciated. > > Sure but it is does not come with any guarantees whatsoever, it might break any time and if it breaks it might stay broken for a long time. However if you will, you can definitely run airflow locally from latest main and if you see any issues, you can even fix them via PR (this is what most people contributing here are doing). > > You can follow contribution flow -> see https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst as an entry point - then you have local virtualenv or `Breeze` contenerized development environment working - where you can more or less easily run airflow, but you have to be prepared for all the cases - like having to wipe your database, reinstall things from scratch, having your machine blow up becaus of used memory and CPU and all the bad things that can happen during the development. We cannot recommend it for running anything tha resembles productoin, and you should not put too much faith on being able to continue using the same instance when 2.9.0 is released, most likely you will have to reinstall everything from the scratch and wipe your database (and you will likely do it several times till the release date). But it also gives you the opportunity to contribute back and improve things. > > Also for that you need to learn git and branching etc. based on the contributing guide, there is an expectation that you know what you are doing there. > > There is no other "approach" that allows you to run things which are not released officially in production. Whatever we do here is purely for development and contribuion purposes. If you want to be exclusively a user, then releasing the software is a Legal Act of the Apache Software Foundation, and only then when the software is formally released and there are 3 binding +1 votes from the PMC members, the software we release should be used by the users who are not contributors. This has legal, licencing implications and even if we would like to, we cannot ever say that whatever we have in the repo is "usable" by users. It's usable to do contributions. Full stop. Thank you! This is what I was missing, specially the how to contribute. I will take a look -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
