On Monday, 16 February 2015 at 16:00:29 UTC, ketmar wrote:
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.
I agree.
To be brutally honest the biggest release mistakes (which seems
to be getting worse lately) are D releases with outstanding
regressions. That's pretty unacceptable IMHO.
