Re: [Mailman-Users] The last release from the GNU Mailman project
On Sat, 2020-02-29 at 16:28 +0900, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > Well, Steve channeled me earlier, so I'll return the favor. > > And did it with extreme precision and accuracy. Sorry if I created > any misunderstandings. > > The only thing I have to add is that mailman-users@python.org is not > going away. Furthermore, I expect that Mark and I, at least, will be > here for the foreseeable future. That's because not only are existing > Mailman 2 installations not going away any time soon, there's every > reason to believe that people will continue installing Mailman 2 for > quite some time (even if it might be more convenient for *us* if > everybody would switch to Mailman 3 ;-). > > Steve Steve, given your comments above, please expand upon this scenario: If a CSF/CSS is identified in Mailman v2.1.30 in May-2020, what will be done to address it? -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses)
On Thu, 2020-02-27 at 14:51 -0500, Bill Cole wrote: > On 27 Feb 2020, at 14:24, Jim Popovitch via Mailman-Users wrote: > > > Personally, I'd like to see the GNU Mailman project have a formal > > Mailman 2.3 release that supports Python3, I feel that there would be > > a > > lot of support for that. > > I'm sure there would be widespread applause and congratulations if such > a thing were actually released. That sort of "support" is unhelpful > towards actually making such a release. > > The needed support is the actual skilled effort of writing the required > Python3 code. I don't have the time to hunt down the specific > statements, but I have vague recollections that both Barry and Mark have > said repeatedly that doing so would be substantially more effort than > they are willing to put into anything built on the MM2 architecture. Interestingly enough, here's a roadmap on exactly how to do it: :) https://engineering.linkedin.com/blog/2020/how-we-retired-python-2-and-improved-developer-happiness -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] The last release from the GNU Mailman project
On 2/28/20 11:28 PM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > Well, Steve channeled me earlier, so I'll return the favor. > > And did it with extreme precision and accuracy. Sorry if I created > any misunderstandings. None whatsoever, at least not from me ;) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] The last release from the GNU Mailman project
On 2/29/20 7:02 AM, Jim Popovitch via Mailman-Users wrote: > > If > a CSF/CSS is identified in Mailman v2.1.30 in May-2020, what will be > done to address it? I'd say it depend on the details of how serious the vulnerability is, how easy it is to exploit and how hard it is to fix. I am not opposed to Mailman 2.1.30-x security fix releases. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] The last release from the GNU Mailman project
On Sat, 2020-02-29 at 10:46 -0800, Mark Sapiro wrote: > On 2/29/20 7:02 AM, Jim Popovitch via Mailman-Users wrote: > > If > > a CSF/CSS is identified in Mailman v2.1.30 in May-2020, what will be > > done to address it? > > I'd say it depend on the details of how serious the vulnerability is, > how easy it is to exploit and how hard it is to fix. I am not opposed to > Mailman 2.1.30-x security fix releases. Thank you, it is reassuring to hear you say that. -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
