Differences

This shows you the differences between two versions of the page.

--- dev:meetings:2011-03-01 [2011/02/28 10:14] – created dbs
+++ dev:meetings:2011-03-01 [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== Developer meeting: March 1, 2011 ======
+Held at
+  * 09:00:00 a.m. Tuesday March 1, 2011 in America/Los_Angeles
+  * 12:00:00 p.m. Tuesday March 1, 2011 in Canada/Eastern
+  * 04:00:00 p.m. Tuesday March 1, 2011 in UTC
+Last meeting: [[dev:meetings:2011-02-08|2011-02-08]]
+===== Agenda =====
+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.
+===== Logs and minutes =====
+  * [[http://evergreen-ils.org/irc_logs/evergreen/2011-03/%23evergreen.01-Tue-2011.log|IRC logs]]
+  * Minutes will be supplied in this document after the meeting finishes
+===== Prior to the meeting =====
+  * Please fill out [[community:irc_channel|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: Dan Scott
 ===== OpenSRF 2.0.0 =====
 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 [[http://evergreen-ils.org/downloads.php#opensrf|has been released]].
@@ Line 5: / Line 32: @@
   * Determine why Unicode patron name entry / retrieval worked with previous versions of OpenSRF but is broken in current version
   * Test OpenSRF 2.0.0 for stability and potential adoption
+**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)
+===== PostgreSQL 9.0 support =====
+[[https://bugs.launchpad.net/evergreen/+bug/725809|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:
+  * Upgrade database to 8.4 and upgrade EG 1.6 to 2.0
+  * Upgrade database to 9.0 and upgrade EG 2.0 to 2.1
+This seems a bit headache-y.
+Discussed by developers:
+  * Summary by Dan Scott: "If someone puts together a patch to update the upgrade script to support 9.0, as well as an accompanying 2.0.x-2.0.y patch, and it gets tested successfully, we would accept it for 2.0.  A nice-to-have document would be a list of development targets and expected minimum prereqs (e.g. 2.1 - develop against postgresql 9.0 minimum)."
+  * Mike Rylander requests community testing for binary upgrade from 8.4 to 9.0 (via pg_upgrade)
 ===== Patch review queue =====
-We don't want to let submitted patches rot, here's a [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-datecreated&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.affects_me.used=&field.has_patch.used=&field.has_patch=on&field.has_branches.used=&field.has_no_branches.used=&field.has_blueprints.used=&field.has_no_blueprints.used=&search=Search|list of bugs with attached patches]]:
+We don't want to let submitted patches rot, here's a [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-datecreated&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.affects_me.used=&field.has_patch.used=&field.has_patch=on&field.has_branches.used=&field.has_no_branches.used=&field.has_blueprints.used=&field.has_no_blueprints.used=&search=Search|list of bugs with attached patches]], some of which are listed below:
   * [[https://bugs.launchpad.net/evergreen/+bug/720795|Patron Registration Customization Overhaul]]
   * [[https://bugs.launchpad.net/evergreen/+bug/715837|Permission Profile Filtering in Patron Search interface]]
   * [[https://bugs.launchpad.net/evergreen/+bug/717308|Missing examples for "interval" settings in Library Settings Editor]]
+Can we get committers to commit (hah) to reviewing and applying these patches (new features target 2.1 of course)?
+  * **ACTION ITEM**: Dan Scott to apply 'Missing examples for "interval" settings' patch.
+  * **ACTION ITEM**: Bill Erickson to review 'Patron Registration Customization Overhaul' and send thoughts to dev-list by Thursday March 3.
+  * **ACTION ITEM**: Dan Scott to apply and test 'Permission Profile Filtering in Patron Search Interface'
 ===== Google Summer of Code application =====
@@ Line 16: / Line 69: @@
   * Need to put together a solid application, with a list of potential ideas for student projects that would be helpful to Evergreen, ideally with a list of prerequisite knowledge and easy/medium/difficult ratings
     * Even if our application is turned down, it provides a good refresh of the long-in-the-tooth software bounties page and offers an entry point for other potential developers
-  * Deadline for applying: March 11, 2011; applications opened today
+  * Deadline for applying: March 11, 2011; applications opened Feb. 28th
+  * Dan Scott, Galen Charlton, and Jason Etheridge to meet and discuss potential projects list and application by next Tuesday, March 8.
+===== Release statuses =====
+  - Evergreen release status:
+    - 1.6.1.x (current release = 1.6.1.7)
+      - Bugs targeted to [[https://launchpad.net/evergreen/+milestone/1.6.1.8|1.6.1.8]]
+    - 2.0.x (current release = 2.0.2)
+      - Bugs targeted to [[https://launchpad.net/evergreen/+milestone/2.0.3|2.0.3]]
+    - 2.1 status
+      * Any target date yet?
+    - [[https://bugs.launchpad.net/evergreen/+bugs?orderby=-datecreated|Most recently reported bugs]]
+===== Next meeting =====
+  * [[dev:meetings:2011-03-15|Tuesday, March 15th]] at 12:00 EST, 9:00 PST