BIND 10 #2221: Add verbosity=2 as an argument when running Python unittests

[BIND 10 Development]

#2221: Add verbosity=2 as an argument when running Python unittests
-------------------------------------+-------------------------------------
                   Reporter:  muks   |                 Owner:  UnAssigned
                       Type:         |                Status:  reviewing
  enhancement                        |             Milestone:
                   Priority:  low    |  Sprint-20120904
                  Component:         |            Resolution:
  Unclassified                       |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:1 muks]:
 > Up for review.
 >
 > Moving this to the current sprint with low priority; it's a trivial
 review and good to get in while it merges cleanly.

 While understandable, I don't think it a good idea to push it to the
 current sprint.  (in my understanding) an important point of the
 concept of a sprint is to eliminate or at least minimize distraction
 that is not directly related to the main focus of the development.
 So, in general, adding a non-planned ticket just because it happens to
 be done for some reason and would be good to be merged sooner.

 If we allow accepting non urgent, unrelated fixes/improvements that
 were not in the original plan as we happen to find them, they will
 themselves be distraction, and the fact that we accept them can be a
 bad precedent to allow yet another one.

 Besides, I guess you mean we take this ticket when we run out of open
 tickets at the end of the sprint by specifying lower priority.  But,
 considering our current situation where we need to do a lot of things
 toward the end of September, if we are good enough and actually run
 out of open tasks, what we should take next is IMO zone loading tasks.
 I don't think we can afford time for lower priority things for the
 moment.

 So, my suggestion is to push it to the next sprint queue, not the
 current one.  If we agree on the relative importance of this ticket,
 it will be accepted, and since it's already in the review queue, it's
 likely to be merged at an earlier stage in the next sprint.  It
 shouldn't be much different from pushing it to the current sprint,
 hoping it'll be taken at the end of the it.  On the other hand, we
 might find we really have no time to do any non urgent tasks at the
 next sprint planning meeting.  In that case we can save some (although
 maybe small) valuable time for higher priority tasks than reviewing
 this one.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2221#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development