Add documentation for Wasmtime's LTS releases #10481
Conversation
With Wasmtime's [LTS releases](bytecodealliance/rfcs#42) this commit documents the various process changes and updates to our release process. Additionally some improvements are made to the release documentation with respect to showing current versions.
docs/stability-release.md
Outdated
|
|
||
| In more visual form this is a gantt chart of the current release trains: | ||
|
|
||
| <!-- JS edits in the chart --> |
There was a problem hiding this comment.
An example of what this generates:
There was a problem hiding this comment.
That is some impressive DOM-tree-editing hackery! The end result looks great.
At the risk of complexifying a little bit: could we add a placeholder ("view this document as HTML in a browser with JavaScript enabled to see contents" or somesuch) so that if the Markdown is processed in some other way -- for example, converted to print pdf by pandoc -- or viewed by a user with JS disabled, they aren't confused?
There was a problem hiding this comment.
FYI, you should be able to use a <noscript> tag for this.
There was a problem hiding this comment.
Sounds good yeah, added some <noscript> tags to indicate that it's empty without JS
|
I originally wanted to document the property of "when backporting must update all branches" and got a bit carried away and went ahead and documented the LTS updates. |
fitzgen
left a comment
There was a problem hiding this comment.
Can you put version numbers in the JS's file paths so that if we ever want/need to upgrade, things are a little easier?
With Wasmtime's LTS
releases this commit documents the various process changes and updates to our release process. Additionally some improvements are made to the release documentation with respect to showing current versions.