Amend README.txt to reflect actual state. #601
Conversation
| branches. Use the latest STABLE branch for development or installation. | ||
| The current stable branch is MOODLE_400_STABLE, and supports Moodle 4.0 and up. | ||
| The current stable branch is MOODLE_404_STABLE, and supports Moodle 4.4 and up. |
There was a problem hiding this comment.
Not completely true. The current stable branch (aside from naming) is MOODLE_401_STABLE. It supports Moodle 4.1 through 4.4.
MOODLE_404_STABLE is the current development branch, for the next stable release, and supports Moodle 4.4 and targeting 4.5.
|
My point being: the current one (both MOODLE_401_STABLE as well as in MOODLE_400_STABLE branch, maybe the one in MOODLE_404_STABLE, too) ought to be amended. |
lucaboesch
force-pushed
the
readmechanges
branch
5 times, most recently
from
c71551d to
16c5506
Compare
|
I think it is accurate now. |
lucaboesch
force-pushed
the
readmechanges
branch
from
16c5506 to
24a96b0
Compare
|
Rebased to MOODLE_404_STABLE branch |
|
What's the change to "tests/custom_completion_test" for? |
|
_provider() classes have to be static now, @mchurchward |
lucaboesch
force-pushed
the
readmechanges
branch
from
24a96b0 to
24daa6e
Compare
|
Rebased to MOODLE_404_STABLE branch |
There was a problem hiding this comment.
Thanks for the changes. But...
Can you leave this PR to be just for the README?
Create a separate issue for the tests - I'm guessing that is something for 4.6? Since my CI isn't failing on that prior to that.
Don't include your CI changes yet. I will create a new development branch after this release to include main. Otherwise, we run the risk of the release branch failing.
No description provided.