Below is a summary of the QA 2.1.2 Post-Release Review conference call on 4/18/2006. Feel free to add additional items or modify any ITEM/ACTION shown below.information to items.
Comments in blue were added after the meeting
Attendees: Ari Consul, Megan May, Peter Knoop, and Seth Theriault.
# | Review Item | Discussion Points | 1|
|---|---|---|---|
Estimatation of QA hours | Considering the work done and the length of the cycle compared to 2.1.1, it's possibly near 600. This is purely a guess as many people haven't responded with this information | 2 | |
Deployment Scripts need better testingFind resources to do this. QA servers testing | More attention needs to be given to this. Building a clean install and a final test of the upgrade path from different releases (ie 2.1 to 2.1.2 or 2.1.1. to 2.1.2) need to be done. Fisrt and foremost, we need to find resources to do this. Megan will send out a request for resources via the newsletter. | ||
3 | There is a | ||
3 | Getting adqaquet . Scripts that populate sites with data are also an option if data retension isn't possible. | ||
Adequate test coverage | Automation of functional tests is becoming more and more critical. Ari expressed interest in this and JMeter was recommended. Need to identify more resources that can get involved in this. One way to start this would be to identify components where automation is critical - for instance, T/Q or GB. Another is to script tests for any bugs being verified. * Megan speculated about performing In this process we'll start to get more and more coverage. would keep up from being in a "scramble" mode in the end and allow for more time to review the general functionality just prior to the release. There are two issues to think about 1) Interpretation by creator 2) Interpretation by developer. Testing closer to the time work is actually be done would minimize any gaps between the two. This would require expanding the nightly servers. At one point it was thought that the QA servers would revert to a nightly build and then slow when the community went into the release phase. The timing of the maintenance branches hasn't alloted much time for this | ||
QA server Network | Still looking toward expanding this pool. It was suggested that when Rutgers have the available resources, they are interested. U of Capetown is also a good candidate. | ||
Samigo | There have been a lot of changes. Some institutions are having trouble updating Samigo for 2.1.2. This tool is a great candidate for functional scripts | ||
Items included in release | Some discussion was centered around understanding how the community requirements are |