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

Bump backup internal version and release information for 3.8 branch

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.8
    • Fix Version/s: 3.8
    • Component/s: Backup
    • Labels:
      None
    • Testing Instructions:
      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>2019052000</backup_version>
        <backup_release>3.8</backup_release>
        

      Automatic:

      1. The version checker job in the CI servers 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>2019052000</backup_version> <backup_release>3.8</backup_release> Automatic: The version checker job in the CI servers pass perfectly both for master and the just created stable branch.
    • Affected Branches:
      MOODLE_38_STABLE
    • Fixed Branches:
      MOODLE_38_STABLE
    • Pull from Repository:
    • Pull Master Branch:

      Description

      We use to update the internal backup version and release on 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 perform always immediately after a major release (hence has been included in https://docs.moodle.org/dev/Release_process#Packaging).

      Summary:

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

      • VERSION must match main $version (8 digits).
      • RELEASE must match 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 master over the on-sync period.

        Attachments

        1. MDL-65643.jpg
          80 kB
          Anna Carissa Sadia

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  11/Nov/19

                  Time Tracking

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