Table of Contents

Developer meeting: February 27, 2012

Meeting takes place on IRC on the #evergreen channel on Freenode. See the Calendar for specific dates and times.

Held at

Last meeting:

Logs and minutes

Links will be added after the MeetBot gives us links:

Agenda

  1. Determine the taker of minutes: MeetBot
  2. Determine meeting leader: bshum
  3. Start MeetBot recording: #startmeeting 2012-02-27 - Developer Meeting
  4. Review past action items:
    1. dbs to update the release process doc with a mention of the version_upgrade directory
      • STATUS: Updated release checklist with some specific mentions of the version_upgrade directory for creation & testing, however this is very high level and doesn't specify:
        • who actually will create the script (I lamely said evergreen-dev which leaves it pretty wide open)
        • naming conventions for the point-to-point upgrade scripts to avoid any ambiguity
        • expectations about what data should be upgraded and what should not be touched (for example, permissions and permission groups)
        • how to notify users about any outstanding manual steps that may need to be taken to complete the database schema upgrade
    2. bshum and others to continue thread discussion about developer meeting times.
      1. STATUS: Done by kmlussier, see mailing list. Thanks for participating in the doodle poll!
    3. dbs to talk about GSOC stuff next time (or send thoughts to -dev mailing list)
      1. STATUS: Done, see mailing list thread
  5. New business
    1. Google Summer of Code 2012 (denials)
    2. Evergreen 2.2 alpha2 / beta1 / RC?
    3. Applying Xulrunner/Firefox 4+ (tsbere)
    4. Developer Meeting Schedule
      1. Does the Doodle poll indicate that Mondays at this timeslot seems to work best for now? Should we consider other ways of managing/scheduling future developer meetings?
  6. Announcements?
  7. End MeetBot recording: #endmeeting