On Sun, 15 Feb 2015 18:19:49 -0800, Andrei Alexandrescu wrote: > Folks, we want to get 2.067 out the door on March 1. That's two short > weeks from now. We really need all hands on deck to make this a > successful release.
we can't. this issue, for example, was known for monthes (or, maybe, years?), yet there is no sign that it's something that MUST be fixed for release. what i want to tell is that there is no release plan, no feature freeze before releasing, no easy accessible and automatically maintained list of release blockers and so on. there is no sense in pretending that we have that, and there is no way to force people to do it. just freese, release what we have and then make some patch releases to fix the obvious blocking (and accidentally missed) bugs, if any. make "just another release in line", with 2.068 in four-six month and so on.
signature.asc
Description: PGP signature
