Thanks pupi for you comprehensive response to my question!
I will follow the links you provided (thanks again) and if I may, I'll add any comments later?
Re; Version 1.6.3 bugs... Having used/implemented Q2A on an active site since v 1.4.1. and with an established commuunity of some 40 active 'regulars' and just over 200 registered users. Those figures changed dramatically because of various frustrations (bugs?) in the software.
I would accept that the definition of what is a 'bug' and what is not. Is quite different depending on one's understanding of a literal definition of the meaning (coder vs user) and concentrating on the latter for a moment. I had many 'complaints' about the very badly implemented 'User Wall' facility, which came along after v 1.5.
The User Wall was a great idea (badly needed) but functionally, it was a disaster. I do appreciate the improvements to date eg. unrestricted deletion of posts and it was brought somewhat nearer to the surface (easier to find and access etc.)
Other regular 'user' issues came about because CKeditor. As we all know. Is rather less than user friendly and has a bit of a learning curve. Even allowing for its idiosyncrasies, adding pictures, links etc. Is too much of a challenge for normal users.
Just for clarification of my own standpoint. I mention the above as examples of what I would say are are not strictly 'bugs' within Q2A core with the caveat, that the latter (CKE) has a few within it but that's another issue. and the former, (user wall) just lacked said functionality and was rather buried away. Of course by definition, if a function doesn't exist then there isn't a bug... To conclude, these things matter to 'ordinary' users who after all, just want to add some content or other or post quick messages to their friends etc. And when things don't just 'click'n'go' They desert a websites in droves!
On the issue of what I would suggest are 'real' bugs?
Q2A is supposed to integrate with 'wordpress' out of the box and to a degree, it pretty well does. I had things set up and running smoothly for 2 out of 7 months of integration. That would suggest that things were 'configured' right at an 'admin' level? However, in 'real world' usage. many 'cracks' appeared to the point that I just installed it (again losing users) I regularly looked on here for info on resolving issues and others frustratingly posted similar problems to my own experiences but I over time I noted they were seemingly ignored and saw little point in repeating problems/points already raised? The same could be said of plug-ins such as the FaceBook module. I found its integration/implementation horrendously frustrating. It too would seem to work for a week or two and then suddenly keel over.
I accept that 'plug-ins' are effective bolt ons and as such, there is bound to be some scope for bugs to manifest. Whether they are bugs in the core or a given module, is impossible for me to call and only you guys who develop the latter can say for sure. Either way, doesn't that suggest that there are plenty of things to smooth out in 1.6.3 and surely the improvements made leading to .4, .5, - .9 etc. would at least show progress rather than have a leap from 1.6.3 to a promised 1.7 which is for whatever (and I'm sure valid) reason, seemingly on hold? and it looks like indefinitely.
As to testing and feeding back... I am also prepared to do that and it makes sense to encourage developers etc. But I call your attention to Jay's comments earlier. I would also add, that plugin developers have offered to share/lighten Scott's load and I don't think that has been taken up? Among others, you yourself have admirably made what look like practical and certainly 'active' improvements to what could and arguably should be part of the core. So it would seem there is quite capable help on hand and yet little movement?
I understand that for developers in particular. Upgrades to HTML5 and mysql are welcome and needed and so, the dev version of 1.7 probably has something to offer you guys. I see you mentioned a potential problem ahead regarding the proposed CKed upgrade and I note the point.
I personally, haven't had the software online for a while now. (since March) Because I was hoping for improvements in things like Wall Posting and when Scott announced in April that this was at least on the 'agenda' then it seemed to make sense to wait for 1.7 upward.
Finally and an observation really...
Q2A is fundamentally a good and functional piece of software although I did notice that 'spamming' had become a bit of an issue on last install. But essentially, It is a very good basic Q&A platform. Any problems are seemingly due to the implementation of additional functionality. So Kudos to GidGreen.
Perhaps from one perspective. A vanilla version minus 'wordpress' and other geegaws but with improved anti-spam control. Is an option... Delivery and maintenance of that might lessen the 'burden' on Scott. I'm assuming there is a framework for plugin dev's to work in for taking care of ancillary services?
I personally (and my own target userbase) want/need wallposting and blogging capabilities (it is a social networking age) and it is a pity that at least one of these has been dismissed as a core function. However, It is good to see there is hope outside of core developer philosophy.
Thank you again for the reply Pupi.