Page History

...

Bugfix fixVersion process

Next time When you you create a bugfix to a bugfix to go to Prod, don't assign it to the weekly release (as we have been doing until now), instead:
1. If you already know when this should go to Production (taking into account time of development), create a fix version following the format bugfix/DD_MM_YY, and assign to the bugfix.
2. If you don't know when this will go to production, assign it to "bugfix-placeholder"  fix version (Pankaj is creating this one in fix version (created for all projects). After you know the day of deployment, switch the bugfix fix version the bugfix fix version following point 1.

Calendar of activities

...

• While BugFix deployments to production will occur on Tuesday, Wednesday, and Friday, it's important that:
  • These are tested in UAT first, and therefore deployed to it following the timelines in the calendar.
    • For example, if I want to deploy a bugfix to production on Tuesday, I should make sure that
      • I have submitted it to release manager before the cut-off on Monday 16pm4pm
      • A developer will be able to assist the release manager during possible fixes in the validation to UAT.
      • A Tester will be able to test from 11-12 CET, taking into account that the cut-off to include it in the deployment to production is 12pm CET.
  • On a general basis, there are no deployment to Production of BugFixes neither Mondays or Fridays, due to other deployment activities of Weekly / Monthly happening at the same time. However, if there is urgency, reach out to Release managers through the "Deploys" group to find a solution.
  • Differentiate HotFix from general Bugfix, to clarify that in the event of a HotFix (bugfix with maximum priority), this will be raised through the HotFix channel in google chat and release managers will assist for the soonest deployment of it, and possibly bypassing the calendar below due to business impact.

...