> And it was a valid Release Candidate I think they messed up calling it a RC1 and leaving it as it is for so long. People started writing drivers and what not

> And it was a valid Release Candidate I think they messed up calling it a RC1 and leaving it as it is for so long. People started writing drivers and what not and were confident that the stack wouldn't change too much, now they are going to wait the official release (i.e. at least a year) because the trust is broken. They should have called it a beta and not let it live for like a year. You don't do that. > It should never be assumed that a Release Candidate is going to make it into production Of course, but release candidate also means that there wont be any significant change in the tooling or philosophy. RC2 has completely different tooling and the code is completely incompatible. It doesn't build up trust.