[development] The "postponed" issue status
Randy Fay
randy at randyfay.com
Thu Jun 3 21:49:10 UTC 2010
Here's a question for the group:
The "postponed" issue status, per http://drupal.org/node/156119, seems to be
either:
"We plan (maybe) to work on this later"
or
"We can't work on this yet because it's blocked by another issue"
To demonstrate this ambiguity, a search of "open
issues<http://drupal.org/project/issues/search/drupal?text=&assigned=&submitted=&participant=&status[]=Open&priorities[]=1&categories[]=bug&categories[]=task&version[]=156281&issue_tags_op=or&issue_tags=>"
does include "postponed". However, the "D7 critical
issues<http://drupal.org/project/issues/search/drupal?version[0]=156281&status[0]=1&status[1]=8&status[2]=13&status[3]=14&priorities[0]=1&categories[0]=bug&categories[1]=task>"
search does *not* include postponed issues.
Further, the "templates for issue transitions<http://drupal.org/node/467548>"
page (mostlly oriented toward module maintainers) clearly takes the former
"maybe we'll work on this later" attitude.
My questions:
1. Which of these interpretations of "postponed" is "correct"?
2. Should we add a "blocked" status that is quite clear?
-Randy
--
Randy Fay
Drupal Module and Site Development
randy at randyfay.com
+1 970.462.7450
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20100603/eb10d939/attachment.html
More information about the development
mailing list