[joomla-wg-production] Production Leadership Team Minutes 18 May 2010

10 views
Skip to first unread message

Andrew Eddie

unread,
May 18, 2010, 7:48:12 PM5/18/10
to joomla-wg-...@googlegroups.com

Production Leadership Team Minutes 18 May 2010

Present: Andrew, Christophe, Mark, Louis, Ron
Apologies: Sam, Ian, Jean-Marie

Agenda

  1. Business arising from the previous meeting
    1. J1.6 communication
      1. Official PR went out as planned following interviews with Ryan, Louis, Andrew and Justin from Voxus.
    2. J1.5.17/1.5.18 followup
      1. Planned to release on 24 May 2010 but may delay due to other niggling issues as a result of version specific PHP bugs.
      2. Giving consideration to producing a test build prior to official release.
  2. Banned persons access to the IRC chat.
    1. Consensus is to maintain project bans in the JBS IRC chat in order to keep the environment safe.
    2. Louis to write up instructions for channel ops.
  3. Pros and cons to moving IRC to a private, invite only chat (but still an easy request to join).
    1. Keep the status quo for now and continue to monitor.
    2. Several casual observers have been picked up in the JBS in the last few days (very positive).
    3. Activity generally on the rise.
  4. Bug Squad Update
    1. Andrew added as JBS coordinator
    2. Patch / commit process for beta1 through rc1
      1. Only require one successful test for most patches instead of two.
      2. No change to trunk general and specialist committers for now.
    3. JBS Teams: Tracker, Testing, Coding, Automated Testing, Migration.
    4. New influx of JBS members 
    5. Webinars / training needed: SVN, How to Test, Coding standards, Unit testing, System Testing, Tracker process, Eclipse / Debugging, etc.
  5. Plan Process for Beta2 and beyond
    1. Feature patch tracker closed during the beta period, will reopen at the release of 1.6 GA (General Availability). Planning to rename the tracker to "Joomla CMS Feature Patches" so that the single tracker rolls from version to version.
    2. Mark and Louis to follow up David Vega on the UserVoice site.
    3. Iterative beta releases don't need a front page announcement, just a blog with a changelog will be satisfactory.
    4. No need for freezes, just tag and release from the tag.  Notionally tag at UTC 19:00 hours (Noon PDT) and release 2-4 hours after, allowing time to complete unit and functional tests.
    5. RC status still needs some fine tuning as to exactly "when" this is released.  RC is considered production ready.  All features need to be complete and operating (in other words, RC cannot have loose ends still to address).
    6. Look into ways to monitor how the beta and RC process is going and review our performance over time.
  6. Consideration for requesting http://saucelabs.com/ as a service.
    1. For-profit that sits beside Selenium
    2. Support something like 10 different browsers and capture screenshots of test failures.
    3. Would free up a lot of sys admin time mucking around with setting up the infrastructure (we just have to worry about creating the functional tests). Much better use of people's time (for probably less than $50 a month).
    4. Following up with how we can work together with them.
  7. PLT Overview Spreadsheet
    1. Consolidating all the PLT information into one central spreadsheet.
    2. Will make public readable once everyone has a chance to touch it up.

--
You received this message because you are subscribed to the Google Groups "Joomla! Production Working Group Leadership" group.
To post to this group, send email to joomla-wg-...@googlegroups.com.
To unsubscribe from this group, send email to joomla-wg-produc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/joomla-wg-production?hl=en.
Reply all
Reply to author
Forward
0 new messages