Changes between Version 3 and Version 4 of ACKSystemReview


Ignore:
Timestamp:
03/27/12 13:44:45 (8 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ACKSystemReview

    v3 v4  
    3636 * [http://en.wikipedia.org/wiki/Static_testing Static testing] (code-ACKs)
    3737
     38== Limitations ==
     39
    3840There are limits to what the ACK process can do. For example:
    3941
    4042 * Runtime errors may be very difficult to notice
    4143 * Seeing the "big picture" may be difficult, especially with big patchsets
     44 * Whether a particular problems is noticed depends highly on the reviewer's skills
    4245
    4346== Cons ==
    4447
    45 By it's nature, requiring an ACK slows down flow of code from contributors to the "master" development tree. This problem gets worse as the patchset size increases.
     48The ACK/NACK process has it's cons:
     49
     50 * Requiring an ACK slows down flow of code from contributors to the "master" development tree. This problem gets worse as the patchset size increases.
     51 * Due to the above, it takes longer to get the code into wide circulation. This means bugs are reported later than if the code had been merged as soon as it's ready.
     52
     53= Raw data =
     54
     55= Analysis =