3.2 is out - not in major distros yet AFAIK, but... at least I'm using it with home cut packages.

This will mean some config changes. Logic within the templates checking version numbers will be very messy and hard to update for new versions, I think - I am thinking in order to make this work we might need sets of config templates per version. Freeradius 4.0 will have similar needs.

We have had some changes in early 3.0.x to later 3.0.x which required template updates as well - which could have been perhaps better done as separate templates rather than updating in place.

I'm not too sure - I don't think we want to end up with a template tree for every version, but, backwards incompatible changes perhaps?

Perhaps a function to resolve template filenames - so we only create new ones if required, rather than lots of duplicates.
Gets a bit messy though, if we have a bugfix to one, we may have to update 3 or 4...