potiuk commented on issue #19569: URL: https://github.com/apache/airflow/issues/19569#issuecomment-968093692
Yeah - the solution is really to semi-automate in a smart way. The fix I came up with in #19573 improves it in the way that it detects whethere we are (semi-automatically) releasing RC or "final image" and then asks a question if the "latest" tag shoudl be applied (latest should not be applied if we release a patch-level fix in an old branch - in case we ever do so). This way we should have far less chance of missing it. For fully automated releases, there is also always the question - who monitors and fixes problems if the "fully automated CI process" fails. Since this process of release is run every few weeks only (we do not fully release the X.Y.Z image more often than that), manual overlook over the release process is actually better than fully-automated release (as long as the semi-automation is complete). Our semi-automated process does a lot of tests on the image and you also visually see the results of it - you can see which providers were installed, you can see if there are no suspicious warnings there, you can see that the tests were actually performed (for example we test if all the required and important packages are importable and whether important "aifllow" commands actually work in the image. While "full automation" of that is possible, if the automation breaks and shows false-positive, having such manual inspection is really a "sanity check". So we have all the scripts tested that they return "success" with every PR but then every release a human eye looks at what's beeing released. I think this is really the best of both automated/manual worlds (as long you have process that make it possible you miss important steps - as we had). With improved semi-automation, I tihnk it's really how it should be (and as good as it gets). -- 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]
