Initial Release

[bbatsov]

I'm adding this ticket, as a place to track down what needs to be done for an initial release.

@koic just cut the very first release of rubocop-performance and I guess he'll now replicate the process here.

@koic, what remains to be done?

[koic]

The main remaining tasks are:

• Extract TargetRailsVersion.
• Add documents.

Others are small tasks. I think that there is no work to be noted.

Among them, it may take a while to extract TargetRailsVersion.

[bbatsov]

Got it. Well, let's wrap the Performance cops removal first then, and tackle the rails stuff afterwards.

[koic]

@bbatsov Sorry I made you wait. RuboCop Rails release schedule.

/Cc @toshimaru

• Specify unset_nil: false to ConfigLoader.merge_with_default #54 requires Add unset_nil option to ConfigLoader.merge_with_default rubocop#7048. Wait for the next RuboCop core (> 0.69.0) release.
• When the next RuboCop core (> 0.69.0) is released, merge some documents and release RuboCop Rails 2.0.
• RuboCop core warns the extracting Rails cops when RuboCop Rails 2.0 is released.
• Remove the Rails cops from RuboCop core when the transition period is over.

I have made a rough preparation up to here.

On the other hand, the following is the work after extracting RuboCop Rails.

Extracting RailsTargetVersion is likely to take some time. Extracting the RailsTargetVersion is an internal implementation issue and will probably not affect users.

First of all, I'd like to extract RailsTargetVersion sometime after releasing RuboCop Rails.

[bbatsov]

First of all, I'd like to extract RailsTargetVersion sometime after releasing RuboCop Rails.

I agree. Keeping this in RuboCop itself is not a big deal for now.

#54 requires rubocop/rubocop#7048. Wait for the next RuboCop core (> 0.69.0) release.

Understood. I'll cut the new release ASAP.

[bbatsov]

The new release is out! I'm looking forward RuboCop Rails 2.0!

[koic]

RuboCop Rails 2.0.0 has been released!
https://rubygems.org/gems/rubocop-rails/versions/2.0.0