Simon Hanna writes: > Up until now I was under the impression that the clients > (Postorius/Hyperkitty) always require the latest version of core.
We don't require that the client be Postorius or Hyperkitty though. While in one sense we're not responsible for what third party clients do *at all*, in another I don't think we should make it hard for them. It's also possible that a third party (hello, Systers!) might have modified versions of the code, and not realize that their "don't fix it 'cause it ain't broken" core isn't compatible with their up-to-the-minute Postorius that they pulled to get Abhilash's security patch. > Do we really want to add the burden of having to care for different api > versions in the clients? I don't think that's the question. The question is, "what can we do to make things easier for developers both in the Mailman project and out?" > In my view backward compatibiliy should be applied so that old clients > can still access newer versions of core. > I don't think it's a good idea to require Postorius to be compatible > with older(all?) versions of core. We don't. Only the current version. The problem is that "version" is a potentially large set. That *is* *our* fault (looking straight at Barry with one forearm on the emergency exit crashbar ;-). Steve _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
