Much of this is fallout from the discovery of the POODLE bug last month, but problems with older versions of SSL and TLS have been well-known for some time. Google's Adam Langley said in an October blog, "... everything less than TLS 1.2 with an AEAD mode is cryptographically broken."
It was in that same blog that Langley announced accelerated plans for Google's SSL/TLS support. He immediately created a Chrome patch to remove support for fallback to SSLv3, the enabler of the POODLE bug. That patch became effective in the new version 39 of Chrome which went out yesterday on the Stable Channel. (Oddly, the change was not noted in any announcement or even the changelog, but Langley announced it in a tweet.)
Chrome 39 also rolls out "BoringSSL," Langley's name for their own fork of SSL/TLS code. They will continue to contribute to, take code from and share information with OpenSSL and LibreSSL. The point is to give them more control over which features go into Chrome. Langley plans eventually for BoringSSL to be used in Android and internal projects.
The Canary version (41) of Chrome introduces some interesting cosmetic changes. Canary is, by definition, an experimental version, so this language could change or disappear altogether when this version hits the Stable Channel.
In the Canary build Google has begun using the words "obsolete" and "modern" to describe implementations of SSL/TLS. The image below shows two examples:
This language only appears when the user investigates connection properties of an SSL/TLS site, so it's nothing the average user would see, but it could eventually translate into more conspicuous visual cues.