Skip to content
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

Jump to bottom

Working demo project as an equivalent for developers #537

Closed
12th opened this issue Mar 30, 2014 · 5 comments
Closed

Working demo project as an equivalent for developers #537

12th opened this issue Mar 30, 2014 · 5 comments
Assignees
@piotrekkaminski
Labels
feature request Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@12th
Copy link

12th commented Mar 30, 2014

It would be good to check with the latest release from the working demo project. For example, the release was issued, the developer downloaded it and started testing it is not correct work and in this case it would be good to have a platform from which to verify functionality.
@Zifius
Copy link
Member

Zifius commented Mar 30, 2014

How about https://github.com/rgranadino/mage2_vagrant?

@verklov verklov self-assigned this Apr 1, 2014
@verklov
Copy link
Contributor

verklov commented Apr 2, 2014

@12th, we did not have a release version of Magento 2 so far. The releases we are doing every week are just a weekly update of the development version. Once we have a release version, we will consider having it on the GitHub as a demo project. So far, we created a ticket and placed it to the product backlog.

@vpelipenko
Copy link
Contributor

Internal ticket: MAGETWO-23174

@vpelipenko vpelipenko added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Mar 18, 2015
vpelipenko added a commit that referenced this issue Sep 3, 2015
@vpelipenko
Merge pull request #537 from magento-south/beta_fixes
30b2e3b 
[South] Merchant Beta Fixes
magento-team pushed a commit that referenced this issue Apr 12, 2016
@slavvka
Merge pull request #537 from magento-tango/MAGETWO-51827
f53c16c 
[Tango] Bugfixes
@piotrekkaminski
Copy link
Contributor

We are currently considering providing a default development environment image that would help with such use case. Currently it is recommended to have a local installation and git pull the latest code (only for contributing/core development purposes, end users should use composer or ZIP download).

@piotrekkaminski
Copy link
Contributor

Thank you for your submission.

We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues.

Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here).

We are closing this GitHub ticket and have moved your request to the new forum.

okorshenko pushed a commit that referenced this issue Dec 14, 2016
Merge pull request #537 from magento-okapis/MAGETWO-58205-google_wron…
8ccf7fa 
…g_request_params_2.0.x

Fixed issue:
 - MAGETWO-58205:  GoogleOptimizer wrong request parameters
magento-engcom-team added a commit that referenced this issue Jun 19, 2019
@magento-engcom-team
ENGCOM-5284: GraphQl-662: Test coverage of USPS shipping method #537
45153b7 
 - Merge Pull Request magento/graphql-ce#537 from magento/graphql-ce:282-shipping-methods-USPS
 - Merged commits:
   1. 7cf77bc
   2. 93881ed
   3. f028f81
   4. b34f173
   5. e7139c9
   6. 797211c
   7. ec36220
   8. cb22adf
   9. 5cd5f04
   10. 3b5096c
   11. 94a8c40
   12. eccc7e7
   13. 26354f6
   14. 8e4ffb4
   15. 8edb9d3
   16. 682f361
   17. 23ab51c
magento-devops-reposync-svc pushed a commit that referenced this issue Jun 13, 2023
@andimov
Merge pull request #537 from magento-performance/ACPT-1324
42f0226 
ACPT-1324: Fix CatalogCustomer GraphQl tests on MTS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@piotrekkaminski piotrekkaminski

Labels
feature request Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Zifius @maksek @piotrekkaminski @12th @verklov @vpelipenko