Author: Karl Schopmeyer
Modification Date:
4 Feb 2010
Karl
Greg
Sahana
Venkat
Marek
See the web page
1. Minutes
2. Actions
3. Build Status
Nightly Build Status
Noted that zos build failed with issue in cimcli tests. Marek will file bugs. karl noted that he is testing on vista now and will start to regularly file reports.
4. Bugs
See notes below on 2.10 release
6. PEPs
See notes below on 2.10 release
7. Any Other Business
Review of Status of 2.10 release
1. Bugs for 2.10 Release
Reviewed the outstanding blocker bugs.There are at least 7 real blocker bugs outstanding. We cannot set source freeze tag today because of this list of bugs. We agreed that the primary priority today is working off these blocker bugs.
8652 - defined for 2.9.1 - Status unknowy
8659 - Status unknown
8692 - valgrind error in anonymousPipe::writeBuffer - Issue since apparently only Sahana can recreate it today
8700- HP Cadvise error - Approved and being checked in
8708 - Nightly build failure in JMPI
8713 - Intermittent Seg fault across server. Being investigated
8719 - Vista nightly test fails in CMPI providers - Reported, no solution
The major bug for this release is probably 8713, an intermitent Seg Fault under load. This occurs in many different parts of the server but is probably due to a single cause. However having real problems finding it becuase use of any of the normal tools (valgrind) causes the problem to go away. Marek asked if anybody has any ideas for ways to track down this bug. Karl suggested that Mike B. had written some new/delete test code several versions of pegasus in the past and Karl would track this down to see if it would help.
Ventkat asked "What do we mean by blocker and depends on?" with a couple of examples it appears that we do not have a common understanding of what setting these fields means. Does it set the order of checkin, the order of fixing, etc. Action karl. Try to define more explicitly what we mean by depends and blocker in our bugs. Sahana noted that the bugzilla documentation might be all we need.
2. PEPs for 2.10 Release
1. All PEPs that have been appproved for this release have been moved.
2. Marek commented that he has one more update for PEPs 351-354 noting that two of them are going to go away completely since they are just pointers to the web site. Ventkat note that he has more comments but needs the close date for the PEPs updated so he can make his comments today.
3. Karl will update 355 (release notes) and put it up for ballot.
Other Issues discussed
Pegasus 2.8.2 - Note that the release has been complete for some time but the files were never put up nor the release email sent.
Pegasus 2.8.3 - Clarify status of 2.8.3. Today there is no web page for this version. The question was raised as to whether we are going to do 2.8.3. Nobody has any objection to doing it. The question today is who.
Sahana noted no announcement email on items going into the Arch Team agenda. Action Karl. The problem was that the fields Send an alert and Send an alert when comments received were not set when the agenda was created.
.