Timestamping the specification

[RieksJ]

For (candidate) standards documents, it is a good practice that whenever a version is ratified or otherwise assigned some state, this is mentioned in the document itself with the date at which that is done. This issue calls for including a section in which a history of such (dated/timestamped) state changes is maintained, or by absence of that, a paragraph in which the most recent such state change is documented (i.e. what the state is, and when the document reached that state).

[bumblefudge]

There's an open issue on the spec generation tool here that would do this automatically, fwiw. I'll try to bump that.

[JaceHensley]

So that's for the generation date but how we have this repo setup is that the document is regenerated on each PR merge (cause keeping the md file in source is nicer than the html file). But we could just add a timestamp for ratified versions

[csuwildcat]

We will add timestamps one way or another.