Hi all, Glibc 2.36 was released last week. I'd hoped to have an archive test rebuild done with a recent snapshot but with one thing and another this didn't happen. So I'd like some thoughts about what to do wrt getting the update in before feature freeze.
One option would be to start a test rebuild asap, fix the issues found and then upload 2.36. Another option would be to upload 2.36 asap, then start a test rebuild and fix the issues as they are found, and in parallel with running all the autopkgtests. I don't expect this to be a very disruptive update. Some header file shuffling is known to cause some build failures, but it shouldn't be too bad (famous last words!). What do the release team think? Cheers, mwh
-- Ubuntu-release mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
