Fine, I didn't know that guanchayuan was asking every single day despite you explained him.
I think the only way to calm down people asking for open source is to give a date of release.
Fair enough.
As for the date though, it's roughly set as after RC5. Still have to complete RC3 and RC4. So, the timeline is difficult to lock down at the moment I think and they want an independent code review first to determine if there are any issues that can be fixed before open sourcing.
I think the goal is to have it locked down and as solid as possible before open source release - so that when everyone takes the tech - it's rock solid and they can't blame Evan and team for any issues and say they didn't do their due diligence on it.
Why are these builds called RC anyhow? RC is Release Candidate, meaning it's a beta and if no problems are found and people like it then it goes gold and is released as-is. That is not what these builds are, there is no intention to release DRK as finished after RC3 (or 4 or 5) no matter how well it goes.
Why not just use proper beta numbering? Maybe call them milestone releases or something like that.