Some good feedback here. I'll try to address your points as best I can.
On Twitter: Disagree that it's always the wrong approach, but it's definitely not always the right approach either. 140 characters is a blessing and a curse - it's harder to get a complete point across sometimes, yes, but it also forces things to be presented more concisely, which is great for certain types of feedback. We're not going to stop using Twitter, but we're continuing to learn about when it's not the right platform.
Also just as an aside, every account other than @WarcraftDevs should be treated as someone's personal account and not as the correct place to provide feedback or look for answers. That also means that it's completely their choice if they decide to mute or block someone.
On the Q&As: I agree that the experiment in the last one to answer more spec-specific questions didn't go well. I honestly don't think the live Q&As are a good way to answer those questions at all. Even if we were to somehow narrow it down to only "legitimate" questions (aside: what criteria determine "legitimate" anyway?), there's far more to answer than we can possibly fit into one Q&A, so we're always going to leave something out.
Secondly, it's important to remember that not everyone follows fansites closely, or saw the BlizzCon panels, or even the other Q&As. AK alt catchup is a great example - despite all of the other places we talked about what's happening in 7.1.5, it was still one of the most-asked questions. I'm glad that you had already heard about it, but clearly a lot of others had not, which made it absolutely worth answering.
I do agree, though, that the Q&As work best when we either stick to broader topics, or focus the entire thing specifically on one topic (like we did with the Professions, PvP, etc. Q&As a few months ago). As a whole, it's a format we're still experimenting with. I can't promise they'll all be great, but I can promise that we'll learn from when they aren't.
On Interviews: Mostly agree, although it depends on the interviewer. You're not likely to see the hard-hitting questions coming from a major gaming publication, but you might from a community site, podcast, etc. Personally, I actually think we need a lot more interviews with those community sites, especially those that focus on more niche playstyles - it's a great way to get answers to those people without "wasting" everyone else's time.
On the forums: I actually completely agree with you here. Our forum presence sucks. It's a big issue that we're working to fix. That's part of why I'm here, posting this, and will continue to be around these forums as much as I can. Resolving this issue will take some time - if it can ever be completely resolved - but we're working on it.
It's worth mentioning that part of the issue - the general lack of dev posts - has been because they've been focusing as much of their time as possible into working on the game. Part of trying to keep patches coming at a good cadence means we need all hands on deck to get the work done, which means less time for the dev team to spend on the forums. That in turn means that, when the devs do get time for the forums, they spend the vast majority of it just reading, so they can absorb as much feedback as possible. So, the community team (including myself, but many others as well) need to step in to fill that gap, in a way that doesn't make you go "Ooh, a blue post! Ugh, it's just a CM." We haven't been, but we're going to.
On Reddit: I also like AMAs, and agree with your thoughts here. I do think that there are some topics where they might work much better than the Q&As, and while I don't want to say what those are for fear of over-promising, it's a cool idea that I'll circulate around.
On Patch Notes: I think a lot of the issues with patch notes are actually symptoms of some of the above issues. The designers' notes are definitely a good addition, but those are intended as little snippets of explanation for the player who doesn't really keep up with fansites, interviews, forums (well, when there's posts on them), etc. It shouldn't, whenever possible, be the first place that the person reading this thread heard about something, unless it really only needs a couple sentences to explain. If we need to give more detail, we should be doing that ahead of time and just referencing that explanation in the patch notes.
We've also heard loud and clear that you guys want PTR Patch Notes back. It's a tough situation for us to solve, though I don't think it's an unsolvable one. The PTR, especially under Legion's development structure, is much more experimental and incomplete than it's been in the past. Having official patch notes makes each individual change - any of which could be reverted at any point - feel a lot more "final" than they really are.
Our approach for 7.1.5, then, was "let's focus on what it'll be when it's done" - that was clearly the wrong choice. Official PTR Patch Notes might not be the answer we need, but we definitely need a way to keep you more informed of what's happening, especially for class changes. Even something as simple as "Class Notes for PTR Build ABCXYZ" might fill the gap.
At any rate, thanks for this - it's given us a lot to think about. I know there's a big difference between saying we'll do better and actually doing better, but threads like this really help us actually improve things.
The one thing I should really say about this is the fact that you have ONE twitter account for EVERY form of feedback and question.
Why don't you like, delegate it out a bit?
you get the idea
Yes, not only is it acceptable to say, 'We don't know," or "We aren't sure yet," but that kind of transparency is absolutely necessary for quality feedback and communication. Those are great jumping off points to get good feedback from the community. Of course, hopefully you would give us more than just those statements. Hopefully, you would explain why you haven't been able to come to a decision yet, what you perceive to be the pros and cons, and why it is so difficult to make that particular call and then MAYBE the community could help you actually make the decision.
Even if our feedback won't help make the decision easier, understanding your thought process will make it easier to accept the decision once it is made.