Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-42931

Decide Moodle 2.7 requirements and push them to environment.xml

    Details

    • Testing Instructions:
      Hide

      0) To test exclusively in all supported stable branches.
      1) Go to admin -> server -> environment
      2) One "2.7 upwards" Moodle version should be available.
      3) It shows the same requirements than a 2.6 version but with these differences:

      a) verify that zlib is required
      b) verify higher versions of database are required
      c) verify PHP 5.4.x is required

      Show
      0) To test exclusively in all supported stable branches. 1) Go to admin -> server -> environment 2) One "2.7 upwards" Moodle version should be available. 3) It shows the same requirements than a 2.6 version but with these differences: a) verify that zlib is required b) verify higher versions of database are required c) verify PHP 5.4.x is required
    • Difficulty:
      Moderate
    • Affected Branches:
      MOODLE_27_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE, MOODLE_25_STABLE, MOODLE_26_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      w51_MDL-42931_m27_env27
    • Sprint:
      BACKEND Sprint 8
    • Story Points (Obsolete):
      13
    • Sprint:
      BACKEND Sprint 8

      Description

      We need to decide ASAP about all the PHP/DB/Moodle versions requirements and put all them into the environmental tests (adding them to all supported branches).

      At the same time, if there is any change in the PHP version... some changes have to be populated to various installers and replace them by the new one when corresponding. To get a list of candidates:

      grep -r '5\.3\.3' * | grep '\.php'

      (and look for MDL-39007 status, about to unify all those duplicated checks)

      Ciao

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Some things to consider:

            A) Make the zlib extension required. It was suggested (and rejected) for 2.6. Let's reconsider it for 2.7. Note this will imply creating some issues to get rid of conditional code in some places.

            B) PHP version... 5.3 is EOL since March 2013. Slower and unmaintained. Consider availability and so on.

            C) DB versions. Review all them, considering availability and so on.

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Some things to consider: A) Make the zlib extension required. It was suggested (and rejected) for 2.6. Let's reconsider it for 2.7. Note this will imply creating some issues to get rid of conditional code in some places. B) PHP version... 5.3 is EOL since March 2013. Slower and unmaintained. Consider availability and so on. C) DB versions. Review all them, considering availability and so on.
            Hide
            gb2048 Gareth J Barnard added a comment -

            Hi Eloy Lafuente (stronk7),

            Looking at http://www.php.net/eol.php - I can't see that PHP 5.3 has reached EOL - where did you get the info from?

            Cheers,

            Gareth

            Show
            gb2048 Gareth J Barnard added a comment - Hi Eloy Lafuente (stronk7) , Looking at http://www.php.net/eol.php - I can't see that PHP 5.3 has reached EOL - where did you get the info from? Cheers, Gareth
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Lol, true it's not there, but i was sure I had read it somewhere time ago:

            Ciao

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Lol, true it's not there, but i was sure I had read it somewhere time ago: http://php.net/releases/5_3_20.php https://wiki.php.net/rfc/php53eol http://php.net/releases/5_3_27.php Ciao
            Hide
            gb2048 Gareth J Barnard added a comment -

            Does updating to Bootstrap v3 count as a possible M2.7 requirement? -> MDL-40177

            Show
            gb2048 Gareth J Barnard added a comment - Does updating to Bootstrap v3 count as a possible M2.7 requirement? -> MDL-40177
            Hide
            skodak Petr Skoda added a comment -

            My candidates:

            • zlib extension requirement
            • slasharguments requirement - even IIS supports it now by default
            • higher PHP version - RHEL+Centos should have some 5.4.* in new repo soon, this leaves us with outdated Debian stuff only - the problem here is that if 2.7 is a LTS we should make the PHP requirement higher because we would need to support ancient PHP like forever
            • latest PHP 5.4.x or 5.5.x on Windows should be strongly recommended - they must not use outdated/buggy/insecure versions there
            • drop Oracle support if 2.7 is LTS - no installer for Oracle, just migration from Oracle to anything else
            Show
            skodak Petr Skoda added a comment - My candidates: zlib extension requirement slasharguments requirement - even IIS supports it now by default higher PHP version - RHEL+Centos should have some 5.4.* in new repo soon, this leaves us with outdated Debian stuff only - the problem here is that if 2.7 is a LTS we should make the PHP requirement higher because we would need to support ancient PHP like forever latest PHP 5.4.x or 5.5.x on Windows should be strongly recommended - they must not use outdated/buggy/insecure versions there drop Oracle support if 2.7 is LTS - no installer for Oracle, just migration from Oracle to anything else
            Hide
            samhemelryk Sam Hemelryk added a comment -

            I'd +1 the following:

            • Require zlib extension.
            • PHP 5.4 - I agree with Petr's view.

            I've not a strong enough knowledge of DB stuff to comment on support there, no doubt any endeavour there would involve working out who is using what out there.

            Show
            samhemelryk Sam Hemelryk added a comment - I'd +1 the following: Require zlib extension. PHP 5.4 - I agree with Petr's view. I've not a strong enough knowledge of DB stuff to comment on support there, no doubt any endeavour there would involve working out who is using what out there.
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Note: People using debian can switch to http://www.dotdeb.org. I'm using those packages since ages ago in my servers and have had zero problems with them so far.

            So:

            • +1 for bumping PHP to 5.4.x (it's like night and day, apart from security and other aspects...).
            • +1 for both zlib and slasharguments if there is no (meaningful) platform not supporting them.
            • +1 to review databases availability and raise requirements (MySQL 5.5, PostgreSQL 9.1 - current 8.3 is EOL since Feb 2013, MSSQL 2008, Oracle 12). That would unlock some databases work (better collations support, limits in varchar, better regexp support...). Of course -1 to to drop Oracle support.

            Ciao

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Note: People using debian can switch to http://www.dotdeb.org . I'm using those packages since ages ago in my servers and have had zero problems with them so far. So: +1 for bumping PHP to 5.4.x (it's like night and day, apart from security and other aspects...). +1 for both zlib and slasharguments if there is no (meaningful) platform not supporting them. +1 to review databases availability and raise requirements (MySQL 5.5, PostgreSQL 9.1 - current 8.3 is EOL since Feb 2013, MSSQL 2008, Oracle 12). That would unlock some databases work (better collations support, limits in varchar, better regexp support...). Of course -1 to to drop Oracle support. Ciao
            Hide
            dougiamas Martin Dougiamas added a comment -

            This has been added to the current BACKEND sprint for devs and integrators to decide on it in the next week or two.

            +1 from me for PHP 5.4
            +1 for zlib and slasharguments
            +1 for a very recent Oracle (if we're keeping it) ... MySQL and Postgres should follow common Linux distributions.

            Show
            dougiamas Martin Dougiamas added a comment - This has been added to the current BACKEND sprint for devs and integrators to decide on it in the next week or two. +1 from me for PHP 5.4 +1 for zlib and slasharguments +1 for a very recent Oracle (if we're keeping it) ... MySQL and Postgres should follow common Linux distributions.
            Hide
            damyon Damyon Wiese added a comment -

            Can we please increase the ridiculous memory limit warning from 40M to something that actually works? It is hard to pick a number - but if you can't even load the admin pages surely it's too low.

            Show
            damyon Damyon Wiese added a comment - Can we please increase the ridiculous memory limit warning from 40M to something that actually works? It is hard to pick a number - but if you can't even load the admin pages surely it's too low.
            Hide
            dougiamas Martin Dougiamas added a comment -

            Would be good if someone can post on moodle.org GDF at least to let people know this is being decided.

            Show
            dougiamas Martin Dougiamas added a comment - Would be good if someone can post on moodle.org GDF at least to let people know this is being decided.
            Hide
            danmarsden Dan Marsden added a comment -

            +1 for PHP 5.4
            +1 for zlib and slasharguments
            +1 to drop Oracle support - people are trying to use Moodle with Oracle in high use environments and PHP's Oracle driver is really poor and there's not much tweaking that can be done to improve it. In all cases, when a client has come to us with issues related to performance with Moodle on Oracle we've eventually moved them to PostGres. Usually after they've spent a significant number of dollars on Oracle consultants. If someone can fix the PHP Oracle driver (or can point to some work/improvements that make it better) please let us know - in the interim Moodle providing "support" for Oracle causes more problems for Moodle Partners that it should.

            Show
            danmarsden Dan Marsden added a comment - +1 for PHP 5.4 +1 for zlib and slasharguments +1 to drop Oracle support - people are trying to use Moodle with Oracle in high use environments and PHP's Oracle driver is really poor and there's not much tweaking that can be done to improve it. In all cases, when a client has come to us with issues related to performance with Moodle on Oracle we've eventually moved them to PostGres. Usually after they've spent a significant number of dollars on Oracle consultants. If someone can fix the PHP Oracle driver (or can point to some work/improvements that make it better) please let us know - in the interim Moodle providing "support" for Oracle causes more problems for Moodle Partners that it should.
            Hide
            dougiamas Martin Dougiamas added a comment -

            Regarding Oracle, see MDL-41310. I would doubt we can actually drop it in 2.7 ... even if we were going to drop it, we'd need to provide more lead notice than that.

            Show
            dougiamas Martin Dougiamas added a comment - Regarding Oracle, see MDL-41310 . I would doubt we can actually drop it in 2.7 ... even if we were going to drop it, we'd need to provide more lead notice than that.
            Hide
            skodak Petr Skoda added a comment -

            ==Operating systems==

            ===Debian===
            1. future (jessie) - unknown release date, PHP 5.5.6
            2. current (7.0 wheezy) - PHP 5.4.4, MySQL 5.5.31, MariaDB n/a (upstream only), PostgreSQL 9.1
            3. previous (6.0 squeeze) - outdated, upgrade

            Alternatives:

            • use Dotdeb to get decent PHP

            ===Redhat/CentOS===
            1. future (7) - unknown release date and details
            2. current (6.5) - PHP 5.4.16, MySQL 5.5.32, MariaDB 5.5.32, PostgreSQL 9.2.4
            3. previous (5.x) - outdated PHP 5.3.x, use Remi repository with latest versions of PHP, etc.

            More info:

            ===Ubuntu===
            1. future LTS (14.04) - mostly up-to-date, to be released before Moodle 2.7
            2. current LTS (12.05) - ancient PHP 5.3.10, MySQL 5.5.34, PostgreSQL 9.1.0, MariaDB n/a (upstream only) - use php5-oldstable repository
            3. previous LTS (10.04) - outdated, upgrade

            Alternatives:

            ===Windows===
            Always use the latest released versions of everything - no excuses! There are no security backports on Windows...

            ==Third-party libraries==

            ==PHPUnit==
            1. future (3.8) - requires PHP 5.4.7 or PHP 5.5.1
            2. current (3.7) - requires PHP 5.3.3

            ==Moodle features==

            ===Password hashing===
            Requires PHP 5.3.7, we could finally cleanup legacy code for older PHP versions.

            ===zlib library===
            We already required it in old 1.x Moodle releases, it should be available everywhere now.

            ==Useful new PHP 5.4 features==
            1. htmlspecialchars() and htmlentities() is now UTF-8, instead of ISO-8859-1 - SECURITY IMPROVEMENT!
            2. New timezone setup - finally defaults to UTC when unknown.
            3. Major json improvements.
            4. Major cleanup - safemode, register_globals, calltime pass by ref, etc removed - we can cleanup the code.
            5. foo()[0]
            6. (new Foo)->bar()
            7. callable typehint
            8. getallheaders() outside of apache, new http_response_code()
            9. new SessionHandler could be used to improve our new session drivers
            10. ICU transliterator can be used instead of buggy icong and typo3 transliteration to ASCII
            11. LDAP paged results - auth and enrol cleanup.

            ==Other==

            ===Slasharguments===
            The only problem is IIS and URL rewriting, we can go half way and always generate slashargument links in HTML but we still need to support the ?file=/xx/xx. In any case that would be a huge step forward and it would eliminate multiple problems in addons and core hacks.

            ===Oracle===
            Removing the WEB and CLI installer options for Oracle should be the first step. We should also prevent database migration to Oracle and support only migration from Oracle to supported database.

            The next step is to stop testing Oracle and just rely on patches from contributors.

            We should also relax the varchar size limit and lift the table name limit (or hack around it) and show only a warning in the XMLDB editor. The core would still obey the old limits but addons would be free to decide if they want to consider basic Oracle support.

            The 2.7 release notes would just state that Oracle is not supported any more, but still mostly functional.

            Show
            skodak Petr Skoda added a comment - ==Operating systems== ===Debian=== 1. future (jessie) - unknown release date, PHP 5.5.6 2. current (7.0 wheezy) - PHP 5.4.4, MySQL 5.5.31, MariaDB n/a (upstream only), PostgreSQL 9.1 3. previous (6.0 squeeze) - outdated, upgrade Alternatives: use Dotdeb to get decent PHP ===Redhat/CentOS=== 1. future (7) - unknown release date and details 2. current (6.5) - PHP 5.4.16, MySQL 5.5.32, MariaDB 5.5.32, PostgreSQL 9.2.4 3. previous (5.x) - outdated PHP 5.3.x, use Remi repository with latest versions of PHP, etc. More info: http://developerblog.redhat.com/2013/09/12/rhscl1-ga/ http://lists.centos.org/pipermail/centos-announce/2013-October/020000.html ===Ubuntu=== 1. future LTS (14.04) - mostly up-to-date, to be released before Moodle 2.7 2. current LTS (12.05) - ancient PHP 5.3.10, MySQL 5.5.34, PostgreSQL 9.1.0, MariaDB n/a (upstream only) - use php5-oldstable repository 3. previous LTS (10.04) - outdated, upgrade Alternatives: https://launchpad.net/~ondrej/+archive/php5-oldstable http://askubuntu.com/questions/343560/update-server-php-version-to-5-4-10-via-the-command-line http://askubuntu.com/questions/109404/how-do-i-install-latest-php-in-supported-ubuntu-versions-like-5-4-x-in-ubuntu-1 ===Windows=== Always use the latest released versions of everything - no excuses! There are no security backports on Windows... ==Third-party libraries== ==PHPUnit== 1. future (3.8) - requires PHP 5.4.7 or PHP 5.5.1 2. current (3.7) - requires PHP 5.3.3 ==Moodle features== ===Password hashing=== Requires PHP 5.3.7, we could finally cleanup legacy code for older PHP versions. ===zlib library=== We already required it in old 1.x Moodle releases, it should be available everywhere now. ==Useful new PHP 5.4 features== 1. htmlspecialchars() and htmlentities() is now UTF-8, instead of ISO-8859-1 - SECURITY IMPROVEMENT! 2. New timezone setup - finally defaults to UTC when unknown. 3. Major json improvements. 4. Major cleanup - safemode, register_globals, calltime pass by ref, etc removed - we can cleanup the code. 5. foo() [0] 6. (new Foo)->bar() 7. callable typehint 8. getallheaders() outside of apache, new http_response_code() 9. new SessionHandler could be used to improve our new session drivers 10. ICU transliterator can be used instead of buggy icong and typo3 transliteration to ASCII 11. LDAP paged results - auth and enrol cleanup. ==Other== ===Slasharguments=== The only problem is IIS and URL rewriting, we can go half way and always generate slashargument links in HTML but we still need to support the ?file=/xx/xx. In any case that would be a huge step forward and it would eliminate multiple problems in addons and core hacks. ===Oracle=== Removing the WEB and CLI installer options for Oracle should be the first step. We should also prevent database migration to Oracle and support only migration from Oracle to supported database. The next step is to stop testing Oracle and just rely on patches from contributors. We should also relax the varchar size limit and lift the table name limit (or hack around it) and show only a warning in the XMLDB editor. The core would still obey the old limits but addons would be free to decide if they want to consider basic Oracle support. The 2.7 release notes would just state that Oracle is not supported any more, but still mostly functional.
            Hide
            skodak Petr Skoda added a comment -

            My proposal for 2.7:

            • PHP 5.4.4 (5.4.7 recommended - in release notes and installation page)
            • MySQL 5.5.31
            • MariaDB 5.5.31
            • PostgreSQL 9.1
            • zlib extension required
            • IIS 7 with FastCGI only - warning if older or CGI
              * Memory limit 96MB (with opcache the memory use is significantly lower)

            Other:

            • slasharguments or URL rewriting required - release notes only, no way to test this during upgrade or install
              * safe_mode check can be removed (not available in PHP 5.4)
            Show
            skodak Petr Skoda added a comment - My proposal for 2.7: PHP 5.4.4 (5.4.7 recommended - in release notes and installation page) MySQL 5.5.31 MariaDB 5.5.31 PostgreSQL 9.1 zlib extension required IIS 7 with FastCGI only - warning if older or CGI * Memory limit 96MB (with opcache the memory use is significantly lower) Other: slasharguments or URL rewriting required - release notes only, no way to test this during upgrade or install * safe_mode check can be removed (not available in PHP 5.4)
            Hide
            skodak Petr Skoda added a comment -

            Submitting for peer-review, I will cherry pick the environment.xml commit to stables after review.

            Show
            skodak Petr Skoda added a comment - Submitting for peer-review, I will cherry pick the environment.xml commit to stables after review.
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment - - edited

            Everything looks ok but, some (conditional) points:

            • If Ubuntu 14.04 is ok (fulfills the requirements).
            • If all them come/have zlib enabled.

            Then +1 to raise PHP to 5.4.4 and make zlib mandatory.

            • If the Windows stuff (IIS 7 and slasharguments) is ok (I don't know a word about it)

            Then +1 to request that IIS 7 and disable (total or partially) slasharguments.

            Oracle: Ok to raise to 10.2. Any other consideration goes to MDL-41310.
            MSSQL: Surely can be raised to 2008 at least (it's near 6 years old!).

            Edited: Forget my 10.2 comment, I confused 10.2 and 12.0. The former is current requirement that remains unmodified.

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - - edited Everything looks ok but, some (conditional) points: If Ubuntu 14.04 is ok (fulfills the requirements). If all them come/have zlib enabled. Then +1 to raise PHP to 5.4.4 and make zlib mandatory. If the Windows stuff (IIS 7 and slasharguments) is ok (I don't know a word about it) Then +1 to request that IIS 7 and disable (total or partially) slasharguments. Oracle: Ok to raise to 10.2. Any other consideration goes to MDL-41310 . MSSQL: Surely can be raised to 2008 at least (it's near 6 years old!). Edited: Forget my 10.2 comment, I confused 10.2 and 12.0. The former is current requirement that remains unmodified.
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            (btw, really not sure why you've sent this to peer-review at all)

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - (btw, really not sure why you've sent this to peer-review at all)
            Hide
            skodak Petr Skoda added a comment -

            The rules are that everything goes through peer review, do not ask me why.

            * zlib should be enabled everywhere because it is not a real extension, but a compilation flag - we would get tons of queries from ppl installing 2.6 already if it was a problem

            • Ubuntu 14.04 will exceed the requirements (PHP 5.5.3 there now)
            • MSSQL - ok I will bump it up to 10 (=== SQL Server 2008)
            • I am not going to touch Oracle - it is a mess, they did not release XE 12 yet, and I always have problems configuring 11; I do not think we need to change anything there
            Show
            skodak Petr Skoda added a comment - The rules are that everything goes through peer review, do not ask me why. * zlib should be enabled everywhere because it is not a real extension, but a compilation flag - we would get tons of queries from ppl installing 2.6 already if it was a problem Ubuntu 14.04 will exceed the requirements (PHP 5.5.3 there now) MSSQL - ok I will bump it up to 10 (=== SQL Server 2008) I am not going to touch Oracle - it is a mess, they did not release XE 12 yet, and I always have problems configuring 11; I do not think we need to change anything there
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Reopening because this has not been agreed yet. It's just Petr's proposal that looks basically ok but the points in my previous comment.

            Please drop any thought ASAP, this it top priority.

            TIA and ciao

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Reopening because this has not been agreed yet. It's just Petr's proposal that looks basically ok but the points in my previous comment. Please drop any thought ASAP, this it top priority. TIA and ciao
            Hide
            poltawski Dan Poltawski added a comment -

            My only concern was php 5.4, but +1 to bump php for this release as CentOS/RHEL & Ubuntu LTS are really long-term releases and I think there are good quality repositories for people to use for back ports there. Also, waiting 6 months won't change the situation for them.

            Show
            poltawski Dan Poltawski added a comment - My only concern was php 5.4, but +1 to bump php for this release as CentOS/RHEL & Ubuntu LTS are really long-term releases and I think there are good quality repositories for people to use for back ports there. Also, waiting 6 months won't change the situation for them.
            Hide
            damyon Damyon Wiese added a comment -

            I don't have opcache so can't test - but does the admin tree search work with that low a memory limit ?

            Show
            damyon Damyon Wiese added a comment - I don't have opcache so can't test - but does the admin tree search work with that low a memory limit ?
            Hide
            dougiamas Martin Dougiamas added a comment -

            As a datapoint: Among the HQ developers we voted 6 to 3 to upgrade PHP to 5.4(.4).

            Show
            dougiamas Martin Dougiamas added a comment - As a datapoint: Among the HQ developers we voted 6 to 3 to upgrade PHP to 5.4(.4).
            Hide
            skodak Petr Skoda added a comment - - edited

            Damyon Wiese admin search takes on my 64bit Mac Ports PHP 5.5.X:

            • with comments - RAM peak: 18.2MB
            • without comments - RAM peak: 17.3MB
            • opcache disabled in config.php - RAM peak: 64.6MB

            So I guess 96MB is a reasonable minimum.

            Show
            skodak Petr Skoda added a comment - - edited Damyon Wiese admin search takes on my 64bit Mac Ports PHP 5.5.X: with comments - RAM peak: 18.2MB without comments - RAM peak: 17.3MB opcache disabled in config.php - RAM peak: 64.6MB So I guess 96MB is a reasonable minimum.
            Hide
            mchurch Mike Churchward added a comment -

            Martin Dougiamas interesting that the vote was 6 to 3... What were the reasons for the 3 to vote no?

            Show
            mchurch Mike Churchward added a comment - Martin Dougiamas interesting that the vote was 6 to 3... What were the reasons for the 3 to vote no?
            Hide
            derekcx Derek Chirnside added a comment -

            I was also curious about the vote. Does this mean MoodleHQ is a democracy.
            I've only come across this PHP question recently as we are doing the upgrade to 2.6. I've been told using PHP 5.5 now will improve speed to do with improved caching.

            Based on what I know, the times between upgrades, start of year for institutions, I'd say yes to 5.4.4 minimum. We have enough time to get ourselves sorted.

            Show
            derekcx Derek Chirnside added a comment - I was also curious about the vote. Does this mean MoodleHQ is a democracy. I've only come across this PHP question recently as we are doing the upgrade to 2.6. I've been told using PHP 5.5 now will improve speed to do with improved caching. Based on what I know, the times between upgrades, start of year for institutions, I'd say yes to 5.4.4 minimum. We have enough time to get ourselves sorted.
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Confusing the right to vote (here and there) with a democracy is one of the biggest mistakes I'm aware of. Politics aside, at least, in Moodle, we all know who our repellent benevolent dictator is. That's a big win, compared with real life.

            ~~ stronk7fucius 2013

            LOL

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Confusing the right to vote (here and there) with a democracy is one of the biggest mistakes I'm aware of. Politics aside, at least, in Moodle, we all know who our repellent benevolent dictator is. That's a big win, compared with real life. ~~ stronk7fucius 2013 LOL
            Hide
            skodak Petr Skoda added a comment -

            no major objections, yay, submitting for integration - please note the IIS warnings are not included, they are going to be master only if implemented anyway

            thanks everybody!

            Show
            skodak Petr Skoda added a comment - no major objections, yay, submitting for integration - please note the IIS warnings are not included, they are going to be master only if implemented anyway thanks everybody!
            Hide
            dougiamas Martin Dougiamas added a comment -

            Mike, Derek, it was just a simple datapoint to show opinions here after a discussion of all the pros and cons.

            Not meant to determine anything, we looked for wider feedback too.

            That said the 3 dissidents did regrettably all experience a freak electrical accident shortly afterwards. Such a shame.

            Show
            dougiamas Martin Dougiamas added a comment - Mike, Derek, it was just a simple datapoint to show opinions here after a discussion of all the pros and cons. Not meant to determine anything, we looked for wider feedback too. That said the 3 dissidents did regrettably all experience a freak electrical accident shortly afterwards. Such a shame.
            Hide
            dougiamas Martin Dougiamas added a comment -

            Please check/update this when done: http://docs.moodle.org/dev/Moodle_2.7_release_notes

            Show
            dougiamas Martin Dougiamas added a comment - Please check/update this when done: http://docs.moodle.org/dev/Moodle_2.7_release_notes
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            All right but, Petr, you need to detail the expected differences in the testing instructions.

            Side note: Some day we should unify all those (now) 5.4.4 comparisons and messages.

            Ciao

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - All right but, Petr, you need to detail the expected differences in the testing instructions. Side note: Some day we should unify all those (now) 5.4.4 comparisons and messages. Ciao
            Hide
            samhemelryk Sam Hemelryk added a comment -

            Thanks everyone, this has been integrated

            Show
            samhemelryk Sam Hemelryk added a comment - Thanks everyone, this has been integrated
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            FYI: I've created MDL-43402 about to clean all conditional code in core looking for zlib availability.

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - FYI: I've created MDL-43402 about to clean all conditional code in core looking for zlib availability.
            Hide
            phalacee Jason Fowler added a comment -

            Shame, most of HQ's devs are running Ubuntu 12.04 LTS, which is still at 5.3.X for PHP.

            Show
            phalacee Jason Fowler added a comment - Shame, most of HQ's devs are running Ubuntu 12.04 LTS, which is still at 5.3.X for PHP.
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Yeah, it's so hard:

            • 5.4: ppa:ondrej/php5-oldstable
            • 5.5: ppa:ondrej/php5

            http://askubuntu.com/questions/4983/what-are-ppas-and-how-do-i-use-them

            Ciao

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Yeah, it's so hard: 5.4: ppa:ondrej/php5-oldstable 5.5: ppa:ondrej/php5 http://askubuntu.com/questions/4983/what-are-ppas-and-how-do-i-use-them Ciao
            Hide
            phalacee Jason Fowler added a comment - - edited

            those PPA's aren't hot-swappable on 12.04.

            I did exactly that, and now have to reconfigure my machine completely - mysqli and pgsql have both broken.

            Show
            phalacee Jason Fowler added a comment - - edited those PPA's aren't hot-swappable on 12.04. I did exactly that, and now have to reconfigure my machine completely - mysqli and pgsql have both broken.
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Poor Jason, I'm afraid.

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Poor Jason, I'm afraid.
            Hide
            phalacee Jason Fowler added a comment -

            Turns out it was a conflict with the new apache 2.4 and mdk that caused all the issues.

            Show
            phalacee Jason Fowler added a comment - Turns out it was a conflict with the new apache 2.4 and mdk that caused all the issues.
            Hide
            dobedobedoh Andrew Nicols added a comment -

            Now that we have testing instrutions this passes.

            Thanks all.

            Show
            dobedobedoh Andrew Nicols added a comment - Now that we have testing instrutions this passes. Thanks all.
            Hide
            damyon Damyon Wiese added a comment -

            Twas the week before Christmas,
            And all though HQ
            Devs were scrambling to finish peer review.
            They sent all their issues,
            and rushed out the door -
            "To the beach!" someone heard them roar!

            This issue has been released upstream. Thanks!

            Show
            damyon Damyon Wiese added a comment - Twas the week before Christmas, And all though HQ Devs were scrambling to finish peer review. They sent all their issues, and rushed out the door - "To the beach!" someone heard them roar! This issue has been released upstream. Thanks!
            Hide
            killedar Manoj Killedar added a comment -

            Moodle should adopt following policies regarding minimum versions when releasing main Moodle versions like 2.7:

            1. PHP should be latest stable version of previous PHP version, that is, as on Jan 01, 2014, it is 5.4.23

            2. MySQL should be latest stable version of previous MySQLversion, that is, as on Jan 01, 2014, it is 5.5.35

            Show
            killedar Manoj Killedar added a comment - Moodle should adopt following policies regarding minimum versions when releasing main Moodle versions like 2.7: 1. PHP should be latest stable version of previous PHP version, that is, as on Jan 01, 2014, it is 5.4.23 2. MySQL should be latest stable version of previous MySQLversion, that is, as on Jan 01, 2014, it is 5.5.35
            Hide
            skodak Petr Skoda added a comment -

            Hello Manoj, that would be ok for Winwdows, but it would not work well for major Linux distributions. I was already considering having separate requirements for Windows, maybe in 2.8...

            Show
            skodak Petr Skoda added a comment - Hello Manoj, that would be ok for Winwdows, but it would not work well for major Linux distributions. I was already considering having separate requirements for Windows, maybe in 2.8...
            Hide
            dobedobedoh Andrew Nicols added a comment -

            Manoj Killedar, please consider contributing in the discussion forums as indicated in the URL field of this issue for further discussion.

            Although on the face of things, it may seem prudent to opt for the latest stable versions of things, many of our users run Linux distributions such as Ubuntu, Debian, RedHat, CentOS, SUSE, etc.
            Many of us chose to rely upon our distribution's packages which include security support for the version of the software that they package. These distributions do not include the latest release version all the time, instead they have policies which mean that once a version of that distribution has been released, they do not add new features - merely fix bugs and security issues.

            If we were to expect users to compile their own packages from source, this would leave them in a more vulnerable position as they would have to:

            • watch for security vulnerabilities on the various mailing lists;
            • understand the issues posed by these security vulnerabilities;
            • upgrade, recompile, and deploy.

            I know of relatively few people who actively follow all of the security mailing lists for all of the software that they run. Additionally, sometimes the DSAs can take a little while to understand and often are related to features that many of us do not use. Furthermore, many of our users are using shared hosting and simply do not have the option of upgrading every time a new version of PHP is released.
            Recompilation is also a fairly non-trivial task for many users.

            New versions also include new features, as well as new bugs. Most systems administrators would prefer stable with known (and hopefully reducing) bugs, over brand new with new issues to be determined.

            Changing to use the latest stable version of packages would exclude many people from using Moodle, and for very minor benefit to Moodle.

            I hope that this helps to explain some of our rationale,

            Andrew

            Show
            dobedobedoh Andrew Nicols added a comment - Manoj Killedar , please consider contributing in the discussion forums as indicated in the URL field of this issue for further discussion. Although on the face of things, it may seem prudent to opt for the latest stable versions of things, many of our users run Linux distributions such as Ubuntu, Debian, RedHat, CentOS, SUSE, etc. Many of us chose to rely upon our distribution's packages which include security support for the version of the software that they package. These distributions do not include the latest release version all the time, instead they have policies which mean that once a version of that distribution has been released, they do not add new features - merely fix bugs and security issues. If we were to expect users to compile their own packages from source, this would leave them in a more vulnerable position as they would have to: watch for security vulnerabilities on the various mailing lists; understand the issues posed by these security vulnerabilities; upgrade, recompile, and deploy. I know of relatively few people who actively follow all of the security mailing lists for all of the software that they run. Additionally, sometimes the DSAs can take a little while to understand and often are related to features that many of us do not use. Furthermore, many of our users are using shared hosting and simply do not have the option of upgrading every time a new version of PHP is released. Recompilation is also a fairly non-trivial task for many users. New versions also include new features, as well as new bugs. Most systems administrators would prefer stable with known (and hopefully reducing) bugs, over brand new with new issues to be determined. Changing to use the latest stable version of packages would exclude many people from using Moodle, and for very minor benefit to Moodle. I hope that this helps to explain some of our rationale, Andrew

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                19 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  13/Jan/14

                  Agile