Production Leadership Team Minutes 18 May 2010
Present:
Andrew, Christophe, Mark, Louis, Ron
Apologies: Sam,
Ian, Jean-Marie
Agenda
- Business
arising from the previous meeting
- J1.6 communication
- Official
PR went out as planned following interviews with Ryan, Louis, Andrew
and Justin from Voxus.
- J1.5.17/1.5.18
followup
- Planned to release on 24 May 2010 but may delay
due to other niggling issues as a result of version specific PHP bugs.
- Giving
consideration to producing a test build prior to official release.
- Banned
persons access to the IRC chat.
- Consensus is to maintain
project bans in the JBS IRC chat in order to keep the environment safe.
- Louis
to write up instructions for channel ops.
- Pros and
cons to moving IRC to a private, invite only chat (but still an easy
request to join).
- Keep the status quo for now and continue
to monitor.
- Several casual observers have been picked up in the
JBS in the last few days (very positive).
- Activity generally on
the rise.
- Bug Squad Update
- Andrew added as
JBS coordinator
- Patch / commit process for beta1 through rc1
- Only
require one successful test for most patches instead of two.
- No
change to trunk general and specialist committers for now.
- JBS
Teams: Tracker, Testing, Coding, Automated Testing, Migration.
- New
influx of JBS members
- Webinars / training needed: SVN, How to
Test, Coding standards, Unit testing, System Testing, Tracker process,
Eclipse / Debugging, etc.
- Plan Process for
Beta2 and beyond
- 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.
- Mark
and Louis to follow up David Vega on the UserVoice site.
- Iterative
beta releases don't need a front page announcement, just a blog with a
changelog will be satisfactory.
- 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.
- 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).
- Look into ways to
monitor how the beta and RC process is going and review our performance
over time.
- Consideration for requesting
http://saucelabs.com/ as a service.
- For-profit that sits
beside Selenium
- Support something like 10 different browsers and
capture screenshots of test failures.
- 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).
- Following up with how we can work together with them.
- PLT
Overview Spreadsheet
- Consolidating all the PLT information
into one central spreadsheet.
- 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.