17.3 Patching

By tonja_ibm

  • 17.3 code branched; develop branch now for 18.1

  • Period: to

    (a) Regression testing (17.3 code, QA5)

    Off of 17.3 branched code
    QA5

  • 17.3 release certified

    Last build at time of cert. is used for updating first set of pods.
  • Period: to

    (b) Fixes to 17.3 before 17.3 goes to any pods

    • create hotfix branch off 17.3 branch
    • merge to 17.3 branch and test on QA5
    • will deploy to production with the first NOW or Expedited Patch after first set of pods updated

  • 17.3 deployed to first set of pods

  • Period: to

    (c) 17.3 fixes first pods

    • IF urgent (and can't wait until after all pods updated)
      • create hotfix branch off of 17.3 branch
      • merge to 17.3 and test in QA5

  • 17.3 deployed to remaining pods

  • 17.3 branch merged to master (and pre-master)

  • Period: to

    (d) 17.3 fixes after all pods updated

    • follow regular patching guidelines (branch from master, merge to pre-master and master, test on QA4 and QA3)