The ocean gem is dead. Long live the ocean-rails gem!

[Peter Bengtson]

The Ruby gem ocean has been renamed ocean-rails. All repos using the gem have been updated.

There are several reasons for this. The most important one is that there already is a gem by the name of ocean on rubygems.org, which makes it impossible to release a gem of the same name using the standard distribution mechanisms. This in itself merits a rename.

The second reason is that it's not impossible that other languages than Ruby might be used for creating services in the future, which interface modules then would have similar suffixes.

I'm about to release the current version of ocean-rails, version 1.14.0, on Rubygems.org tomorrow, to claim the name. After that release, we will use Semantic Versioning (http://semver.org) for the gem. This also allows us to branch the gem in development.

[Peter Bengtson]

The ocean-rails gem v1.14.0 has now been released via RubyGems.org and thus is available just like any other gem, and you can do a gem install ocean-rails to install it locally or let bundle update do it for you after you've pulled next time. All repos have been updated accordingly.

If you want to require the ocean-rails gem in some other context, the recommended method is:

gem 'ocean-rails', '~> 1.0'

You can find ocean-rails here:

https://rubygems.org/gems/ocean-rails

[Peter Bengtson]

Version v1.14.2 has been released to Rubygems. It's functionally identical to v1.14.0 and v1.14.1, the only difference being that the license is specified in the gemspec.

[Peter Bengtson]

Version v1.14.3 has been released. Functionally identical to previous versions, it now has full RDoc documentation for all Ocean classes.