- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
We added 10 pull requests to the community dashboard this month for processing, based on the votes on the PRs.
Thank you to all the community members who voted!
Community Prioritization Process is an initiative to empower the community to influence the Magento Open Source roadmap and codebase by upvoting the pull requests that brings most value to them. Adobe then picks the most up voted Pull Requests and adds them to the community dashboard to work on, with a purple label - “Project:Community Picked".
Here is the combined status of the pull requests worked on so far.
Total: 51
Functionalities that made into the code base this month:
- Fix potentially corrupt merged CSS files. magento/magento2#29173
- Replace {YYYY} in the copyright line by the current year magento/magento2#36754
- Change selected identifier magento/magento2#25627
- Enforce array type in DesignTheme config processor magento/magento2#34092
- magento/magento2#35881: Final Price for grouped products does not include tax in the Recently Viewed...
Ready to be merged:
- magento/magento2#35906 GraphQL Routes query with fragments has issue in the category page #35906 #36...
- Fix Call to a member function getId() on int #36769
- magento/magento2#33010: Sort of related products in GraphQL not implemented #36462
The ones that are ready to be merged are at the top of the merge queue and are expected to be in by next week.
For real time status, please visit the community dashboard.
Thank you to everyone who contributed to voting, coding, reviewing, testing, and merging of these enhancements and improvements.
How to get involved in the process:
- You can vote on your favorite PRs in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository - https://github.com/magento/magento2/pulls
- If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.
- Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources.
If you missed our earlier updates on community prioritization process, please visit the DevBlog. You could also follow #commercecommunitymonthly on LinkedIn to view the monthly community newsletter that has a permanent section to share update on this process.
We will be ready to pick the next batch soon.
Thank you for your engagement and contribution to the Magento Open Source community!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.