To be clear, this isn’t about secrecy; it’s about uncertainty. We don’t want to promise to have a new feature out by a particular date when we know that it’s possible that the release could slip due to a variety of factors, such as a major bug being discovered late in the release process. Setting expectations that we can’t be positive we’ll deliver on can lead to worse customer impressions than not saying anything about scheduling, which is why companies usually don’t. With the holiday season approaching, release cadences can also become more unpredictable as people take time off to spend with their families, so there’s more uncertainty about when a given change will ship (including whether it’s before or after the new year).
The feature work to support non-backwards-compatible Dolby Vision on Apple TV and iOS will be available in upcoming releases of those clients and the media server, which I expect to be available within the coming weeks, but I hope you can understand why I’m not able (at a practical level, rather than just a policy one) to provide any more specific a guarantee than that.
