Re:Ruby 2.1.2 is released
by dragonwriter on Monday May 19, 2014 @12:31PM
(#7768293)
> It appears there is at least one test failing on Windows that no one has had the time to fix.
The failing test for test_float wasn't Windows-specific (it looks from the tracker [1] that other packagers were hitting it even though it passing on the CI system used by core, its just that Windows users are more likely to be dependent on the packager rather than building from source without running the test suite, so RubyInstaller treating it as a blocker meant more on windows than other packagers treating it that way would mean on other platforms.)
Also, there've been a number of apparent fixes (the issue was closed 5 months ago, and then again 4 months ago), before it was (hopefully, finally) resolved four days ago. Its not -- well, for the last half or so of the bugs life -- an issue of no one taking time to fix it
> Considering that we are almost half way to the 2.2 release date (Dec 2014), it seems like Windows support may end up becoming a second-class citizen.
Irritating as it is for RubyInstaller users, this doesn't really seem to be a result of less attention being paid to Windows.
The failing test for test_float wasn't Windows-specific (it looks from the tracker [1] that other packagers were hitting it even though it passing on the CI system used by core, its just that Windows users are more likely to be dependent on the packager rather than building from source without running the test suite, so RubyInstaller treating it as a blocker meant more on windows than other packagers treating it that way would mean on other platforms.)
Also, there've been a number of apparent fixes (the issue was closed 5 months ago, and then again 4 months ago), before it was (hopefully, finally) resolved four days ago. Its not -- well, for the last half or so of the bugs life -- an issue of no one taking time to fix it
> Considering that we are almost half way to the 2.2 release date (Dec 2014), it seems like Windows support may end up becoming a second-class citizen.
Irritating as it is for RubyInstaller users, this doesn't really seem to be a result of less attention being paid to Windows.
[1] https://bugs.ruby-lang.org/issues/8358