Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #9202 Make Tuleap compatible with PHP 5.6
    Infos
    #9202
    Thomas Gerbet (tgerbet)
    2017-12-04 13:53
    2016-05-27 08:55
    9488
    Details
    Make Tuleap compatible with PHP 5.6

    There is a dedicated Jenkins job that tracker PHP5.6 incompatibilities:

    Overall strategy

    • For development
      • Install php 5.6 in parallel and have nginx + fpm in front
    • For production
      • Install/keep tuleap standard on centos/rhel6
      • Have a package to install all scl php56 packages (even from the deps not installed)
      • Have nginx in front reverse proxy
      • Allow to switch from php 5.3 to php 5.6

    The goal would be to progressively move pieces from php 5.3 to php 5.6 (with crafted ngnix reverse proxy rules that either redirect to apache for not converted part or to fpm to get the latest and brightest)

    For RHEL/Centos7

    • Develop packages to only depends on SCLs and not install stock php

    Todo list

    • General
      • Replace fake php scripts (src/www/users, groups, wiki/uploads, ...) by real php scripts ✓
      • SOAP
      • Access to API page
      • REST explorer
    • SVN / CVS
      • viewvc wrapper (SVN plugin, SVN core & CVS)
      • SVN proxy
    • Git
      • gitphp wrapper
      • git http wrapper
    • Mediawiki
    • Backend scripts
    • Project web pages

     

    Other
    All
    Empty
    • [ ] enhancement
    • [x] internal improvement
    Empty
    Stage
    Empty
    Closed
    2017-12-04
    Attachments
    Empty
    References
    Referencing request #9202

    Artifact

    request #10074 Viewvc doesn't deal properly with folders with spaces
    rel #8983 8.16
    rel #9210 8.17
    request #9269 Can't create new mailing list
    request #9349 Wiki page can not be accessed via the document manager
    request #9765 Wiki escaping escape characters
    request #9796 Have a PHP 5.6 dev environment
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2017-12-04 13:53
    I think we can now close this meta-request about PHP 5.6. All new instances are running PHP 5.6 by default. Remaining issues are bugs that must be fixed but it's not really part of the migration process now that we have live instances using it.
    • Status changed from Under implementation to Closed
    • Close date set to 2017-12-04
    User avatar
    Manuel Vacelet (vaceletm)2017-01-31 09:34
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2017-01-31 09:13
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2017-01-26 14:37
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2017-01-26 14:36
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Yannis ROSSETTO (rossettoy)2017-01-02 10:13
    On the PHP 5.6 dev environment, viewvc (SVN core, SVN plugin and I suppose on CVS too) is not working.
    User avatar
    Thomas Gerbet (tgerbet)2016-11-03 15:56
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2016-11-03 11:58
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2016-05-30 12:46
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes