TPTP-PMC-20090624

Logistics

Attending: Kathy, Oliver, Chris, Eugene

• Paul, Ernest or having conflicts

Last weeks summary deemed awesome.

4.6.0

4.6.0 ready to be officially posted and released. This will be done shortly.

4.6.0 had a nasty bug at last minute that only affects users that download from the Galileo update site. It relates to launching Eclipse applications. A slight tweak is needed.

• We are currently suggesting folks download from TPTP site instead of update site

4.6.1

4.6.1 head is now opened

• Final 4.6.0 tag exists
• 4.6.1 head opened for checkin
• 4.6.1 builds going

Kathy now has a detailed schedule on the development site Schedule

• There are ~90 bugs targetted to 4.6.1 at the moment
• Sep 25 GA
• RC1 and RC2 are a few weeks before
• We will have development till around August then test passes

There is general happiness that we do not have parallel streams this year (emergency patches, etc)

Kathy noted that Paul has a swag at the bugs to fix for test

• General agreement that it is in the right ballpark for number of bugs that we can fix
• It stresses moving our bugzilla over to point out those that we REALLY plan to fix; not really old bugs that we do not really have plans for
• Paul wanted general approval for his 4.6.1 list
  • The PMC granted Pauls approval and gave him brownie points for being so on top of it.

Bugzilla Cleanup

While Chris was out the PMC had started to discuss closing out (will not fix) bugs older than 2 years that TPTP has no intention of fixing. Submitter can reopen if they want to launch new discussion about fixing.

• This will affect unresolved defects >2yrs old
  • Kathy asks if leads should look at each one individually or can do blanket "will not fix". It would be hard to do one by one since we're talking >500 bugs here.

We had a discussion about whether this is bugs that have been open for more than 2 years or if has been 2 years since the last activity on the bug

• In general there seemed to be agreement that it would be preferable to date it from the last true activity
  • But we need to have an intelligent way to probe for true activity date
  • Problem today is that some bugs have their only activity being moved from one release to the next but no real discussion or anything else.
  • AI Paul needs to find a good query because Kathy notes that almost all the bugs have been touched

We discussed the possibility of adding some sort of status keyword to bugs that are closed during this general cleanup to faciliate later finding things that were closed do to timeout rather than closed with a technical reason to not fix.

• There was general agreement that this was a good idea.
• AI Add to status keyword "4.6 housecleaning" for the houseswept bugs.

4.5.2.1

IBM has their bug ides in mind for milestone 3 ideas (~3 defects)

• Expect list to be brought forward later in week
• IBM hopes to have a build later today. Will ask Intel to be aware of 4.5.2.1 build requests
  • Each time need to trigger a separate build request (manual step is involved)
  • IBM asked if Chris could assist when these bulid requests come in to avoid multi-day turnaround.
  • Chris says that if Yi can provide the instruction (cron job and/or script tweak) needed, that Chris can watch for these requests too.

4.5.2.1 build transitions to IBM

IBM noted that 4.5.2.1 uses old gcc on some platforms while 4.6.x uses newer gcc. This is causing some issues for IBM trying to do builds for 4.5.2.1.

• Would like Intel to continue to build 4.5.2.1s as needed
• Intel would like a timeframe for this being needed no longer
  • IBM only consumer of 4.5.2.1 and it is not a planned release
  • If 4.5.2.1 will continue past the 4.6 spring maintenance it will be imperative that this shift occur.

We had a discussion about how long IBM will need 4.5.2.1 builds

• Generally, this will be until 4.6 consumption picks up...
• Chris mentioned that there is some flexibility thru Spring maintenance with having Yi support occasional builds but that is about the longest possible timeframe.

Misc

AIX Agent controller code is almost ready for review

MACOS contribution CQ request opened (>250 lines)

Next week PMC is cancelled (Canadian holiday)

• POG will be on agenda on the 8th

We discussed a bit about the continuing saga of trying to get Itanium systems to IBM for TPTP builds.

• Currently in some Intel decision processes reviewing IBM counterproposal to the loaner agreement.

Action item to Kathy to send list of names who made significant contributions over last year to Oliver so he can do a thank you.

Oliver mentioned some new positive TPTP press.