Update rake version constraint

[backus]

I've updated the gemspec to permit rake 11.1.2. Devtools works on 10.4 and 11.1 so I just made the version more permissible. I usually would just bump the version but rake is literally the number one dependency in the ruby ecosystem so I don't think devtools should dictate the version bump when it doesn't need it.

[mbj]

@backus Shouldnt we simply use the latest major version of rake?

[backus]

@backus Shouldnt we simply use the latest major version of rake?

See the description.

I currently can't upgrade a dependency on one of our projects because devtools forces 10.4.2. Rake 11 is still under two months old so I expect that we would run into the same problem with other gems that aren't yet updated to allow Rake 11. If you want I can just set a reminder for myself to remove the Rake 10 version constraint in another month or so.

Another approach would be to release 0.1.7 and 0.1.8 of devtools at the same time with the only difference being that 0.1.8 requires rake 11. The download count of the two versions should reveal how many dependent apps can't yet use rake 11 due to a conflicting dependency.

[mbj]

Lets release support for Rake 11 for devtools, people with older rake requirements simply will not update devtools. I'm fine with that.

Reduces complexity.

[backus]

k fair enough

[backus]

@mbj updated