The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.
By tvn on
D7 upgrade stats this week: 56 open issues out of 236 total! In other words: 76,3% fixed and 23,7% to go. Test stats also look much better. 827 documented and automated scenarios for Drupal.org. 74,3% of them are passing. Visibility is around 88%, which means that roughly 12% of the steps are being skipped because they follow a step failure.
On the automated testing front, PIFT has been upgraded to Drupal 7, having required a significant rewrite due to interdependencies with the revamped Project Issue module. Initial validation of the issue queue integration is complete. Validation of commit-triggered tests is expected to wrap up this week, after which the PIFT cron runs will be turned on and the staging site will be fully test-enabled on the qa.d.o staging environment; allowing users to test the new patch workflow in its entirety.
Help with development
Conflict is a module we created to help make simultaneous node edits less painful. We’re using it for issues. To make it more useful, highlight modified and conflicting fields during conflict resolution needs a developer. The module has a handful of other open issues, including needing tests.
Project issue tracking’s issues are dwindling. A good self-contained issue to work on is Port per-project default component setting to D7.
As always, we’d like to say thanks to all volunteers who are working with us and to the Drupal Association Supporting Partners, who made it possible for us to continue the upgrade project. The Supporting Partner Program crowd sources funds that pay for the development team’s time and Drupal.org hosting costs.
File attachments:
Comments
Is there a test site? I know the UI is seriously overhauled, have this been tested with contributors?
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
Test site url: http://git7site.devdrupal.org/
Use drupal/drupal to access it and your usual username/password to login.
Jibran gave the correct url to our staging site.
While working on the issue page UI changes we did solicit feedback from a number of active core contributors and UX team members, who helped a lot. We also asked wider community to test the new UI in this blog post awhile back: https://association.drupal.org/node/17983 and got a lot of feedback.
At that point only general issue page UI and file uploads were available for testing, because PIFT has not been ported yet. As mentioned in this week notes, we expect to finish PIFT-related work next week and full patch workflow will be available for testing. Of course we will additionally announce that.
Is there a way those of us that use Drupal.org on a daily basis can test out how things are working with the port to D7 and can provide constructive feedback?
As a part of our QA process, we will open our staging site for a wide community testing and provide details on how/where to file issues. We are close to that, but not quite ready yet. There will be a separate announcement with instructions.
If you are eager to start right now though, feel free to look around: http://git7site.devdrupal.org/ (drupal/drupal and usual D.o username and password).
Here is a queue where you can provide feedback: https://drupal.org/project/drupalorg-site-upgrade-qa
Is there somewhere that I can help? I opened an issue quite a long time ago, and IMO, it's critical that it's fixed before the D7 version of the site is released: https://drupal.org/node/1991500
I saw this comment of yours, and that's exactly how you can help. Thanks a lot!
Can help with testing. not sure how to get started.
Shyamala
http://www.unimitysolutions.com
Thanks a lot Shyamala, we'll definitely let you know when staging site is ready for community testing. Do you have any interest in BDD testing - test writing and test maintenance? That's another area where we could use some help.