Held at:

• 09:00:00 a.m. Tuesday January 11, 2011 in America/Los_Angeles
• 12:00:00 p.m. Tuesday January 11, 2011 in Canada/Eastern
• 04:00:00 p.m. Tuesday January 11, 2011 in UTC

Last meeting: 2011-01-11

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

• IRC logs
• Minutes will be supplied in this document after the meeting finishes

• Please fill out Who's who if you want to be identified more readily in the future

1. Determine the taker of minutes:
2. Determine meeting leader:
3. (10 min) Review Action Items from previous meeting
   1. Dan Scott to continue working on his action items from previous meetings:
      1. Write release notes for OpenSRF 1.6.2
         • STATUS: ???
   2. Mike Rylander to write release notes for Evergreen 1.6.1.5
      • STATUS: ???
   3. Security mailing list - any updates on expected dates
   4. Adoption of the release checklist; Mike RylanderDan Scott to propose a release coordination mailing list on -dev and -general
      • STATUS: Done
   5. People to test schema upgrade for moving custom index definitions around to make room for the pinned-ID indexes added in stock 2.0
      • STATUS: Ben Shum reported success; also worked on Conifer
   6. James Fournie / SITKA to test 2.0RC2 and report back
      • STATUS: ???
   7. Mike Rylander to continue the "DVCS? and if so, which one and when and how?" discussion on the mailing list
      • STATUS: ???
   8. Dan Scott to post a notice to the -dev mailing list to call for ideas and discussion about any other major infrastructure changes that we should consider for post-2.0
      • STATUS: In progress - message posted, response from Jason Etheridge adding another idea
   9. Dan Scott to post a notice to the -dev mailing list to find out if there's support / start planning for an extra day or two at the end of the conference for an in-person dev team meeting / planning session / coding session
      • STATUS: In progress - several positive responses (Bill Erickson, Jason Etheridge, …), need to nail down details (how long and where)
   10. ACTION: Follow up on dbwells' proposed unit/call number schema change (initial reactions suggested a preference to keep it to 2.1, given the late state of 2.0)
4. Evergreen release status:
   1. 1.6.1.x (current release = 1.6.1.6)
      1. Bugs targeted to 1.6.1.7
   2. 2.0
      • Bugs targeted to RC3
   3. Most recently reported bugs
5. (2 min) Schedule next meeting
   • Tuesday, January 18th at 12:00 EST, 9:00 PST