Major version releases should be optionally ignored. I would like to scope a gem to a supported version range, that may not be the latest version.
For example, several of our projects use Rails 3, but Gemnasium says that it's outdated, even though it's supported at 3.2.17 right now, simply because Rails 4.0.3 is out.
This is just one example, and occurs for lots of software regularly.58 votes
Thanks for the idea, it really makes sense, so we’re starting to evaluate how to implement this.
Per-user / Per-project option:
When a dependency hasn't released in a year, consider it dead, and encourage users to find a modern alternative.25 votes
We love the idea, but this requires a bit of stats to be exposed first. Anyway, this is certainly a direction we’ll take very soon. Thanks for proposing this.
This isn't a new language so much as a new Ruby gem source. We've started using rails-assets.org, and noticed that the gems there don't have dependencies. The gems there are auto-created from bower.json files, so you may be able to crosslink the two efforts.
Example gem that doesn't work as of yet: https://gemnasium.com/gems/rails-assets-c311 votes
Good idea! Thanks for reporting it
- Don't see your idea?