Table of Contents

Developer meeting: July 5, 2011

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

Held at

Last meeting: 2011-06-21

Logs and minutes

Prior to the meeting

Agenda

  1. Determine the taker of minutes: ?
  2. Determine meeting leader: ?
  3. Review action items
    1. gmcharlt to write up some ideas on improving git use and releases
      • STATUS: ?
    2. gmcharlt working on: LP 740320 and LP 520175 ( related work )
      • STATUS: ?
    3. dbs to poke jamesrf via email about: LP 780665 (spine labels assume LC)
      • STATUS: jamesrf uploaded a patch as requested; dbs still needs to test and apply it (hopefully in time for 2.0.8)
    4. gmcharlt to review LP 787162, LP 758945
      • STATUS: ?
    5. gmcharlt suggested that we have a pullrequests review meeting opposite to dev meetings (to be added to mailing list for discussion)
      • STATUS: ?
    6. phasefx will take an action for making a custom git command to spit out the invocation for checking out a specific branch from a specific repository
      • STATUS:
        #!/bin/sh
        # Have this be something like /usr/local/bin/git-url and invoke as "git url" while sitting in the checked out branch.
        # Not perfect.  For example, you may have the repo URL be something like git@git.evergreen-ils.org while others may
        # need git://git.evergreen-ils.org/, or vice versa
        giturlbranch=`git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/\1/'`
        giturlrepo=`git config -l | grep ${giturlbranch}.remote | cut -f2 -d=`
        giturlrepourl=`git config -l | grep ${giturlrepo}.url | cut -f2 -d=`
        echo git add remote $giturlrepo $giturlrepourl
        echo git co -b $giturlbranch $giturlrepo/$giturlbranch
  4. Conifer held TT OPAC development days @ University of Windsor, June 27-29th. See notes here.

Patch review queue

We don't want to let submitted patches rot, here's a list of bugs with attached patches

Also a list of bugs with "pullrequest" tags that may also contain patches

Evergreen release statuses

  1. Evergreen release status:
    1. 1.6.1.x (current release = 1.6.1.8)
      1. Bugs targeted to 1.6.1.9
    2. 2.0.x (current release = 2.0.7)
      1. Bugs targeted to 2.0.8
    3. 2.1.x (current release = 2.1-rc1)
      1. Status check

Next meeting