User Tools

Site Tools


Developer meeting: December 21, 2010

Held at:

  • 09:00:00 a.m. Tuesday December 21, 2010 in America/Los_Angeles
  • 12:00:00 p.m. Tuesday December 21, 2010 in Canada/Eastern
  • 04:00:00 p.m. Tuesday December 21, 2010 in UTC

Last meeting: 2010-12-14


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


  1. Determine the taker of minutes:
  2. Determine meeting leader:
    1. ACTION: Dan Scott to continue working on his action items from previous meetings:
      1. Create a draft page and request feedback for "Evergreen supported releases" document.
      2. Write release notes for OpenSRF 1.6.12
        • ACTION: Deferred with an offer to adopt out to a loving family
      3. Implement proper library versioning using autotools for Evergreen release.
        • ACTION: Deferred with an offer to adopt out to a loving family
    2. Bug-squashing related:
      • ACTION: Jason Stephenson (head bug wrangler) to go through the list of "Fix Committed" bugs and change those that were tied to beta5 release to "Fix Released"
        • Status: Done
      • ACTION: Dan Scott to create an "Evergreen release team" on Launchpad with Mike Rylander, Dan Scott, and Jason Stephenson as starting members to coordinate bug targeting needs.
        • Status: Done
    3. ACTION: Mike Rylander to write release notes for Evergreen (5?)
      • STATUS: Deferred with an offer to adopt out to a loving family
    4. ACTION: Jason Etheridge to update with RC1 to allow for more public testing.
      • STATUS: Deferred until 2.0-RC1 actually exists.
  3. General news and issues:
    • OpenSRF 1.6.2 was released on Sunday
      • NOTES:
        • dbs noted that OpenSRF 1.6.2 is recommended for EG 1.6.1+
        • dbs noted that removal of /openils/lib/*oils* was required for a successful recompile of EG after upgrading from OpenSRF 1.2 to 1.6 (a full log of the upgrade process is available, warts and all
    • There is now an Evergreen security team on LaunchPad
      • This team is currently composed of the current committers, significant code contributors, and security bug reporters; their only power at the moment is to be able to read and edit LaunchPad bugs marked as "Security" issues
        • ACTION: miker suggested: an "anyone can post" moderated list made up of the LP sec team members; if yes, ESI can host. miker will propose on the -dev list
          • STATUS: Email sent to -dev.
      • There is some desire for a secure channel for discussions (mailing list, secured XMPP server, ?) outside of bugs - talking about security vulnerabilities on IRC is not ideal - but no action as of yet
      • LaunchPad mailing lists are all public, so that's not an option
    • OpenLibrary added content - there was a request on the list to backport to 1.6; should just be a matter of copying into place but per release guidelines new features should go into a new release (
      • ACTION: Consensus vote was "too late for 1.6"; will not be backported. Suggestion of a ILS-Contrib backport was raised.
    • Maybe we need a release checklist to follow so that steps for a release don't slip through the cracks (e.g. was cut and uploaded on 2010-12-10 but not updated on downloads page until 2010-12-21 and has not been announced on the mailing list or blog)? Something like the following, perhaps where a given branch has one person to fulfill each responsibility, and each of these steps could be further documented on the wiki (for example, rolling an OpenSRF release so that we can build more resilience into our release and development processes:
      1. release-lead cuts the release tarball and uploads to
      2. release-lead uploads the ChangeLog to
      3. staff-client-packager creates the Windows staff client and uploads to
      4. release-notes-writer puts final release notes on / into official documentation / wherever (assumes that release notes are created as the release is created, rather than after the fact)
      5. bug-wrangler changes "Fix committed" bugs to "Fix released" for that milestone
      6. bug-wrangler creates new milestone for that release
      7. web-team-member updates download page with new release
      8. communication-team-member announces release on mailing list / blog and updates wikipedia / freshmeat
      • ACTION: Consensus vote was to adopt this checklist. miker will propose a release coordination mailing list on -dev and -general; should be called out in the community meeting for non-developer resource acquisition (release-notes-writer, web-team-member and communication-team-member, in the least)
  4. 1.6.1.x release status (current release =
  5. 1.6.2.x release status (current release =
    1. Any feedback on
      • NOTES: No external feedback. will be cut with 2.0-RC1 (see below)
  6. 2.0 release status
    • Bugs targeted to RC1
      • Maybe a review of recently reported bugs should fall under a general QA/bug wrangler section?
    • A beta5 virtual image is available for download, just in time for…
    • 2.0 RC1?
      • ACTION: 2.0-RC1 to be cut once "Merging authority records" bug (above) is addressed, and Dan Wells has a chance to commit Serials fixes.
  7. Post-2.0 planning (probably not time to discuss today, but we should start thinking about things like this):
    • Update Dojo from 1.3 (released March 2009) to 1.5 (out since July 2010)?
    • Move to git or some other DVCS for the official repository?
      • ACTION: discussion postponed until next meeting.
  8. (2 min) Schedule next meeting
    • Guessing not… January 4th? January 11th?
    • ACTION: January 4th is the date of consensus
    • Tuesday, January 4th at 12:00 EST, 9:00 PST
dev/meetings/2010-12-21.txt · Last modified: 2022/02/10 13:34 by

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.