-
Notifications
You must be signed in to change notification settings - Fork 56
Give it a try #27
Comments
@LeeSaferite @tmotyl @manish172 @davidwindell @sebastianwagner @drobinson @kalenjordan @sunel @empiricompany @rafaelstz @AydinHassan @emateu @t-richards @ToonSpin @sebastianwagner @bragento @davidverholen @Zifius @km-digitalpatrioten @daniel-rose @navarr @egon0 @flancer64 @adrien-louis-r |
I wonder if https://github.com/magento would consider providing an official mirror alongside the old SVN repo (especially considering the recent security attacks). |
Hey, This leads to automatically generated dev - Versions pointing to each branch |
@davidwindell no, they don't have resources to manage it, but it would be really nice. @davidverholen we can do this, I created #29 for it |
Good idea, and this is why the OpenMage/magento-lts was created. I would be really happy if Magento would take the pull requests we;re creating and incorporate them into the official version. Maybe @piotrekkaminski knows if this is something Magento has in plans? |
@tmotyl Firegento not bound to any company as well. It is association with a lot of active members, that organises a lot of hackathons in Germany. @benmarks is active member of those hackathons. OpenMage/magento-lts:
And each time you want update your magento you just need to run As for bugfixes I would recommend to have separate repo which could be used as magento-module and installed on top of magento. Thanks @SchumacherFM for this idea. |
Thanks @razbakov - will check this out next time I'm in security patch mode :) |
@razbakov LTS doesn't have the releases because each release from Magento gets a new branch - so definitions in composer.json like yours work exactly the same. But I agree...it would be great to have a central repo for community to agree on. |
That was the whole idea behind OpenMage in the first place. I'm always open to help there. |
Sounds greate to me 👍 As i know If this central repo idea could incorporate both offical and community fixes it would be great. |
I also vote for contributing to OpenMage instead of doing it as part of Firegento. And I mean for a Magento Mirror, *and for a fork which allows contributions. Firegento is a partially good known community brand (at least in the german speaking area). |
The openmage package seems broken on packagist.org. There is only one stable version (1.9.1.1) shown. https://packagist.org/packages/openmage/magento-lts Also we need a new version (or patch version) every time a new Patch is released, so magento is updated automatically for every customer. Another Problem is, that it requires the magento composer installer directly. You can only use this package (except you replace the installer in every project) if you are using the hackathon installer. Not everyone does this. Apart from this, it is unnecessary to require the installer in a core package since it does not support core install anymore. |
as the primary problem is the composer installer |
Let's give it a try to use one central repo for Magento:
Firegento Magento Community Magento-1.x Mirror Github Repository with Patches.
Follow instructions in README to install magento.
In case of any problems we will fix it ASAP.
Nowadays there are thousands of other magento-mirror-repos which are doing the same job every time when new patch or magento version is released. Here is just a small list of repos, which I know:
What if we bring our hands together and help each other to deliver security patches faster and with better quality?
The text was updated successfully, but these errors were encountered: