Hi,
Thanks for putting up the proposed schedule and for creating a GitHub project to provide this overview – I think this is really awesome! I was not aware of some of the tools provided by GitHub to track projects, and will look into using them more for libc++.
We shipped LLVM 14 with an unfortunate regression in std::span which makes adoption of LLVM 14 somewhat difficult in large code bases. Long story short, some valid code won’t compile anymore, and while workarounds exist, it’s a bit painful and it really shouldn’t be necessary since the code is 100% fine from a user’s perspective. This is my fault, I let that slip into the release, did not realize it was going to have the impact it has, and my fixes missed the final RC by a couple of days. Had I known the impact, I would have made this a release blocker.
We do have a workaround on the release/14.x branch already, but it missed the last release candidate. With the proposed release schedule, we would have to wait until May 31st for this issue to be fixed. Instead, I would like to express support for the release schedule changes you proposed here some time ago, and I wonder whether there would be interest for switching to this new process for the LLVM 14 release.
If that were to happen, it would reduce the time to get this fix to our users from 12 weeks to roughly 2 weeks, which would be really awesome. Thoughts?
Thanks,
Louis