Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-79625

Bump backup internal version and release information for 4.4 branch

    XMLWordPrintable

Details

    • MOODLE_404_STABLE
    • MOODLE_404_STABLE
    • MDL-79625-master
    • Hide

      Manual (master branch):

      1. Perform 1 backup of any course.
      2. Download the resulting .mbz file.
      3. Rename the file to add the .tgz suffix
      4. Uncompress the file

        tar -zxf path/to/moodle_backup.mbz.tgz
        

      5. Look to the "moodle_backup.xml" file"
      6. TEST: Verify these contents are in the <information> tag:

        <backup_version>2023100900</backup_version>
        <backup_release>4.4</backup_release>
        

      Automatic:

      1. The version checker job in the CI servers should pass perfectly both for master and the just created stable branch.
      Show
      Manual (master branch): Perform 1 backup of any course. Download the resulting .mbz file. Rename the file to add the .tgz suffix Uncompress the file tar -zxf path/to/moodle_backup.mbz.tgz Look to the "moodle_backup.xml" file" TEST: Verify these contents are in the <information> tag: <backup_version>2023100900</backup_version> <backup_release>4.4</backup_release> Automatic: The version checker job in the CI servers should pass perfectly both for master and the just created stable branch.
    • 1
    • Team Hedgehog 2023 Sprint 3.3

    Description

      We used to update the internal backup version and release during majors. While it's not used along the process, that information is included on each backup and has helped in the past to detect inconsistencies caused by codebase partially updated and other problems.

      Since Moodle 2.4 we are checking version & release with the CI versions checker so this is a task that we should always perform immediately after a major release (hence has been included in the Release process).

      Summary:

      1) Both in the new stable branch and in the master (file backup/backup.class.php):

      • VERSION must match the main $version (10 digits).
      • RELEASE must match the main $release (X.Y format).
        (provide all the needed changes to achieve this)

      Side note: this is one of the allowed differences between the just-created branch and the master branch over the on-sync period.

      Attachments

        Issue Links

          Activity

            People

              jpataleta Jun Pataleta
              jpataleta Jun Pataleta
              Huong Nguyen Huong Nguyen
              Sara Arjona (@sarjona) Sara Arjona (@sarjona)
              Ron Carl Alfon Yu Ron Carl Alfon Yu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour, 22 minutes
                  1h 22m

                  Clockify

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