Doesn’t the module start internal testing from the moment it can actually be loaded into DCS? Isn’t that testing each time they load it up to see what it’s doing, even if they’re still deep in coding?
This talk of “internal testing” sounds like an arbitrary milestone name that is just another step on the long road of obfuscation to destroy the time-honored alpha/beta/rc/gold standards that we all knew and understood. Therefore it was doomed by current marketing theory which dictates that you need to keep coming up with fancy sounding names for steps in the development process even when they are really meaningless when it comes to how far you are from release.
Actual release. Not Early Access release, which apparently pre-dates beta.
Bottom line is there was nothing wrong with the old naming scheme, it made sense, and it’s really ridiculous that it was replaced with this 12 step scheme where placement of the product is more semantics than anything else.