July 25, 2011

Attendees: Eric, Conrad, TomG, TomF, YZ

Action Items

• Someone (Elaine? Conrad?) to indicate on the Chimera web site that 1.5.3 is the last release that will support the PowerPC architecture.
• Scooter will update Trac to latest version (0.12) and possibly convert it from SQLlite to MySQL.
• Discuss components/categories at next meeting.
• Discuss use of keywords in enhancement requests at next meeting.

Items

1. Mac OS X 10.7 (Lion) release
   • We support the last two releases of Apples OS's, so with the release of 10.7, we can discuss what to do about 10.5.
   • Normally, the next Chimera release (1.6) will be the last to support 10.5. However, this means we will be supporting the PowerPC platform for another year.
   • The consensus is that although 10.5 is probably still in widespread use, it is mostly on Intel platforms.
   • We will make 1.5.3 the last Chimera release to support PowerPC. 1.6 will support 10.5, 10.6 and 10.7 on Intel platforms.
2. Tracking enhancement requests
   • TomG, after returning from the last meeting with hundreds of suggestions, proposes that we put enhancement requests into Trac (as opposed to a Wiki page that he maintained).
   • Eric uses his own home-brewed system and does not want to have yet another list.
   • The pros for Trac are that:
     • Everyone can find out what is on the list
     • Comments may be recorded for ideas, even if no code is written
     • It may help in generating release notes
     • Trac tools can help bring more organization (in contrast to wiki page)
   • The cons are that:
     • It is yet another list to maintain
     • The overhead of creating a Trac ticket is greater than adding a line to a document
     • Some ideas are not really ready to be documented in a full ticket
   • The consensus is to try using Trac for enhancement tracking and see whether it works or adds too much overhead.
   • Other Trac issues are:
     • It sends out too much mail. For example, when a ticket owner will get mail when he changes the priority of the ticket, even if he is the one making the change and the only person to get the mail. (It may be easy to set up a mail filter to send such mail to a special folder. This would be done by individual users.)
     • We are not running the latest version of Trac.
     • Do we have the right set of components/categories for tickets?
     • Are there other effective ways to differentiate and group tickets other than categories (e.g., keywords)?
3. Meeting adjourned