![]() The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed. Note: Change records used to be called change notifications. Needs change recordĪ change record needs to be drafted before an issue is committed. See the scope of responsibilities for product managers. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. ![]() Make sure the issue summary describes the problem and the proposed solution. When adding this tag, make it easy to review the issue. ![]() ![]() Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |