I am working on cutting out a release for Mailman Core, 3.2.1, soon. Most probably by end of this week. If you have anything small you really want to get into this release, please ping me, I'd prefer if we don't put anything huge. I'll cut out an -rc1 release EOD today.
We are going to move to more of SemVer[1] approach and avoid having to bump major versions (which, in our case, is minor version) if we don't need to. We will keep on bumping minor versions till we really need to bump major version due to backwards incompatibility reason. This would also help us make more point releases that downstreams can upgrade to, without having to worry about bumping major versions. We don't really break API everytime when bumping major versions, which is slightly confusing and hard to keep track of. This should also help us not worry too much about backporting fixes to old release branches. We will continue to release minor versions, till we have to bump major, after which the old version will be unmaintained. But in history of Mailman 3, we only had to break compatibility once with REST API change with 3.1 release. Finally, I'll keep the release codename of 3.2.0 series and keep 'Tom Swayer' reserved for the next major version bump, whenever we end up doing that. [1]: https://semver.org/ -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
