Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-5809 Release Ozone 1.2.0
  3. HDDS-6016

Update ozone upgrade acceptance tests to use 1.2.0

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      Now that 1.2.0 is released, we need to test the following paths:

      1.1.0 -> 1.3.0 upgrade/downgrade

      1.2.0 -> 1.3.0 upgrade/downgrade

      This matrix would take a significant amount of CI time and will only get larger with each release, so I suggest we only enable 1.2.0 <-> 1.3.0 testing on master, and update the release guide to specify how to test the full matrix before cutting a release branch.

      Attachments

        Issue Links

          Activity

            People

              erose Ethan Rose
              erose Ethan Rose
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: