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

Bump all versions, requires and dependencies near major release in master

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 2.3
    • 2.3
    • General
    • MOODLE_23_STABLE
    • MOODLE_23_STABLE
    • Hide

      1) TEST: Visually verify that all the changes in the patch point to the correct version (2012061700) and nothing else is changed.

      2) Upgrade from any previous 2.2.x or 2.3dev version.

      3) TEST: In the plugins screen ALL the plugins are show "to upgrade".

      4) TEST: All the target versions and all the dependencies show the "2012061700" version along the whole page.

      5) TEST: Run upgrade. Ends without error.

      6) TEST: To integrators, this is not available yet in the hq server my in my one. Verify the "Versions checker and setter" job in the integration server ends without error, that everything points to "2012061700" and that the report does not include any "ERROR". You can run it from http://stronk7.doesntexist.com/view/various/ and then, look to the generated "versions_check_set.txt in the workspace.

      Show
      1) TEST: Visually verify that all the changes in the patch point to the correct version (2012061700) and nothing else is changed. 2) Upgrade from any previous 2.2.x or 2.3dev version. 3) TEST: In the plugins screen ALL the plugins are show "to upgrade". 4) TEST: All the target versions and all the dependencies show the "2012061700" version along the whole page. 5) TEST: Run upgrade. Ends without error. 6) TEST: To integrators, this is not available yet in the hq server my in my one. Verify the "Versions checker and setter" job in the integration server ends without error, that everything points to "2012061700" and that the report does not include any "ERROR". You can run it from http://stronk7.doesntexist.com/view/various/ and then, look to the generated "versions_check_set.txt in the workspace.

      This task corresponds to point #3 of:

      http://docs.moodle.org/dev/Major_release_process#One_week_before

      And it's achieved in a semi-automated way with the "versions_check_set.sh" script available @ https://github.com/stronk7/moodle/tree/ci/local/ci.

      1) In a working master site with the ci local plugin installed.
      2) Define and export all the env variables required by the script.
      3) Run it. With errors, they will be reported and fixing will be necessary.
      4) Without errors, all the versions, requires and dependencies will be bump.
      5) Commit and push

      Note the checker is also run periodically by the ci server and also as part of the "remote_branch_checker", so normally all the version.php files should be under control.

      (This issue will be cloned for each major release).

      Ciao

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

              Created:
              Updated:
              Resolved:

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