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.

• Raw IRC logs
• Minutes - look below!

• 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. 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.
         1. Status: Here's the page, please provide feedback to the open-ils-general mailing list
      2. Write release notes for OpenSRF 1.6.1
      3. Implement proper library versioning using autotools for Evergreen release.
   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 1.6.1.4 (5?)
   4. ACTION: Jason Etheridge to update acq.open-ils.org with RC1 to allow for more public testing.
4. General news and issues:
   • OpenSRF 1.6.2 was released on Sunday
   • 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
     • 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 OpenLibrary.pm into place but per release guidelines new features should go into a new release (1.6.3.0)
   • Maybe we need a release checklist to follow so that steps for a release don't slip through the cracks (e.g. 1.6.1.5 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 evergreen-ils.org
     2. release-lead uploads the ChangeLog to evergreen-ils.org
     3. staff-client-packager creates the Windows staff client and uploads to evergreen-ils.org
     4. release-notes-writer puts final release notes on evergreen-ils.org / 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
5. 1.6.1.x release status (current release = 1.6.1.5)
   • http://evergreen-ils.org/downloads.php needs to reflect this, still says 1.6.1.4
     • Status: dbs has now updated this
6. 1.6.2.x release status (current release = 1.6.2.0-rc1)
   1. Any feedback on 1.6.2.0-rc1?
7. 2.0 release status
   • Bugs targeted to RC1
   • Most recently reported bugs
     • 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?
8. 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?
9. (2 min) Schedule next meeting
   • Tuesday, December 28th at 12:00 EST, 9:00 PST
     • Guessing not… January 4th? January 11th?
   • http://evergreen-ils.org/calendar has the next 6 weeks blocked for the same time, same place