Skip to content

Added a discussion entry #65

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 29, 2013
Merged

Added a discussion entry #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions Milestone/2/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,4 @@ bragento: You shouldn't exclude Magento 1 in any case. The community is just emb
Even when customers start switching to Magento 2, some customers won't be willing to do so anytime soon. As we are working towards standartizing our deployment processes throughout all releases, we would much appreciate to keep the same (or at least a simmilar) workflow.
Of course you could always start working on a magento2-composer-installer whilst sharing parts of the package with the magento1 version and optimizing other parts for Magento 2.




maderlock: I'm with avstudnitz. There are parts of the current integration that I like more than option 3 even if given a free choice. For exampkle, having symlinks into the code folders lets me see at a glance what is installed, and those of my team less used to composer can work more or less as they used to. I have therefore not voted, as my vote would be for option 4: continue support of version 1 in a similar vein to at present.