On Mon, Jan 26, 2026 at 07:32:39PM +0800, Kevin J. McCarthy wrote: > On Mon, Jan 26, 2026 at 08:56:58AM +0100, Fabian Groffen via Mutt-dev wrote: > >Why don't you do it now, and declare 2.3.0 a "last" release that will not > >receive any updates. If there's a problem, that needs resolving that is > >too big not to easily backport to 2.3.0, just release 2.4.0. > > > >I think with the effort to get things going again, perhaps it is nice > >when all of that can be done immediately on a codebase that's formatted > >in the way it should be. > > I'm willing to consider doing it now. Traditionally, stable branch releases > are just for security issues and important bug fixes. I try to keep the > changes small, so while there might be some pain in merges it's probably not > insurmountable. > > How do others feel?
If we're going to do a style clean-up, (which seems like a good idea that has general consensus), it would probably be worth documenting somewhere what the expected style is for new code.
