docs: TrueNAS compatibility matrix and the two-stage release process
The matrix is regenerated daily by CI rather than typed once and forgotten — a support table that quietly goes stale is a false promise to someone deciding whether to trust this with their backups.
This commit is contained in:
@@ -5,6 +5,9 @@
|
||||
/hook_status.json
|
||||
/disabled
|
||||
/nested_snapshots_enabled
|
||||
# Written by apply.sh when a module's assumptions no longer fit the installed
|
||||
# middlewared (see tools/compat.py). Evidence for the alert; not source.
|
||||
/incompatible.json
|
||||
|
||||
# Python
|
||||
__pycache__/
|
||||
|
||||
Reference in New Issue
Block a user