I’m curious what the use case is. I often encounter this issue from the perspective of wanting to know what a compiler supports (ie is it 2003 compliant, 2008 compliant, …) and when working with older code I want to know what the vintage of the code is to have a better idea of what is likely to need looked at (which compiler switches that enforce a standard are often useful for), but much less rarely am I looking at when a feature was introduced. Knowing what platform a code ran on is often very important, as some features have a complex history, having emerged from various compiler-specific extensions, but being subtly different in the standard than in some of the pre-standard variants and so on. Is there a use case for just knowing when something was introduced independent of such issues other than general curiosity?
Knowing really old code with something like “array=scalar” was only setting element one of the array, not the entire array (pre-standard 66 Fortran in most cases) and other such things can be critical to getting an old code running, and being really suspicious of arrays being dimensioned to a size of one that are procedure parameters and so on can be critical, but I am wondering if I am missing another aspect of knowing Fortran history.
More specifically, it is often the use of non-standard features that I need to know the history of,
as Fortran is nearly obsessively upward compatible if code was standard-conforming in the first place.