-
-
Notifications
You must be signed in to change notification settings - Fork 437
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
Documentation Around Version Numbers #985
Comments
Hi, Yes I think it needs updating as didn't work for me either. Using "19.4.x" (which took from the further instructions link) did and I'm now on version 1.9.4.5 from Magento's point of view. I've created a pull request #992 to amend the README.md which hopefully is correct and will get accepted if so. Thanks, Ed |
Agree, there's the need for a more clear documentation about the versioning. |
1st
2nd
Actually working on this ... |
* Updated README.md, closes #992 - add branch alias to composer.json (see #992#issuecomment-638974892) - add AFL 3.0 license - removed duplicate LICENSE.html - ... * Renamed dev-master to dev-main * Renamed dev-master to dev-main - missed one * Added event #1168 Co-authored-by: Sven Reichel <sven.reichel@sandstein.de>
I believe some clarity around this would be good. For example, I read that 19.4.1 should be used as per here.
However, when I place that on top of my magento code (just a zip file download and a copy over), in the admin panel I get Magento ver. 1.9.4.4.
If I go to the github repo and just do git clone https://github.com/OpenMage/magento-lts.git then copy the files over I get Magento ver. 1.9.4.5
I never see anything like 19.4.1. Worse off, when I git clone https://github.com/OpenMage/magento-lts.git I got commits from today. I was under the assumption that a LTS version should have released versions and not just pull in all of the latest commits.
My recommendations here are as follows:
Maybe I am just confused, or perhaps this will confuse others as well.
Thanks!
The text was updated successfully, but these errors were encountered: