====== Developer Meeting: December 17, 2012 ======

Held at 
   * 10:00:00 a.m. Monday, December 17, 2012 in America/Los_Angeles
   * 1:00:00 p.m. Monday, December 17, 2012 in Canada/Eastern
   * 18:00:00 Monday, December 17, 2012 in UTC

===== Logs and Minutes =====
   * Minutes: http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-12-17-13.03.html
   * Minutes (text): http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-12-17-13.03.txt
   * Log: http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-12-17-13.03.log.html

===== Action Items from Last Meeting =====
  - Draft summary of "how we handle security-related bugs" and disseminate through appropriate channels.
     - **STATUS** - Draft document available at [[dev:security]], feedback and edits solicited in a post to open-ils-dev.
  - edoceo to work on setting up a dojo 1.6 test server
     - **STATUS?**
  - kmlussier to help coordinate end-user testing
     - **STATUS** - waiting for setup of dojo test server
  - kmlussier, bshum (and others) to edit the TPAC plan wiki page and create appropriate bug links if necessary.
     - **STATUS** - Update from kmlussier: I updated [[http://open-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:plan|TPAC plan wiki page]] to more clearly identify missing jspac features and created corresponding Launchpad entries for most of them. I also added jspacremovalblocker tags to the very few LP entries I consider to be blockers. We need more people looking at these bugs and adding the jspacremovalblocker tags where necessary. I particularly would like to hear from people who were one jspac longer than the MassLNC consortia were since I don't have a long history with any of these missing features.

==== GSoC reports ====

Will anything from the GSoC projects land in 2.4?


==== Release info ====

=== Evergreen ===

Dyrcona wants to discuss 2 things related to releases:

  - Creating releases and "Fix Released" bugs for alphas, betas, and RCs.
  - Bug targeting at series and milestones for releases.

Dan wants to ask about:

  - Monthly minor release cycle - we released 2.3.1/2.2.3/2.1.4 on 2012-11-08, we're due for 2.3.2/2.2.4 - going to happen?
  - We seem to be slipping on the communications from release managers / dev team outward to the broader community.
    - Related; what's the plan for 2.4? We need to get some milestones (both technical and calendar-oriented) in place.
  - [[dev:Signoff/review checklist]] proposal for ensuring we don't forget important bits during signoff & commit. Needs revision & extension, but might be a good start?