You're probably misunderstanding how this works in Debian, let me explain:
Installing ruby1.9.1 gives you /usr/bin/ruby1.9.1.
Installing ruby2.0 gives you /usr/bin/ruby2.0.
Installing ruby2.1 gives you /usr/bin/ruby2.1.
The "ruby" package is merely a package that points /usr/bin/ruby to one of those from above; installing ruby2.0 or 2.1 doesn't change where /usr/bin/ruby points to.
This is similar to the python packages.
Now 14.04 apparently froze at a time where jessie was in the middle of the transition from 1.9 to 2.0. (A similar thing would apply today: jessie already has ruby2.1, but /usr/bin/ruby is still 2.0.)
I don't know if Ubuntu has dedicated resources to ruby or not, but I doubt they can still change this for 14.04.
You're probably misunderstanding how this works in Debian, let me explain:
Installing ruby1.9.1 gives you /usr/bin/ruby1.9.1.
Installing ruby2.0 gives you /usr/bin/ruby2.0.
Installing ruby2.1 gives you /usr/bin/ruby2.1.
The "ruby" package is merely a package that points /usr/bin/ruby to one of those from above; installing ruby2.0 or 2.1 doesn't change where /usr/bin/ruby points to.
This is similar to the python packages.
Now 14.04 apparently froze at a time where jessie was in the middle of the transition from 1.9 to 2.0. (A similar thing would apply today: jessie already has ruby2.1, but /usr/bin/ruby is still 2.0.)
I don't know if Ubuntu has dedicated resources to ruby or not, but I doubt they can still change this for 14.04.