Developer meeting: March 15, 2011
Held at
09:00:00 a.m. Tuesday March 15, 2011 in America/Los_Angeles
12:00:00 p.m. Tuesday March 15, 2011 in Canada/Eastern
04:00:00 p.m. Tuesday March 15, 2011 in UTC
Last meeting: 2011-03-01
Agenda
Meeting takes place on IRC on the #evergreen channel on Freenode. See the Calendar for specific dates and times.
Logs and minutes
Prior to the meeting
Please fill out
Who's who if you want to be identified more readily in the future
Agenda
Determine the taker of minutes: Ben Shum
Determine meeting leader: Anoop Atre
Review action items:
Test OpenSRF 2.0.0 with Evergreen 2.0.2 for stability and potential adoption (fix for Unicode patron name problems) : Ben Shum (tbd), Jason Etheridge (acq.open-ils.org), Bill Erickson (dev.gapines.org)
PostgreSQL 9.0 support on Evergreen 2.0: Mike Rylander committed
a patch by Anoop Atre that seems to provide PostgreSQL 9.0 support
Mike Rylander requested community testing for binary upgrade from 8.4 to 9.0 (via pg_upgrade)
Patch reviews:
Dan Scott to apply 'Missing examples for "interval" settings' patch.
Bill Erickson to review 'Patron Registration Customization Overhaul' and send thoughts to dev-list by Thursday March 3.
Dan Scott to apply and test 'Permission Profile Filtering in Patron Search Interface'
STATUS: All three patches have been committed to trunk for further review/testing.
Google Summer of Code application: Galen and Dan put together an application and a
project coding ideas page with some help from the community
STATUS: GSoC application submitted. Will receive results by March 18th. See
full timeline
Discuss Postgresql locale recommendations - are current recommendations of 'C' as locale inviting problems for libraries using primarily non-Latin character sets?
There was considerable discussion, but eventually concluded that no change will be made in recommendation of using C for locale at this time. Further discussion to occur on the lists if necessary, but there was also post-meeting discussion that took place. See full log for details.
Patch review queue
Release statuses
How's that release process working out?
Evergreen release status:
1.6.1.x (current release = 1.6.1.7)
-
2.0.x (current release = 2.0.3)
-
2.1 status
-
Next meeting