-
-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace lib/Zend with shardj/zf1-future 🚀 #2827
Conversation
I'd have loved to modify my PR instead of a new one since I held this topic very dear. Anyway it is an amazing job, I only have a question, do you like the "patches" folder in the root folder? wouldn't it be possible to hide it somewhere else? like in a ".patches" folder or something like that? It's a very minor thing but now files/folders in root make me itchy :-D |
Thank you Sven for your work, an important step in OM future. Please let me know what files will remain in the /app/code/core (I did not implement locally this PR). In my test only a few files created trouble after deleting, especially those related to database operations. |
conflict with the baseline (isn't this a new thing) |
applying the patches doesn't seem to work correctly, using -vvv I was able to see this
|
I would still move the patches directory to another place if possible |
Its
This is strange. It works for me ...
Guess it comes from #2823. And we made some changest to Zend files too. |
I'm using php7.3 and composer 2.4.4, removed vendor completely before running the install |
PHP7.3 and composer 2.4.2. I think the problem is that Date.php is patched three times causing |
@fballiano can you do a quick test please ...
|
I modified patches/MAG-1.1.1.patch to
but it seems not to work:
|
Y 😂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's take this important step. There may still be issues but we can solve them as soon as they appear.
ouuu nouuuu we've a conflict with the freaking baseline, I was that excited to hit the "merge" button! |
There is another one that I approved in the last hour with the same problem. |
# Conflicts: # phpstan.dist.baseline.neon
OMG I can't believe we did it 😍 |
Unfortunately, OM 20 is still waiting behind version 19, with a gap of many commits. We should reverse the priority from 2023 and this version 20 should receive all the attention. OM 19 also goes ahead, but it will only collect certain commits from the default version. When I clone this repository to have the possibility to get an OM 20 up to date, not to wait for it to be updated from time to time. I think that it would make the work easier for the maintainers as well. |
as I said many times, we should stop working on v19 and work only on v20. have a single default branch which is v20 and that's it. v19 should receive only security updates if extremely necessary. we do not have the manpower to maintain 2 branches and develop something that's also interesting and fun for us to do (which is also very important). |
I support your point of view. v19 must pick from v20 not the other way around. the decision must be taken as soon as possible. Related to this PR all that remains is to intensively test the new ZF-1 version with OM. I did not get any issues after 2 weeks. It is incredible to see now only two files in /app/code/core/Zend and a brand new /lib/Zend with all updates inside. If I remember in my tests I had to keep those two files because OM stopped working if I renamed them. Indeed it's really a huge update for this project. There is nothing to say more. Many thanks to everyone involved and happy holidays. This year there have been many changes like PHP 8.1, ZF1-Future and many others. We still have problems with the management of reported issues and PRs, there are too many, but if we compare with what it was at the beginning of the year I can say that we are on the right track. |
I still prefer v19 over v20. What are the major changes?
However ... let not dicuss this here. |
The directory /lib/Zend no longer exists in our repository in any branch. Do you think that for those who do not use Composer we should inform them in the Readme that they can download the archive from ZF1-Future and add it themselves to /lib/Zend? If they don't do this they won't run OM anymore. |
we've to inform them that they have to remove lib/Zend, the release builder will already have the right components in the vendor folder ;-) |
and I'd also bump the version to 20.1.0 and 19.5.0 at least, since this change is pretty massive |
README should be updated. Have have to tell how to make changes to vendor/zf1f (adding patches) and about change requirements. E.g. |
I'll do that ASAP |
Nice. My PRs got merged, so we can removes some patch files with next release :) |
Description (*)
This PR replaces
lib/Zend
with shardj/zf1-future.All changes made to
lib/Zend
orapp/code/core/Zend
have been replaced with patches. There are only two files left inapp/code/core/Zend
that needs reviews./app/code/core/Zend/Db/Select.php
/app/code/core/Zend/Db/Statement.php
Applied patches: #2787 (comment) & #2787 (comment)
Related Pull Requests
Comments
Contribution checklist (*)