April 6th, deployed Release Candidate the link to the left describes the process
Created 2 Release Candidates (see graphs on link)
First round: found 59 bugs and 11 regressions
Second round: found 24 bugs
We have a process of resolving any blocker or critical bugs and prioritizing any others
Questions:
Does this testing include all pieces of OpenLMIS (UI, Server, Data)?
Yes and it is manual testing. There are also thousands of automated tests that must pass as part of this process.
Is there scale and performance testing available?
Yes, it's part of the process and is done with data that the Malawi project provided to us. Both the automated and manual performance tests are performed with the target that we will not degrade performance between releases.
Request: Review the performance with an increased number of orderables and see how it works compared to the current system.
This is on our roadmap and we will invest resources in improving performance before the next release.
We would like to work as a group to define the scalability parameters.
We're working to get the teams ramped up. It's exciting to see how three organizations working on the code base can work together in a unified way.
There are risks we identified around creating new Gaps as we go through the process.
Mary Jo will circulate the roadmap
Ashraf provided an update on the Gap project and highlighted the link between Gap and the country implementations that are actively under development. He would like to establish closer coordination to ensure that the Gap doesn't widen.
We would like to enhance collaboration across the country implementations. The teams could prepare a 10 minute update for the Tanzania OpenLMIS management meeting and perform an update to the Product committee to share what's happening in Tanzania.
Question: How can we get better views into the product roadmap across OpenLMIS implementations?
Chris Opit (Unlicensed) is the PM from the JSI team who is based in Zambia. Chris can help give us updates as part of the GAP product committee.
New Requests (NO NEW REQUESTS)
Filter:
Getting issues...
As a committee we will review any new requests that come in. We will then ask follow up question or clarifications. Once the scope is clear, we will prioritize with the current work for development.
Roadmap status = still under discussion
ToDo status = ready for work
Once the feature is slotted for work, we will change the ticket type to a "story"