Nusnus commented on PR #34031: URL: https://github.com/apache/airflow/pull/34031#issuecomment-1703860020
@hussein-awala @potiuk With every failure, we learn new lessons. As the most recent Owner at Celery, I am still discovering what's under the hood and I've been investigating the release flow for some time. > I really don't know how you manage the releases in Celery, I will check if this procedure is described somewhere. Unfortunately, the release flow is very lacking as I have discovered these past few days. As far as I am aware, there isn't an official updated procedure, which is why this latest release was messy. I am discussing this exact subject with the rest of the Celery Owners team to improve on this flow as part of a general effort from 5.3.0+ to increase the frequency of new releases, mainly with patch/bugfixes releases (which 5.3.2 was supposed to be, fixing important bugs), so I am totally onboard with improving this procedure. > However, deleting a release is completely different from yanking it, and IMHO it's a bad practice. As far as I know, to yank a python release we just need to yank it in PyPI, and update the github release by adding (YANKED) to the description. This is good feedback, I'll pass it on to our team to avoid such practices in the future. Thank you! > I think you really can't event have another 5.3.2 release. PyPi will not let you upload another 5.3.2 even if you delete the previous one Are you sure? I need to confirm that. If correct, then 5.3.4 is inevitable. This will cause a gap between 5.3.1 -> 5.3.4 but I guess that's the consequence of the removal instead of labeling of the versions. -- 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]
