As someone who works in a similar space: please don’t ask engineers or the like to be able to make any statements on upcoming/unreleased products, updates, etc. Even in cases where the upper management isn’t communicating well or at all. For two reasons:
1) In many cases, if it hasn’t been given the OK by management, and it hasn’t been disclosed by the company already (i.e. it isn’t already public knowledge), management will get upset when they find out. It should be assumed the company will retaliate against the employee.
2) Things do happen during development, and so disclosures like this can have unintended consequences. In the sense of creating unintentional promises, providing intel to competitors, and so on. So management tends to run this stuff through processes intended to avoid that sort of thing. Some do it better than others, clearly.
To give you an example of what can happen, there was a project that had a yearly hardware cycle. So it’s common that when that year’s hardware is out the door, within a month or two, there’s engineering samples available for next year’s hardware so that work on software can go forward. Someone leaked information on one of those first engineering samples. It caused a huge stir in the blogosphere to the tune of “Oh, they are replacing X already?” as everyone assumed it was nearly ready to ship. It was also hardware from a partner company, so it damaged the relationship between the two companies. All this because one person decided to share details of a project in progress that wasn’t due for nearly a year.