Meeting takes place on IRC on the #evergreen channel on Freenode. See the Calendar for specific dates and times.

Held at

• 11:00:00 a.m. Tuesday, June 5, 2012 in America/Los_Angeles
• 2:00:00 p.m. Tuesday, June 5, 2012 in Canada/Eastern
• 18:00:00 Tuesday, June 5, 2012 in UTC

Last meeting:

• 2012-05-23

Links will be added after the MeetBot gives us links:

• Minutes: http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-06-05-14.09.html
• Minutes (text): http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-06-05-14.09.txt
• Meeting Log: http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-06-05-14.09.log.html

1. Determine the taker of minutes: MeetBot
2. Determine meeting leader:
3. Start MeetBot recording: #startmeeting 2012-06-05 - Developer Meeting
4. New business
   1. Sign-offs for branch merges
      Sign-offs for branch merges are not as clear as commit picks, as the sign-off is in a separate commit. See this case for an example. Possible solutions:
      1. Teach those of us who are still green in Git how to easily recognize and trace these cases
      2. Come up with a simple method for signing each commit (e.g. Before merging, rebase, but edit the new commits rather than squash, then amend with your signature)
      3. Decide we don't care, as it's rarely an issue
      4. ???
5. Releases
   1. OpenSRF
      • OpenSRF 2.1.0 has been released (http://list.georgialibraries.org/pipermail/open-ils-dev/2012-June/008320.html)
      • Still need someone to review https://github.com/evergreen-library-system/OpenSRF/pull/2
   2. Evergreen
      • dbs has been plugging away at an Evergreen 2.1.2 release candidate
      • Of the remaining targeted bugs (https://launchpad.net/evergreen/+milestone/2.1.2), only 788629 (Search loses advanced limiters) is confusing
      • Still need to resolve a problem where the acq indexes from upgrade 0691 are being applied in 2.0.11, 2.1.2, and 2.2.0 version upgrade scripts; should we just move them out of the transaction?
6. Announcements?
7. End MeetBot recording: #endmeeting