I believe this to be a good change and agree with it. However, normally
such changes should be discussed in the relevant issue queue before
being made. A note to this list telling people about the discussion
early on is a good courtesy.
--Larry Garfield
On 1/11/11 5:59 AM, Steven Jones wrote:
Hello Drupal developers,
With automated testing, Drupal 7 has had the policy that a failing
test would be a sufficient condition for the related issue to be
marked as 'critical'. This was according to the handbook page that
describes the meaning of the issue priorities:
http://drupal.org/node/45111
However, this was not true. Drupal 7 was released with several tests
that failed, but only in the secondary testing environments notably:
PostgreSQL and SQLite on Linux. They passed in the primary testing
environment of MySQL + Linux.
I think that this is fair, but a failing test should still be given a
higher priority that other issues, so I've updated the aforementioned
handbook page so that failing tests in the secondary environments are
'Major' issues.
I've basically changed this because it makes sense to me, and because
changes to the handbook are really easy to revert. Was this the right
change to make?
Regards
Steven Jones
ComputerMinds ltd - Perfect Drupal Websites
Phone : 024 7666 7277
Mobile : 07702 131 576
Twitter : darthsteven
http://www.computerminds.co.uk
