plugin compatibility matrix
compatibility from Plugins pro Moodle-Version and Release-Fenster steuern.
Quick overview
This page describes the working standard for plugin compatibility matrix – with a focus on concrete decisions rather than general guidance.
The main focus here is approval neuer plugins and upgrade-blocker through plugins so that teams apply the same standard.
The standard only becomes traceable through linked evidence such as plugin-liste / matrix and through documented edge cases/exceptions.
When this page helps
Typical situations in which this page adds value as a working document, and where another document is more appropriate.
Typical use cases
- when for plugin compatibility matrix technical standards about eingesetzte plugins incl. version and zweck must be documented in a binding way
- when team handovers or temporary cover the same process for approval neuer plugins should be able to execute safely
- when incidents or Changes show that evidence such as plugin-liste / matrix are still missing
- when configuration or operational deviations (e.g. plugin becomes produktiv activeiert without staging-test) occur repeatedly
Less suitable when
- when plugin compatibility matrix only about a one-off individual case without need for standardization applies
- when a detailed project ticket or a technical step-by-step guide is the better fit
Recommended process
A pragmatic sequence that works in practice, from scope to review.
- capture the current state and scope for plugin compatibility matrix capture, including eingesetzte plugins incl. version and zweck and critical dependencies.
- define the target state and standards; key decisions include approval neuer plugins.
- test changes in a controlled way (Staging, Testsystem or Checklist) and Ergebnis document.
- implement in production, run follow-up checks, and plugin-liste / matrix + staging-testergebnisse link.
- Monitoring/Reviews auswerten and recurring Befunde such as „Plugin becomes produktiv activeiert without Staging-Test“ in the standard einarbeiten.
Decision rules
plugin compatibility matrix is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.
scope & Wirkung
For plugin compatibility matrix first define the scope clearly: eingesetzte Plugins incl. Version and Zweck.
approvalregel
decisions about approval neuer plugins and upgrade-blocker through plugins not implizit lassen, sondern roles and approvals explicitly benennen.
Exceptions cleanly halten
Allow exceptions only if they do not dilute the standard; especially relevant here are compatibility to the moodle-version.
Verifiablekeit
Verifiable is the rule only, when plugin-liste / matrix and staging-testergebnisse cleanly verlinkt are.
What should be documented
Here only the spezifischen Inhalte about plugin compatibility matrix maintain; general documentation rules remain in the centraln guideline. Central guideline.
The page is good when a substitute can apply or review the standard without first collecting tribal knowledge.
scope
terms, scope and boundaries about plugin compatibility matrix specify in concrete terms, including eingesetzte plugins incl. version and zweck.
Concrete Parameter/rules
Den standard so record, dass approval neuer plugins and deactiveierung/abkündigung eindeutig entschieden are.
evidence
Name and link evidence directly: Plugin-list / Matrix, Staging-Testergebnisse, approvalprotokoll.
Versionierung
Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with compatibility to the moodle-version.
Common pitfalls
This section captures real-world pitfalls from plugin compatibility matrix; general guidance belongs in the central guideline. Central guideline.
- scope driftet: Plugin becomes produktiv activeiert without Staging-Test.
- the rule is too abstract: compatibility to the target version is unclear.
- evidence is missing: Owner for a Plugin is missing.
- the exception gets out of control: Release bündelt about viele ungetestete changes.
Moodle reference (official docs 5.1)
Kurze Verweise on the offizielle Moodle documentation for plugin compatibility matrix. So remains this Page AFANDI-spezifisch and vermeidet doppelte Grundlagen.
Official references
Documentation focus
- Kompatibilitätsmatrix with Moodle-Version, Plugin-Version and Teststatus maintain.
- UI path, role and test case record explicitly (not only the desired target state).
- Mark deviations from AFANDI standards separatelyely so that updates remain easier to review.
Review & maintenance
Check this Page gegen reale processes about plugin compatibility matrix – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.
- Ist the Plugin-list fully?
- Passen Plugins to the Moodle-Version?
- Gibt it ungenutzte or veraltete Plugins?
- War the scope realistisch?
Review focus for „plugin compatibility matrix“: Plugins; check especially eingesetzte plugins incl. version and zweck.
Useful metrics
A few metrics are enough – what matters is that they trigger decisions or improvements.
For „plugin compatibility matrix“ Kennzahlen directly an approval neuer plugins and the most frequent Praxisrisiken koppeln.
Plugin-Aktualität
Anteil Plugins on freigegebenem Stand
Interval: monthly
Kompatibilitäts-Blocker
Anzahl Plugins, the Upgrades blockieren
Interval: monthly
Staging-Testquote
Anteil Plugin-changes with Staging-evidence
Interval: monthly
Next steps
Add jetzt the concrete Entscheidung about approval neuer plugins incl. Verantwortlichen, Datum and Verweis on plugin-liste / matrix.
On „plugin compatibility matrix“ make especially clear as the next step: which eingesetzte plugins incl. version and zweck apply in the standard case and which exceptions are time-limited.