mcatanzaro commented on issue #1758: URL: https://github.com/apache/buildstream/issues/1758#issuecomment-1380788816
> I agree, but I don’t think anyone is mandating that release team members use latest fedora either I spend half my time on the _next_ stable Fedora, so using the latest Fedora is slow for me. Using a previous stable release is out of the question. We need to develop the next one. > (and I’m not sure that it’s suitable for fedora to wrap such a new python version into a “stable” release either). Similarly, Fedora often ships the _next_ stable python. This is essential to ensure the quality of python releases; otherwise, if no distros ship until the stable release, how to ensure the stable release actually works with a large body of python software? Same reason we build spring Fedoras with prerelease GCC, to ensure the GCC release is good. python 3.12 is just around the corner now. -- 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]
