Tasks for 3.4 code freeze

Owned by Sebastian Brudziński
Last updated: Oct 30, 2020 by Klaudia Pałkowska (Deactivated)

The code freeze period is dedicated to regression and performance testing, as well as fixing critical and blocker bugs. However, usually not everyone in the team is involved in it (eg. because there's only last test case remaining or there's only last bug being worked on).

We prepare this list of tasks, that can be worked on if the developers have spare time during this period. Of course testing and fixing bugs is ALWAYS a priority. Tasks from this list can only be worked on if a developer cannot help with testing or fixing bugs anymore.


Tasks:

  • OLMIS-5054 - Getting issue details... STATUS
  • OLMIS-4570 - Getting issue details... STATUS
  • OLMIS-5146 - Getting issue details... STATUS
  • OLMIS-4674 - Getting issue details... STATUS
  • OLMIS-3781 - Getting issue details... STATUS
  • OLMIS-5135 - Getting issue details... STATUS
  • Review screens that slowed down after merging perf data into demo data and create necessary tickets for improvements
  • Documentation review and fixes
  • OLMIS-5177 - Getting issue details... STATUS


OpenLMIS: the global initiative for powerful LMIS software