Conversion to standard Rails gem naming

[justin808]

In order to use the proper module name: cypress_on_rails, we're going to do the following:

• Create a new release for cypress-on-rails with the deprecation message that the name is changing
• Change the references of CypressDev to CypressOnRails, update the Gemspec and related files to indicate version 2.0.
• Publish new cypress_on_rails gem
• Update the name of the github repo to cypress_on_rails

[grantspeelman]

+1 on renaming CypressDev to CypressOnRails

to release a whole new gem really worth it?
Possible issues worth considering:

• searching rubygems will return 2 very similar named gems.
• the download count of the new gem will be less than the old gem for a long time
• Wild links on the internet will first take you to the old gem

[yagudaev]

I do think it is worth it for consistency. The new release with a description about the rename will tell people it has been renamed and avoid confusion.

Overtime it should be ok. FactoryBot was renamed from FactoryGirl too. The Ruby community is good at moving forward

[yagudaev]

Looks like #10 addresses this PR.

Btw, GitHub can automatically redirect to a new repo. So any links directly to the repo from other website will always be correct.

[vfonic]

For the old gem name you can also add postinstall message that will notify users of existence of the new gem name.

[vfonic]

You should really go ahead and "reserve" cypress_on_rails gem name on rubygems (push the same code that's in this gem or push gem boilerplate) right now. Otherwise someone will do it before you and you won't be able to take ownership of that gem name anymore.

[Systho]

Shouldn't this issue be closed now ?