Adding end of life notice for CurationConcerns

Based on conversations on Slack and through email, the community has
agreed that CurationConcerns is end-of-life, but that decision may not
be as obvious to those outside the community's communication channels.

Related to samvera-deprecated/sufia#3181

README.md

@@ -11,6 +11,26 @@ Docs: [![Apache 2.0 License](http://img.shields.io/badge/APACHE2-license-blue.sv
 
 Join in: [![Slack Status](http://slack.projecthydra.org/badge.svg)](http://slack.projecthydra.org/) [![Ready](https://badge.waffle.io/samvera/curation_concerns.svg?label=ready&title=Ready)](http://waffle.io/samvera/curation_concerns)
 
+# End of Life Notice
+
+We envision the 2.x releases as the end-of-life for CurationConcerns. During 2017, the [Samvera community](http://samvera.org/) consolidated [Sufia](https://github.com/samvera/sufia) and [CurationConcerns](https://github.com/samvera/curation_concerns) into [Hyrax](https://github.com/samvera/hyrax):
+
+* [planning notes on consolidation](https://wiki.duraspace.org/pages/viewpage.action?pageId=78161232))
+* [release notes on the bridge of Sufia to Hyrax](https://github.com/samvera/hyrax/releases/tag/v1.0.0)
+* [release notes on the bridge of CurationConcerns to Hyrax](https://github.com/samvera/hyrax/releases/tag/v2.0.0)
+* [Samvera documentation for developers and managers](https://samvera.github.io)
+
+<hr>
+<br>
+<br>
+<br>
+<br>
+<br>
+<br>
+<br>
+<br>
+<br>
+
 A Hydra-based Rails Engine that extends an application, adding the ability to Create, Read, Update and Destroy (CRUD) objects (based on [Hydra::Works](http://github.com/samvera/hydra-works)) and providing a generator for defining object types with custom workflows, views, access controls, etc.
 
 ## Prerequisites