Samples don't indicate what's deployed on latest CDN

[corinagum]

As noted in #1556, our samples (with related updates or enhancements) are immediately deployed when a merge is made, but since deployment to latest is scheduled and not done per merge, /latest/ on CDN will not be able to utilize the changes indicated in new samples. It is not immediately visible to a user when changing their CDN is necessary.

Some ideas:

• Leave a note on the samples saying these changes will be reflected on /latest/ in the subsequent (predicted) release. The downside of this is we will have to go and update new-ish samples every release to remove this note.
• We can also inform users what release immediately after the sample incorporates the changes, meaning users can update their CDN to a more current version until the next release is made. This, however, puts the burden on the customer to know when to switch back to /latest/. We don't currently have an announcement feed, so conveying this to users is another problem we will have to solve. Relates to Look into ways to show developer story #1399

[corinagum]

"Samples available on master are not necessarily available on latest CDN" -- @compulim mentions that we can simply be more explicit in the samples so that users will know to check the CHANGELOG.md to see what samples are on master vs latest.

[corinagum]

Close - our current solution for this problem is to add new samples to our release notes -- update the CDN after the release is out.