Giving timescales to communities is universally a dangerous thing and are generally dodged until they can be completely certain of it themselves.

When nobody is willing to give a timescale it is a safe assumption that they simply don’t know internally themselves at this point in time. They might have some hopes and dreams, but there are a lot of surprises that can and almost always knock back timescales in dev.

Everything else however would be nice to hear, but I think it’s an unreasonable expectation to get a timescale if they don’t know themselves, and the only companies that ever admit to not knowing something are indie developers.

I can guarantee that when they know, we’ll know, because they want to be able to tell us that kind of information, but can’t. If they gave this community a timescale and then failed to deliver it would be a far bigger drama storm than ignoring the question, if they admit to not having a timescale then people ignorant of development realities will take it as evidence of incompetence. It’s just a lose-lose situation for them with the less impactful evil being to stay quiet.

Again though, talking about certain technical aspects would be nice, my assumption however is that in order to talk about the technical they need someone working on the technical to take time away from working on it to make sure the PR staff aren’t saying incorrect things and get the details correct. Often those staff in development teams are somewhat unwilling to do that compared to continuing to work on the problem.

But they should take the time to address the details of what they’re working on. It brings fevers down a few notches for a significant amount of time and relieves people’s worries knowing what is actually happening. It’s worth weeks of further quiet on the issue.