Devise a robust, transactional system for "publishing" repository versions about xeps HOT 2 OPEN

I would like to propose an alternative to this, which would hopefully be much easier to do.

If I understand correctly, we basically want historical versions of XEPs, the attic is what we currently call this. But this is highly brittle, because we are trying to create our own transactional system instead of using a database or git, but we already have git, and developers looking at XEPs are already used to the concept of history etc, so I think what we really want is just a way to view historical XEPs ?

Just like how with anything else I'd go to https://github.com/xsf/xeps/blob/master/xep-0368.xml and click "commit" and then "parent" or "history" and then click to look at past versions? Except we'd want these rendered as XEPs right? Why not just write a tool to do exactly this, using git? Possibly even taking gitea/cgit/rgit and just adding a xep-rendering-extension similar to how they render markdown now? Or go through history and using xep2md create a git repo with the same history except XEPs are markdown and then github will render them for free for us?

tl;dr find a way to use existing git viewing tools to solve the attic for us

Do any of those sound acceptable? I understand this slight process change may require Board approval but I can't imagine they'd have a problem with it.

from xeps.

While this helps with viewing, it doesn't help with automating the email sending process, does it?

from xeps.