Of course there won't ever be a statement with that wording since their external messaging is clear: "There is no RTM", "Windows as a service", etc. Because it's only marketing talk. There's nothing to "accept". RTM isn't "gone" as it's a milestone that's part of the development cycle, that hasn't changed. For RS1, that milestone is 14393, and for that reason people are going to keep referring to it as RTM.
The one thing that makes me believe that this won't be the final iteration of the Anniversary Update is the known BSOD issue with the Surface Book / Surface Pro 4. While this can and will be fixed with a new driver delivered via WU, wouldn't they want to bundle this fixed driver with the final release? Since the upgrade can and often will be applied via USB and without Internet access - wouldn't they want a version that doesn't potentially bugscreen on their flagship and Windows 10 showroom hardware?
Surface Book shipped without the ability to even sleep reliably for ages. Microsoft have a funny idea of quality control. It's not a big issue to ship this build anyway. They don't use a vanilla Windows 10 release on shipping surfaces, but a customised retail image. When they put together an RS1 version of this customised image, that's what'll go out to the showrooms and on new devices, and that'll have the new driver bundled into it.
I bet 1$ a new build will be out just before August 2nd + Final RS1 SDK (not yet available). "RTM" does not exist anymore, MS now digitally ships "Official Releases" to everybody when ready (OEM included), even hours before public ETA. 14393 only released on Fast Ring, no SDK, and it's still a bit rough to be considered Production level anyway. "14393" number is not a clean version number for a public build too. Even WZOR said it's not "RTM" (in the sense of Production/Public build)
Some people saying: This is not RTM Ok, I have one question for you. Why did they put the Release Preview ring? This ring is for cumulative updates of this build not for get new ones. If this is not the RTM, why did they put this?
Well I felt like putting build 14393 on my other computer (hoping for improvement) with joe public win 10 as you'd think in 2016 the system would be bullet proof using the computer in a simple way....it's win 10-64 and all I did was update Kaspersky and any updates for win 10, carried on using my other computer (this) with insider builds and went back to the other computer to see if updates had finished and everything had locked up and nothing worked using keyboard and mouse and had to reset by the computer
As I'm going to need to be deploying this to machines of my friends, will anyone be able to get hold of en-GB x86 and x64 home links? Thanks