cucumber-nagios
cucumber-nagios copied to clipboard
auxesis
Abandon Ruby 1.8.7: When?
Given RVM allows you to trivially run several Rubies, and then gemsets under each Ruby, can we assume the monitoring of systems/ops is upto date, i.e. Ruby 1.9.2?
Or is 1.8.7 support mandatory for Cucumber-Nagios? If so, it'd be nice to understand how different RVM env's can't workaround any issues.
I have every thing refactored and working on 1.9.2, with 2 examples failing on 1.8.7. One due to the generator producing different ordered output, annotying but inconsequential. The second due to realdirpath not being available in 1.8.7 likewise that too can be hacked around, but it'd be nice to draw a line under 1.9.2 and say no more looking back :)
In my Aruba branch all specs bar one trivial text test pass. The failure is due to the generator changing its output.
Anyway legacy plans would be useful to know.
Auxesis asked me to take over CN, so closing this issue, since it is resolved in: https://github.com/hedgehog/cucumber-nagios
A lot of people (myself included) are against running RVM in production. I don't think that cucumber-nagios should force people to use a particular version of Ruby.
1.8.7 support should be a priority, given that REE (which is based on 1.8.7) is very popular in hosting environments, and cucumber-nagios will likely be running there.
OK, I did manage to get everything to pass on 1.8.7. which was why I closed it. but the note about ree and 1.8.7 should probbaly go into the readme.md
Ruby 1.8.7 team will stop releasing bug fixes after June 2012. Security fixes will continue until June 2013, then it's really really EOL.
http://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7/
