(Snipping translators because this thread is irrelevant there.) David Balazic spake unto us the following wisdom: > Well, then you could have sent an email, before doing the release: > > Hi! > > At http://some.server/pidgin-2.7.0-rc.exe you can get the release > candidate > for Pidgin 2.7.0-win32. If anyone has time, please test it. > > Profit!
Sort of, but not really. First of all, we did float the release candidate to a small number of responsible people. It just turns out that "responsible people" and "windows users" are sets with a very narrow intersection, I guess. No surprise there. Second, this release contained a security-critical fix (see http://pidgin.im/news/security/), so floating a binary to the general public prior to embargo date would be bad form. Yes, there are various ways to mitigate that (release a binary without the security fix, release the binary without a changelog announcing the security fix, etc. etc.), but they all take time and effort, and many of them introduce the possibility for bugs to *still* creep through and/or require a developer with a Windows machine on which to build and test anyway. We all agree that testing would have been useful here -- what's not useful is the sarcastic remark to that effect, particularly without any clue as to how it happened or what the circumstances were. Ethan -- The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764
signature.asc
Description: Digital signature
_______________________________________________ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
