eladkal commented on PR #70932: URL: https://github.com/apache/airflow/pull/70932#issuecomment-5160731058
> I have no idea if it will, but I think this is a risk I woul like to avoid. I am actually planning to yank 1.0.0 release once we release 1.0.1 precisely because it had wrong metadata - because both registry and releases is something we are responsible for - and if this bears no problems to our users, I prefer to "fix" both code and metadata in unambiguous way. That is your call but I think you are taking it too far. Airflow registry is not the package metadata. By yanking you are sending a message that the package is broken why it is not. As I user I would lose heart beat waking up in the morning to see a version I use in production is now yanked. Please reconsider. You are trying to solve a problem but may consider many more also given shared governance model I would at least ask to let Clickhouse team a heads up before you make that action. -- 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]
