Page Comparison

...

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
    server System JIRA columns key,summary,type,created,priority,status,resolution maximumIssues 20 jqlQuery filter = "20523" and Priority = "Critical" serverId 448ba138-230b-3f91-a83e-16e7db1deed1

    •  

      Jira Legacy
      server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3708

       (Must finish before we deploy RC1)
    •  Quick wins for anyone not working on bugs: 

      Jira Legacy
      server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter = "QuickWin" and Labels = "Phase1bug" serverId 448ba138-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

...