Held at
Last meeting: 2011-02-08
Meeting takes place on IRC on the #evergreen channel on Freenode. See the Calendar for specific dates and times.
Problem was observed with entering / retrieving patron names containing Unicode in Evergreen 2.0 on OpenSRF 1.6. Dan found a fix for the problem in OpenSRF 2.0 but there's a different problem with OpenSRF 1.6, thus a release candidate of 2.0.0 has been released.
TODO:
ACTION ITEM: Test OpenSRF 2.0.0 with Evergreen 2.0.2 for stability and potential adoption: Ben Shum (tbd), Jason Etheridge (acq.open-ils.org), Bill Erickson (dev.gapines.org)
Bug 725809 reports a problem upgrading from Evergreen 1.6 to 2.0 on a PostgreSQL 9.0 server.
Given that we largely didn't test or develop the Evergreen 2.0 upgrade script on PostgreSQL 9.0, are we supporting it for Evergreen 2.0?
If we do want to support PostgreSQL 9.0 for Evergreen 2.0, then does the path for support become running the 1.6-2.0.X script, where "X" is the iteration where all of the PostgreSQL 9.0 kinks are worked out?
If we don't want to support PostgreSQL 9.0 for Evergreen 2.0, then does the migration path from 1.6 to 2.1 become:
This seems a bit headache-y.
Discussed by developers:
We don't want to let submitted patches rot, here's a list of bugs with attached patches, some of which are listed below:
Can we get committers to commit (hah) to reviewing and applying these patches (new features target 2.1 of course)?