Changes between Version 3 and Version 4 of ACKSystemReview
- Timestamp:
- 03/27/12 13:44:45 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ACKSystemReview
v3 v4 36 36 * [http://en.wikipedia.org/wiki/Static_testing Static testing] (code-ACKs) 37 37 38 == Limitations == 39 38 40 There are limits to what the ACK process can do. For example: 39 41 40 42 * Runtime errors may be very difficult to notice 41 43 * 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 42 45 43 46 == Cons == 44 47 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. 48 The 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 =