This was a useful exercise

‌

1. Version numbering - we should be doing major/minor/hotfix

   1. We did:

      1. Main release: v5.48
      2. Hotfix 1: v5.49
      3. Hotfix 2: v5.50
         

   2. We should have used revision numbers for this, e.g.

      1. Main release: v5.48
      2. Hotfix 1: v5.48.1
      3. Hotfix 2: v5.48.2
         

   3. Potential Action: Document how to do version numbering and agree on it

2. Previous Hotfix versioning was unclear (we use tagging)

   1. Problem: When the hotfix is merged to our master branch, the release tag for the hotfix is no longer visible in the master branch
      Solution: In DevOps look in the Tags area to see the latest release tag
   2. Potential Action: Document the hotfix process for future reference
      

3. Testing: The need for a regression plan became pretty obvious - and we dont have one

   1. Potential Action: Create regression plan or at least document how a non-tester would run a smoke test

      1. testing team needs to own this
      2. partial regression plans
      3. testing automation
         

4. Testing of production post go live

   1. We had a few problems

      1. Login wasn't working
      2. ‘No Cover’ payment wasn't working

   2. Potential Actions:

      1. Have SMOKE TESTS OF SOME KIND
      2. Create basic scripts to check that stuff is coming in (PowerBI?)
         

5. There was some discussion on when we should do releases

   1. Potential Actions:

      1. No Friday releases - To ensure that any post release issues don’t build up over the weekend
      2. No Monday releases - To minimise impact on the business, if there is a backlog of work from the weekend (is this required?)
      3. Do releases first thing in the morning, rather than last thing in the day - To give time to do post release testing in working hours and ensure that things are running ok before the end of the working day