Release Activities

• Testing for RC3 was completed by Sam, Nick, and Josh (see RC3 Final Regression Testing cycle). RC3 is ready to be released on Thursday.
• On Thursday Team Parrot will:
  
  • release all components (Services, UI, etc)  EXCEPT openlmis-ref-distro.  DO NOT RELEASE openlmis-ref-distro 
  • As part of releasing each component, bump each service version to the next version
  • Update test.openlmis.org and contract tests to be deploying and testing the next SNAPSHOT versions (not the old RC or release)
  • Remember, do not change ref-distro (we, Team ILL, haven't finished the release notes)
  • Provide release status in #general

After 3.2.1 Release (only start these after components are released)

Goal: CCE final touches, reverted bugs, minor admin fixes, stock management Tech Debt.

CCE

• Q -  OLMIS-3334 - Getting issue details... STATUS
• OLMIS-3243 - Getting issue details... STATUS
• OLMIS-3347 - Getting issue details... STATUS
• C -  OLMIS-3333 - Getting issue details... STATUS
• OLMIS-3239 - Getting issue details... STATUS
• OLMIS-3238 - Getting issue details... STATUS

Performance

OLMIS-3493 - Getting issue details... STATUS  (Team Parrot - this is an Epic, open it up and take these in priority order (OLMIS-3403 first and blocks others))

UI

• Q -  OLMIS-2656 - Getting issue details... STATUS (MUST)
  
  

Reference Data UI / Administration Screens

• OLMIS-2285 - Getting issue details... STATUS
• OLMIS-3306 - Getting issue details... STATUS  
• OLMIS-2727 - Getting issue details... STATUS

Stock Management

• OLMIS-3087 - Getting issue details... STATUS  Q in ticket
• OLMIS-2419 - Getting issue details... STATUS

• OLMIS-3167 - Getting issue details... STATUS (Nikodem Graczewski (Unlicensed): we want you to re-start the discussion on the dev forum, ping Josh Zamor (Deactivated) as needed, don't start coding anything yet for this)
  
  • had been in discussion, listed here to re-start it after v3.2.1 drops

Platform

• OLMIS-1652 - Getting issue details... STATUS

Team ILL

Open Question: how do we 'see' into the reporting work and what dependencies exist? Do we know of dependencies?

• OLMIS-3423 - Getting issue details... STATUS  (Ben doing for Malawi implementation)
• OLMIS-3585 - Getting issue details... STATUS  (Josh has an email thread with Brandon and Elias)
• OLMIS-3584 - Getting issue details... STATUS
• OLMIS-2884 - Getting issue details... STATUS
• OLMIS-3254 - Getting issue details... STATUS  (Chongsun)
• OLMIS-3501 - Getting issue details... STATUS  (Chongsun)
• OLMIS-3583 - Getting issue details... STATUS  (Rachel is writing ticket)
• OLMIS-3587 - Getting issue details... STATUS  (Sam doing Product Committee research and proposal)
• OLMIS-3588 - Getting issue details... STATUS  (MJ and Brandon) → connected to Reporting because it may need mock data
• RTM
  • OLMIS-3387 - Getting issue details... STATUS  (first one in epic OLMIS-3385)
  • OLMIS-3589 - Getting issue details... STATUS  (Sam, Nick, Josh so the implementation could happen next sprint)
• OLMIS-3590 - Getting issue details... STATUS  (Rachel leading ticket writing – Definition of Done is actionable tickets)
• OLMIS-3591 - Getting issue details... STATUS  (Josh and Sam)
• Reporting (Ona, MJ, Josh)
• OLMIS-3533 - Getting issue details... STATUS  (Team ILL first needs to identify Desired Behavior)
• OLMIS-3505 - Getting issue details... STATUS  (Related to OLMIS-3533) (Team ILL needs to review Desired Behavior for stock dates on emergency requisitions here)
• OLMIS-3545 - Getting issue details... STATUS
• OLMIS-3463 - Getting issue details... STATUS
• OLMIS-3316 - Getting issue details... STATUS
• OLMIS-3196 - Getting issue details... STATUS
• Nick Reid (Deactivated): FYI, UI stuff happening this sprint is Fulfillment and Making An Order stuff (see above).
• WAIT------------------------------------------
  • Mobile Implementation
  • Mobile Strategy
  • Implementor Toolkit (Tenly involved after Thanksgiving)