One thing I will give X-Plane credit for is that - when they originally released XP-12 - they were very up-front about the fact that it WASN’T ready for prime-time, there WOULD be bugs, that it’s essentially a beta release, and they’re releasing it into the wild so that they can gather failure data as rapidly as possible. (End users have a particular talent for finding bugs that the devs can’t find. 
)
Their idea, (AFAIK), is that they wanted to capture as many data-points and failure modes as possible so that when it went to “official release” status, the primary failure vectors[1] would have been identified and the lion’s share of the issues would be resolved.
==================== Footnotes ====================
- Failure vector:
The reason why a particular failure wasn’t identified and where else can this particular class of failure occur.
Example of a failure vector analysis:- Failure:
Roads are not rendered correctly with respect to elevation.
(Roads either float in the air or disappear within forests or mountains, etc.) - Root cause:
Road placement logic did not have access to the elevation data for that particular road in that particular location. - Solution:
Change the class “roads” to include elevation data in the rendering sub-class. - Other possible locations of the same error:
Class “rivers”
Class “railroad_tracks”
Sub-class “Highways”
(etc.)
- Failure: