Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Here are the steps we believe are involved in this release process which will take us most or all of this sprint. I'm not sure if you want to create tickets for some of these (like creating RC1) now or not. That's up to you. We will continue using the daily Slack check-ins to we confirm what step of this process we are at.

  •  Fix critical/blocker bugs (we flagged the 2 must-have tickets OLMIS-4383 and OLMIS-4384)
  •  Regression Phase 2
  •  Fix additional critical/blocker bugs (if any identified)
    •  As of April 2nd there are 5 critical bugs that need to be fixed before we can deploy the release candidate Sebastian Brudziński, Nikodem Graczewski (Unlicensed)Joanna Bebak (Deactivated):
      Jira Legacy
      serverSystem JIRA
      columnskey,summary,type,created,priority,status,resolution
      maximumIssues20
      jqlQueryfilter = "20523" and Priority = "Critical"
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      •  
        Jira Legacy
        serverSystem JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId448ba138-230b-3f91-a83e-16e7db1deed1
        keyOLMIS-3708
         (Must finish before we deploy RC1)
      •  Quick wins for anyone not working on bugs: 
        Jira Legacy
        serverSystem JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        maximumIssues20
        jqlQueryfilter = "QuickWin" and Labels = "Phase1bug"
        serverId448ba138-230b-3f91-a83e-16e7db1deed1
  •  Create RC1 & make sure it is announced to the community
  •  Complete testing RC1 
  •  Fix critical/blocker bugs (only if any more identified – hopefully not) and re-issue RC2, RC3 and repeat....
  •  Publish official 3.3.0 release

Team ILL

  •  New Ticket: Performance testing, both automated and manual, for new features - Josh will write
  •  New Ticket: Take snapshot to preserve UAT2 stock demo data - Chongsun
  •  New Ticket: Spike on how to preserve/leverage the stock demo data - Chongsun
  • Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4479
  •  
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4492
  •  
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4493
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4460
     
  •  Finalize agenda for April 11-13 Gap Estimation Meetings