Updated README, rake tasks, and TravisCI build targets.

[jdantonio]

Deprecate in lieu of Concurrent Ruby

Several months ago @headius suggested that the code in this gem be merged into Concurrent Ruby and this gem be deprecated. Subsequently we:

• Created the ruby-concurrency organization within GitHub
• Moved several gems from the personal accounts of @headius and @jdantonio to the ruby-concurrency organization
• Merged the code from ruby-atomic into concurrent-ruby (numerous merged commits prior to PR #153)
• Released v0.7.0 which included the merged code
• Began troubleshooting issues with the native extensions from the community
• Discussed different ways to handle C/Java Native Extensions in the upcoming 0.8.0 release
• Spiked an implementation which retained the Java native code within the core concurrent-ruby gem...
• ...while moving the native C code into an extension gem

Recommendation

If the original plan discussed in Concurrent Ruby Issue #83 is still the plan then I recommend we merge this PR and make the final atomic release suggested by @headius back in May.

Thoughts? @headius @pitr-ch @mighe @chrisseaton @obrok @lucasallan

[coveralls]

Changes Unknown when pulling 46c28be on docs into * on master*.

[coveralls]

Changes Unknown when pulling b1b9901 on docs into * on master*.

[pitr-ch]

It think we should allow users to load just what they need from concurrent-ruby eg. concurrent-ruby/atomic and document it here. Maybe bumping to 1.2 or 2.0 would be better since this is biggish change.

[jdantonio]

This is also being discussed in a concurrent-ruby issue but I'm posting the answer here, too, for those who haven't read that other thread.

@pitr-ch Although it's not documented, we've always structured concurrent-ruby so that only a subset of the gem can be loaded. So require 'concurrent/atomic' should already work as you've suggested. We just need to update the documentation for that gem to be more explicit.

[jdantonio]

We've released concurrent-ruby and concurrent-ruby-ext 0.8.0. Are there any objections to me merging this PR and publishing one final release of this gem?

@headius @pitr-ch @mighe @chrisseaton @obrok @lucasallan

[chrisseaton]

Not from me.

[pitr-ch]

No, go ahead 👍

[mighe]

👍

[headius]

Go for it. Did I give you the rights you need, or do I need to do something?

[jdantonio]

@headius You shouldn't have to do anything. I just wanted to get everyone's buy-in before moving ahead.

[jdantonio]

Done! I've built the two gem packages and pushed them to Rubygems.