====== Developer meeting: June 5, 2012 ======

Meeting takes place on [[http://evergreen-ils.org/chat.php|IRC]] on the #evergreen channel on Freenode. See the [[http://evergreen-ils.org/calendar|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: 
  * [[dev:meetings:2012-05-23|2012-05-23]]

===== Logs and minutes =====

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

===== Agenda =====

  - Determine the taker of minutes: MeetBot
  - Determine meeting leader: 
  - Start MeetBot recording: #startmeeting 2012-06-05 - Developer Meeting
  - New business
    - 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 [[https://bugs.launchpad.net/evergreen/+bug/985227/comments/5|this case]] for an example.  Possible solutions:
      - Teach those of us who are still green in Git how to easily recognize and trace these cases
      - 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)
      - Decide we don't care, as it's rarely an issue
      - ???
  - Releases
      - 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
      - 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 [[https://bugs.launchpad.net/bugs/788629|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?
  - Announcements?
  - End MeetBot recording: #endmeeting