If you want to do something that is actually productive here, why don't you find a way to use your own resources and your own personal free time to resolve this issue?
Maybe you could run a very large mailing list server you'd be willing to use as a guinea pig for all RC's, so that we would have an independent certification process, whereby you willingly sign away your first born if the code proved to have bugs in it, even after you certified it as being perfect. -- Brad Knowles <[EMAIL PROTECTED]> Sent from my iPhone On Apr 15, 2008, at 8:56 PM, "Jim Popovitch" <[EMAIL PROTECTED]> wrote: > On Tue, Apr 15, 2008 at 9:44 PM, Brad Knowles <[EMAIL PROTECTED] > internet.org> wrote: >> Quoting Jim Popovitch <[EMAIL PROTECTED]>: >> >> >>> Fair enough. Where's the release then? >>> >> >> Dragon is right -- the code is up-to-date and waiting for >> translation, as >> do pretty much all RCs released by this project. >> >> >> >>> Look, I know you folks are working hard on this, and I certainly >>> don't >>> dis-respect that. >>> >> >> Actions speak louder than words, and your actions in this case tell >> me that >> you most definitely *do* dis-respect us. >> >> Feel free to act in some other manner that proves me wrong. >> >> >> >>> HOWEVER, the process flow needs some re-thinking. >>> You should not publicly release security vulnerability details >>> before >>> fixes are identified for current versions. I can't imagine that >>> you >>> don't already know that. >>> >> >> I don't care what you think. You don't run this project. We have to >> support a wide variety of languages, and we can't just release an >> English-only version when we think it's ready. >> >> The best we can do is to put out an RC and tell people what the >> reasons are >> for wanting to upgrade to this code, so long as they know it's only >> going to >> be available in limited numbers of languages. Others can wait for >> the >> updated versions that support their language of choice. >> >> Each person installing or running Mailman gets to make their own >> choice as >> to when they're going to pull that trigger. The security notices >> are out >> there, there is an RC available which addresses them. If you feel >> the >> burning need to have the latest and greatest code which avoids the >> more >> recent security issues, then go and install the RC. >> >> >> But unless you're putting up the money to run this entire project >> out of >> your own personal pocket, I'm tired of listening to you bitch at us >> for not >> following your rules regarding how a release should be done. > > Nice. > > Sad too. > > -Jim P. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
