I am a Parsoid developer. I was participant #6 in the thread. As noted, reponses #14 and #16 were also from VE developers, and our contributions have continued. From my perspective the devs involved have done a pretty good job of picking out technical content from the discussion and acting on it (creating bugzilla entries and/or adjusting priorities of existing entries).
I will note that "# of bugzilla items for a component" is not any sort of proxy for "bugginess". Bugzilla is used for feature planning, for refactoring, for notes-to-self about minor cleanups, for discussion of build/testing infrastructure, etc -- and even when it is recording "bugs", those bugs vary greatly in severity (from "different than PHP rendering but probably it's the old PHP renderer which needs to be fixed" through "technically a bug but we grepped through all wikipedias and couldn't find anyone using this particular construct" up to "OMG"). And then there are the dups.
I appreciate Robert Rohde's quantification efforts. I'll note that I am currently reviewing a fix written by subbu for the single instance of "VE / Parsoid errors" in his sample. I thought that his point was excellent about all the existing help pages written using wiki syntax. It would be a great help if the community could help update those. --scott