You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This relates to issues like #15711 and #21477, and the suggestion is to add a more prominent notice that the current spec is long out of date or legacy. A more visible notice is needed because the document's presence in the master branch under doc/spec.md suggests (at a glance) that the document would be current, and the version number and date at the top is easy to overlook and is bound to cause confusion (speaking from experience).
The text was updated successfully, but these errors were encountered:
This relates to issues like #15711 and #21477, and the suggestion is to add a more prominent notice that the current spec is long out of date or legacy. A more visible notice is needed because the document's presence in the
master
branch underdoc/spec.md
suggests (at a glance) that the document would be current, and the version number and date at the top is easy to overlook and is bound to cause confusion (speaking from experience).The text was updated successfully, but these errors were encountered: