Actions

Developer Area/Developer Meetings/29: Difference between revisions

From Mahara Wiki

< Developer Area‎ | Developer Meetings
No edit summary
No edit summary
Line 13: Line 13:
# Drop support for MySQL 5.1 in Mahara 1.9
# Drop support for MySQL 5.1 in Mahara 1.9
## For 1.8 we claim to support MySQL 5.1 or later, but all the devs are actually running 5.5 or later. So, since 5.5 will have been in a stable release for 4 years by the time 1.9 comes out, we should just raise the minimum supported version to 5.5.
## For 1.8 we claim to support MySQL 5.1 or later, but all the devs are actually running 5.5 or later. So, since 5.5 will have been in a stable release for 4 years by the time 1.9 comes out, we should just raise the minimum supported version to 5.5.
## If we don't want to drop 5.1 completely, we should consider requiring 5.1.6 or later, because 5.1.6 makes the trigger creation permissions a bit more sensible: https://bugs.launchpad.net/mahara/+bug/1237198/comments/8
# Plans & priorities for Mahara 1.9
# Plans & priorities for Mahara 1.9
## Some of the things the Catalyst team is looking at for 1.9 are:
## Some of the things the Catalyst team is looking at for 1.9 are:

Revision as of 12:17, 28 November 2013

Agenda for the 29th Mahara developer meeting on Thursday, 5 December 2013 at 8:00 UTC

The developer meetings are held on IRC in the #mahara-dev channel. An IRC bot will be used to take minutes of these meetings and agendas made available on these pages before-hand.

If you don't have an IRC client, you can join us using your web browser.

Chair: Aaron Wells

Agenda:

  1. Items from last meeting
    1. The "Choose a skin" contest
  2. Drop support for MySQL 5.1 in Mahara 1.9
    1. For 1.8 we claim to support MySQL 5.1 or later, but all the devs are actually running 5.5 or later. So, since 5.5 will have been in a stable release for 4 years by the time 1.9 comes out, we should just raise the minimum supported version to 5.5.
    2. If we don't want to drop 5.1 completely, we should consider requiring 5.1.6 or later, because 5.1.6 makes the trigger creation permissions a bit more sensible: https://bugs.launchpad.net/mahara/+bug/1237198/comments/8
  3. Plans & priorities for Mahara 1.9
    1. Some of the things the Catalyst team is looking at for 1.9 are:
      1. Automated testing
      2. Accessibility (though after consulting with our accessibility tzar we've determined that non-JS operation is not required by modern accessibility standards)
      3. Upstreaming third-party "Sent Messages" and Inbox improvements
  4. Next meeting and chair
  5. Any other business