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

Bump backup internal version and release information for the 5.0 branch

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • 5.0
    • 5.0
    • Backup
    • MOODLE_500_STABLE
    • MOODLE_500_STABLE
    • MDL-83373-main
    • Hide

      Manual (main branch):

      1. Perform a 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>2024100700</backup_version>
        		 
        <backup_release>5.0</backup_release>

      Automatic:

      1. The CI servers' version checker job should pass perfectly for main and the just created stable branch.
      Show
      Manual (main branch): Perform a 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>2024100700</backup_version> <backup_release>5.0</backup_release> Automatic: The CI servers' version checker job should pass perfectly for main and the just created stable branch.

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

      Since Moodle 2.4, we have been checking version and release with the CI versions checker, so this is a task that we should always perform immediately after a major release (hence, it 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)

      As a side note, this is one of the allowed differences between the just-created branch and the master branch during the on-sync period.

        1. MDL-83373.png
          MDL-83373.png
          289 kB

            jpataleta Jun Pataleta
            jpataleta Jun Pataleta
            Nobody Nobody (Inactive)
            Huong Nguyen Huong Nguyen
            Ron Carl Alfon Yu Ron Carl Alfon Yu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 35 minutes
                35m

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