From webchick's original post:
It's great when we get newly injected energy into usability efforts in Drupal, as happened with the Drupal Usability Study at Google last week. However, these patches always run aground of various "freezes" we put in place in the stable release of Drupal:
- API freeze
- Don't commit patches that break backwards API compatibility within a stable release, for the benefit of contributed module and theme authors.
- String freeze
- Don't change any user-facing text (e.g. anything in a t() function), for the benefit of translation teams.
- UI freeze
- Don't commit patches that affect the user interface, for the benefit of the documentation team, as well as to not invalidate tutorials, screencasts, books, etc.
- Feature freeze
- Don't commit patches that add new features; stick only to bug fixes. Additional functionality gets added in contrib.
Read the full discussion and comment!
Read »
