Santiago, could you PLEASE stop arguing with me? I am not going to agree with you!
I was there when the decision about the always releasable testing was made and it was most certainly *not* about making testing ready for production use. It was made, to _reduce_ the freeze period, that's all. Heck, that's even the first sentence when you look up the rationale on the Debian Wiki [1]. Really, please stop defending entitled users who think that just because it's free software they get to work developers to work on the software for them for free. We have one release which is called "stable" and that is what people are supposed to use. Both "testing" and "unstable" were never ever to be used in environments where reliability and the absence of bugs is important, those have always been _development_ releases. It's simply not practical to keep something production-ready when you're in the middle of the development process. We have had enough head-aches with all the transitions: Be it gcc-5 with its new libstdc++6, Perl 5.22 or Ruby 2.3 and whatnot. I have had tons of issues to fix on all the architectures I am supporting and I have spent many many nights and days in contributing Debian. Thanks, Adrian > [1] > https://wiki.debian.org/Debate/JessieReleaseProcess/AlwaysReleasableTesting -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
