Addison

I agree @colinmollenhour. This project really needs improvements not only bug & security fixes. A project dies when there is a lack of enthusiasm. Magento 1 has received a special...

Being an important PR that aims at several hundred changes must be analyzed in all aspects before being merged in OM 20. For a strict change in OM I'm not...

When there are so many changes involving dozens and even hundreds of files I think it would be best to break them into several PRs. I don't always have the...

This was the output for the ```composer install``` command before the changes in this PR:  This is the output for ```composer install``` command after the changes were merged: ...

My Linux distribution that I currently use in testing is Debian 10, but here I was asked to do a remote installation of OM + XAMPP + Phpstorm + Composer...

@fballiano - good observation. In my case PHP version installed by XAMPP is 8.1.6. Another condition to be evaluated and which creates confusion. We changed the minimum PHP requirement to...

I first ran with composer.lock from the repo, but when I saw that an error appeared, I brought the whole directory to the previous stage then I deleted composer.lock. Unfortunately...

On my Windows installation, look what happens when I run ```composer install --no-dev``` (without the file composer.lock existing in the directory). 

The arguments brought by @sreichel are pertinent. The current composer.lock is a file created by Composer and contains particularities that may not be found in the configuration of the system...

The latest version of composer.lock has already been merged yesterday into OM via PR #2378. It was generated in Ubuntu 22.04 with PHP 8.1.2 installed. Therefore, the file will remain...