Rubocop: 1.0?

Created on 29 Mar 2016  路  3Comments  路  Source: rubocop-hq/rubocop

Lots of folks depend on Rubocop these days, but I haven't seen a discussion about the path to 1.0.

@alexdowad seems to have some thoughts on the subject in https://github.com/bbatsov/rubocop/issues/2783

Is Rubocop naturally approaching stability right now, or would there have to be a concerted effort to be ready for 1.0? Could the maintainers kindly share their thoughts here?

Thanks so much for your hard work!

All 3 comments

I don't see us releasing 1.0 any time soon. There are a lot of cops that have to be implemented and refined yet, and the configuration setup is less than ideal right now. I hope that we'll get there eventually, but ti's definitely not something I'm actively pursuing. We also don't have a real extension api, we have to move the Rails stuff to separate gem and to create a proper manual...

As it stands, we're making breaking changes pretty often and I don't want us to release one new major release per month for trivial breaking changes.

Thanks so much @bbatsov. That is very helpful.

How would you feel about a 1.0 milestone and opening issues for the items you mention (if they aren't already being worked on)? Do you think it would be help increase the clarity around the work to be done, or would it be more of an overhead burden?

Guess I'll just close this for now. I still feel that 1.0 is far away into the future.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

NobodysNightmare picture NobodysNightmare  路  3Comments

bbugh picture bbugh  路  3Comments

benoittgt picture benoittgt  路  3Comments

ecbrodie picture ecbrodie  路  3Comments

Aqualon picture Aqualon  路  3Comments