Draft an interview-style Q&A post

You write for a WordPress plugin company's blog. You interviewed the lead developer
of your WooCommerce integration (async, via written responses to emailed questions)
about the upcoming roadmap. The answers are long, some ramble, and one question got
a non-answer.

RAW Q&A: [
"Q: What's the biggest change coming in the next release?
A: Honestly there's a lot going on, we've been heads down on performance stuff, the
database query layer, also some UI work on the settings page, I'd say if I had to
pick one thing it's probably the checkout speed improvements, we're seeing like 30%
faster checkout processing in testing so far, that's the one I'm most excited about
honestly.

Q: Will you be dropping support for PHP 7.4?
A: That's something we're definitely thinking about, there's a lot of factors, we
want to make sure our users have time to migrate, it's an ongoing conversation
internally."]
GOAL: [a Q&A post for the blog, keeps the developer's actual voice, roughly 4-5
question/answer pairs]

Work through this before drafting:
1. Tighten each answer to its actual substance (the checkout speed answer has one
   real headline fact, 30% faster processing, buried in three sentences of
   preamble), cut the rambling lead-up while keeping the developer's actual phrasing
   and personality intact, this isn't a PR rewrite into corporate-neutral voice.
2. Edge case: the PHP 7.4 answer doesn't actually answer the question asked (will
   you drop support: yes/no/when). Don't paraphrase this into a cleaner, more
   decisive answer than what was actually said, that would misrepresent the
   interview. Either keep the honest non-answer as-is with a light editorial note
   ("still an open question internally, as of this writing"), or flag it back to
   request a follow-up answer before publishing, don't invent a timeline the
   developer never gave.
3. Reorder questions for reader logic if needed (lead with the most interesting
   answer, the checkout speed number, rather than strictly the order they were asked
   in during the interview).
4. Add 1-2 sentences of intro context on who this person is and why their answer on
   this specific topic carries weight (their role building the integration), so
   readers understand the credibility behind the answers.
5. Pick the single most quotable line (the checkout speed stat, stated in the
   developer's own words) for a pull-quote treatment near the top of the post.

Draft the full Q&A post: intro, 4-5 tightened Q&A pairs in a sensible order, and a
pull-quote.

Replace the bracketed raw Q&A and goal above with your own.