A colleague at the UW reached out in one of our internal channels. He is looking to replace the Skype for Business client with the MS Teams and his testing said MS Teams client is not feature complete enough yet, but he referenced a MS article that it was complete now. I explained that he should trust his testing and that 'now' may really mean 'sometime soon'. I then used this article as an example of the ambiguity of 'now' in our current cloud world of rolling updates. I have been in a few presentations with Chris McNulty and I have been blow away by his delivery and knowledge across a range of SharePoint topics from Farm Administrations to Taxonomy, so I have a great deal of trust and respect for Chris and this comment doesn't change that. Here is what I said to my colleague -
"When you read to the bottom of this post it says " We expect to begin rolling this feature out to Targeted Release on or about January 29, 2018. We anticipate a slightly longer cycle than usual for the expansion of this release throughout Targeted Release and general availability to allow for sufficient time to gather and address your feedback." This was posted on 1/19/2018 so 'now' was never 'now'. When I read this I realize I don't know what 'Targeted Release' means either, but it must be different than 'First Release'. First release is a thing, or actually at least two things. There are 'First Release' tenants (we have a test\dev tenant in 'First Release') and there are users that are in a 'First release' group, but they don't see first releases that are only released to first release tenants. In any case my guess is that for our tenant 'slightly longer cycle' + ' Targeted Release on or about January 29, 2018' means I don't expect to see this highly desirable feature any sooner than the end of April. "