Uploaded image for project: 'Moodle Community Sites'
  1. Moodle Community Sites
  2. MDLSITE-8072

Create a MOODLE_STABLE branch

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Low Low
    • git.moodle.org
    • None

      Here are our published branches:

      https://github.com/moodle/moodle/branches

      • `MOODLE_500_STABLE`
      • `MOODLE_401_STABLE`
      • ...

      Please add `MOODLE_STABLE` to this list. `MOODLE_STABLE` will track the latest `MOODLE_XXX_STABLE` branch.

      1. Why?

      The community of people that do Moodle software is MUCH LARGER than you, dear maintainers, of the Moodle core project.

      There is a serious problem of adjunct Moodle software—that software is targeting old Moodle versions.

      My installation is running 404. And I can't upgrade to 405 because most plugins I need don't support it yet... let alone 500.

      EVEN THE MOODLE TEAM"S OFFICIALS PROJECTS [ARE STUCK ON 2-MAJOR-VERSIONS AGO COMPATIBILITY](https://github.com/moodlehq/moodle-docker/blob/25102ac86e05e1695010e4ee29b1c4fd3be588eb/README.md?plain=1#L30).

      Asking people to accept a one-line PR [is too much of a hassle](https://github.com/moodlehq/moodle-docker/pull/305).

      And the solution is simple: don't require people to do ANYTHING when upgrades happen, just support a `MOODLE_STABLE` branch, and CI tools can automatially test and validate against it as new versions release.

            Unassigned Unassigned
            fulldecent William Entriken
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.