Skip to content

[docs] Make system requirement bumps clearer in supported versions #1415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mickhawkins
Copy link
Collaborator

The language previously used to describe when a system requirement version was bumped was really confusing: "increase since" mean "has increased since", which is confusing when you are looking at notes for a version beyond where it was bumped, because it sounds like the version listed is when it changed, when i twas actually changed in the release after that. For example the 4.5 notes had "increased since Moodle 4.1" which actually meant something increased in 4.2...

I have updated all of the currently supported versions and the documented future versions (4.1, 4.4, 4.5, 5.0, 5.1, 5.2, 5.3) so that they say "increased in this Moodle version" in the initial version where a bump has occurred, and in subsequent versions it now says "last increased in Moodle X.Y" and lists the specific version where the change took place.

Copy link

netlify bot commented Aug 11, 2025

Deploy Preview for moodledevdocs ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit ebb98be
🔍 Latest deploy log https://app.netlify.com/projects/moodledevdocs/deploys/689a29f5260e840008e265e1
😎 Deploy Preview https://deploy-preview-1415--moodledevdocs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant