Loading...
 

Tracker Item History

View Tracker Item

Version Date User Field ID Field Difference
10 2021-06-05 00:41 Marc Laporte 238 Resolution Status
9 2021-05-20 10:11 Marc Laporte 237 Also visible to
- +1- Visible to Anonymous (Public content)
8 2021-05-15 18:33 Marc Laporte 52 Task
-Tiki23beforebranching: Composer v2 +Tiki23beforebranching if easy, else very important for Tiki24: Composer v2
      55 Priority
-1 +3
      171 Related
-Review how Tiki uses Composer and Satis (with Jordi), Implement recommendations for Composer package version strategy, Make sh setup.sh call a PHP script that reverts Composer to HTTP was What is strategy for Composer to work for Macau?, Make an option console.php vcs:update to run composer without https, Decide if local change to Tiki, or global change to ClearOS was Composer cache write access (advice please) was: 18.x: Issues with composer environment, Scout the PHP ecosystem for opportunities, On hold: Method to test if all Composer dependencies are still being used in the code, Check everywhere where external scripts are called was Fix Composer itself instead of workaround: when the ENV variable HTTP_ACCEPT_ENCODING is passed to composer, there is some trailing (garbage) being return from the call, We are looking into an option to avoid need to set PATH in all crontabs was tiki.ocr.suite.wiki: composer dependencies were not updated by TRIM (but svn code was up to date), Further work on satis.json || was Done: Improve our use of asset-packagist, Review status of composer.tiki.org, Satis, and discuss its future, Twelve-factor app / Cloud Native modernization: An option to move vendor_bundled/ outside the root, Make console.php and Tiki Manager deal with package upgrades, Latest Tiki Manager: Warning: The lock file is not up to date with the latest changes in composer.json. , trunk abandoned packages, Useful on Windows: Add patch tool in Tiki in PHP (was Harmless error messages in trunk for webcron_type and adodb-php__remove_references_to_adodb_extension.patch) +Review how Tiki uses Composer and Satis (with Jordi), Implement recommendations for Composer package version strategy, Make sh setup.sh call a PHP script that reverts Composer to HTTP was What is strategy for Composer to work for Macau?, Make an option console.php vcs:update to run composer without https, Decide if local change to Tiki, or global change to ClearOS was Composer cache write access (advice please) was: 18.x: Issues with composer environment, Scout the PHP ecosystem for opportunities, On hold: Method to test if all Composer dependencies are still being used in the code, Check everywhere where external scripts are called was Fix Composer itself instead of workaround: when the ENV variable HTTP_ACCEPT_ENCODING is passed to composer, there is some trailing (garbage) being return from the call, We are looking into an option to avoid need to set PATH in all crontabs was tiki.ocr.suite.wiki: composer dependencies were not updated by TRIM (but svn code was up to date), Further work on satis.json || was Done: Improve our use of asset-packagist, Review status of composer.tiki.org, Satis, and discuss its future, Twelve-factor app / Cloud Native modernization: An option to move vendor_bundled/ outside the root, Make console.php and Tiki Manager deal with package upgrades, Latest Tiki Manager: Warning: The lock file is not up to date with the latest changes in composer.json. , trunk abandoned packages, Useful on Windows: Add patch tool in Tiki in PHP (was Harmless error messages in trunk for webcron_type and adodb-php__remove_references_to_adodb_extension.patch), Tiki23beforebranching: PSR-12, Tiki25: Tiki and PHP 8: We need Smarty 4
7 2021-04-28 19:20 Marc Laporte 52 Task
-Composer v2 +Tiki23beforebranching: Composer v2
      55 Priority
-3 +1
      169 Assigned by
      170 Keep informed
-guillaume.leclerc, jonny.bradley +guillaume.leclerc
      171 Related
-Review how Tiki uses Composer and Satis (with Jordi), Implement recommendations for Composer package version strategy, Make sh setup.sh call a PHP script that reverts Composer to HTTP was What is strategy for Composer to work for Macau?, Make an option console.php vcs:update to run composer without https, Decide if local change to Tiki, or global change to ClearOS was Composer cache write access (advice please) was: 18.x: Issues with composer environment, Scout the PHP ecosystem for opportunities, On hold: Method to test if all Composer dependencies are still being used in the code, Check everywhere where external scripts are called was Fix Composer itself instead of workaround: when the ENV variable HTTP_ACCEPT_ENCODING is passed to composer, there is some trailing (garbage) being return from the call, We are looking into an option to avoid need to set PATH in all crontabs was tiki.ocr.suite.wiki: composer dependencies were not updated by TRIM (but svn code was up to date), Further work on satis.json || was Done: Improve our use of asset-packagist, Review status of composer.tiki.org, Satis, and discuss its future, Twelve-factor app / Cloud Native modernization: An option to move vendor_bundled/ outside the root, Make console.php and Tiki Manager deal with package upgrades, Latest Tiki Manager: Warning: The lock file is not up to date with the latest changes in composer.json. , trunk abandoned packages +Review how Tiki uses Composer and Satis (with Jordi), Implement recommendations for Composer package version strategy, Make sh setup.sh call a PHP script that reverts Composer to HTTP was What is strategy for Composer to work for Macau?, Make an option console.php vcs:update to run composer without https, Decide if local change to Tiki, or global change to ClearOS was Composer cache write access (advice please) was: 18.x: Issues with composer environment, Scout the PHP ecosystem for opportunities, On hold: Method to test if all Composer dependencies are still being used in the code, Check everywhere where external scripts are called was Fix Composer itself instead of workaround: when the ENV variable HTTP_ACCEPT_ENCODING is passed to composer, there is some trailing (garbage) being return from the call, We are looking into an option to avoid need to set PATH in all crontabs was tiki.ocr.suite.wiki: composer dependencies were not updated by TRIM (but svn code was up to date), Further work on satis.json || was Done: Improve our use of asset-packagist, Review status of composer.tiki.org, Satis, and discuss its future, Twelve-factor app / Cloud Native modernization: An option to move vendor_bundled/ outside the root, Make console.php and Tiki Manager deal with package upgrades, Latest Tiki Manager: Warning: The lock file is not up to date with the latest changes in composer.json. , trunk abandoned packages, Useful on Windows: Add patch tool in Tiki in PHP (was Harmless error messages in trunk for webcron_type and adodb-php__remove_references_to_adodb_extension.patch)
6 2021-04-05 04:54 Marc Laporte 55 Priority
-2 +3
5 2021-03-15 20:47 Marc Laporte 55 Priority
-4 +2
      238 Resolution Status
4 2021-02-02 20:36 Marc Laporte 55 Priority
-3 +4
      238 Resolution Status
3 2020-07-29 10:02 ricardo.melo 133 Files
-+ 745da76d E54f 492f B260 B1c4c4045960
0056e355 F8b2 45ed A484 186f9fbd162a
2 2020-06-13 07:11 Marc Laporte 170 Keep informed
-guillaume.leclerc +guillaume.leclerc, jonny.bradley
      171 Related
-Review how Tiki uses Composer and Satis (with Jordi), Implement recommendations for Composer package version strategy, Make sh setup.sh call a PHP script that reverts Composer to HTTP was What is strategy for Composer to work for Macau?, Make an option console.php vcs:update to run composer without https, Decide if local change to Tiki, or global change to ClearOS was Composer cache write access (advice please) was: 18.x: Issues with composer environment, Scout the PHP ecosystem for opportunities, On hold: Method to test if all Composer dependencies are still being used in the code, Check everywhere where external scripts are called was Fix Composer itself instead of workaround: when the ENV variable HTTP_ACCEPT_ENCODING is passed to composer, there is some trailing (garbage) being return from the call, We are looking into an option to avoid need to set PATH in all crontabs was tiki.ocr.suite.wiki: composer dependencies were not updated by TRIM (but svn code was up to date), Further work on satis.json || was Done: Improve our use of asset-packagist, Review status of composer.tiki.org, Satis, and discuss its future, Twelve-factor app / Cloud Native modernization: An option to move vendor_bundled/ outside the root, Make console.php and Tiki Manager deal with package upgrades +Review how Tiki uses Composer and Satis (with Jordi), Implement recommendations for Composer package version strategy, Make sh setup.sh call a PHP script that reverts Composer to HTTP was What is strategy for Composer to work for Macau?, Make an option console.php vcs:update to run composer without https, Decide if local change to Tiki, or global change to ClearOS was Composer cache write access (advice please) was: 18.x: Issues with composer environment, Scout the PHP ecosystem for opportunities, On hold: Method to test if all Composer dependencies are still being used in the code, Check everywhere where external scripts are called was Fix Composer itself instead of workaround: when the ENV variable HTTP_ACCEPT_ENCODING is passed to composer, there is some trailing (garbage) being return from the call, We are looking into an option to avoid need to set PATH in all crontabs was tiki.ocr.suite.wiki: composer dependencies were not updated by TRIM (but svn code was up to date), Further work on satis.json || was Done: Improve our use of asset-packagist, Review status of composer.tiki.org, Satis, and discuss its future, Twelve-factor app / Cloud Native modernization: An option to move vendor_bundled/ outside the root, Make console.php and Tiki Manager deal with package upgrades, Latest Tiki Manager: Warning: The lock file is not up to date with the latest changes in composer.json. , trunk abandoned packages
1 2020-04-19 13:02 Marc Laporte 54 Description
 https://php.watch/articles/composer-2 https://php.watch/articles/composer-2
 +Please scope this to see if we should do now or later?
 +And approximate work load?
 +And are there any tradeoffs?
⌅