Provide version fallback for versioned pages

[trainman419]

Many ROS wiki pages try to maintain backward compatibility with old versions of ROS by supplying different versions of the page for different versions of ROS.

When a new version of ROS is released and the wiki is updated to default to the new version of ROS, these pages often appear empty at first glance, even though the documentation from the previous version of ROS most likely still applies. I've had to update 3 or 4 pages in the last few days, since the switch to Indigo.

For example, the stereo_image_proc page has this problem.

Is it possible to have a 'latest' version or some way to specify an open-ended version range to use when displaying content? Maybe something as simple as groovy+ instead of groovy ?

[dirk-thomas]

I agree - that would be such a valuable feature to have.
We talk about it over and over again - especially when a new release comes out.

Someone should step up and implement that... @esteve @tfoote @wjwwood?
Or someone else could provide a pull request for that?