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

Bump backup internal version and release information for 3.4 branch

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • 3.4
    • 3.4
    • Backup
    • MOODLE_34_STABLE
    • MOODLE_34_STABLE
    • Hide

      Manual:
      1) Perform 1 backup of any course.

      2) Download the resulting .mbz file.

      3) Uncompress it (may be in .zip or .tgz format).

      5) Look to the "moodle_backup.xml" file"

      6) TEST: Verify these contents are in the <information> tag:

      <backup_version>YYYYMMDD00</backup_version>
      		 
      <backup_release>X.Y</backup_release>

      (and they match the values in the main version.php file)

      Automatic:
      1) The version checker job in the CI servers pass perfectly both for the new stable branch and for master.

      Show
      Manual: 1) Perform 1 backup of any course. 2) Download the resulting .mbz file. 3) Uncompress it (may be in .zip or .tgz format). 5) Look to the "moodle_backup.xml" file" 6) TEST: Verify these contents are in the <information> tag: <backup_version>YYYYMMDD00</backup_version> <backup_release>X.Y</backup_release> (and they match the values in the main version.php file) Automatic: 1) The version checker job in the CI servers pass perfectly both for the new stable branch and for master.

      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):

      • Update VERSION to match $version (8 digits).
      • Update RELEASE to match $release (X.Y format).

            stronk7 Eloy Lafuente (stronk7)
            stronk7 Eloy Lafuente (stronk7)
            Dan Poltawski Dan Poltawski
            John Okely John Okely
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

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