TPTP-PMC-20090715

Logistics

Attending: Oliver, Eugene, Chris, Kathy, Ernest

Does anyone need to leave quickly

• No

4.6 discussion

None. It is done

4.6.1 discussion

• Paul says test project is delayed due to TPTP 4.5.2.1 M3 work and vacation schdules.
• Kathy says platform project is slower starting because they are finishing a few things in 4.5.2.1 M3 first
  • ~100 targeted to 4.6.1; most are P2s & P3s.
  • We are on track regarding P1s (all have committed resource)

4.5.2.1

Paul and Jonathan trying to finish up first before moving over to 4.6.1

• Intel China team finishing up a few bugs here too

Kathy mentioned that 4.5.2.1 build transition seems to be complete and asks if both builds can happen together now

• Chris looked at the Intel crontab file and noted that both builds are live.

Misc

4.6.2 target created in bugzilla for stuff committed for Spring maintenance release and 4.6.3 target created in bugzilla for stuff intended for Helios

• Oliver asks if there are any known P1s for this yet
  • No.
• Oliver asks how P1s will these be set up/identified?
  • Probably will wait to formally identify until 4.6.1 rampdown
  • Oliver says that in past we had large number of P1s that we continuously moved from release to release. We have the opportunity of not having any P1s and actually demonstrating removing our P2 backlog.
    • Oliver thinking of making a message to our sponsors to talk about the beauty of cutting away at the bug backlog to drive to zero.

We did a quick rehash of Itanium system shipping hell between Intel and IBM

• Oliver noted that (a) it is funny and (b) it is sad and (c) having the systems at IBM is actually good for Intel to ensure longer life of Itanium support on TPTP.

For POG Eugene notes that the P1 list that he has circulated of POG defects should be able to be done in 4.6.1

• Some of them are being looked at by Intel team now and some by IBM team
• Depending on how things go, we might be able to get to some of the 4.6.2 P2s pulled in also
• In anyone has comments about Eugene's prioritization of POG defects, please send mail to Eugene.
• Oliver mentions that some of POG defects that are most appropriate for Intel to resolve should be targeted sooner rather than later (e.g. 4.6.1, 4.6.2 rather than 4.6.3).