[[ blog 이사 과정에서 정확한 posting날짜가 분실됨. 년도와 분기 정도는 맞지 않을까? ]]
In case that several branches are maintained at the same time, 'change list'(ex. bug fix) tends to be patched to several different code branches. General way to apply 'change list' is code-merge. In this case, the guy who merges 'change list' may not know enough about change. So, there should be information about checking patch result - to verify that patching is successful or not - as a comments of 'change list'.
One of good example is something like this.
* before patch : title string is "xxxx" in screen A.
* after patch : title stringis "yyyy" in screen B.
'Essay > Software' 카테고리의 다른 글
[Prog] Outputs should be separated from inputs at directory level. (0) | 2008.02.19 |
---|---|
[Dev] Let's make schedule-history-table! (0) | 2007.11.25 |
[Essay] Timezone이 다른 지역의 사람들과 같이 일할때... 이런 방법은 어떨까?? (0) | 2007.07.10 |
[Dev] 요약 [extream programming installed]. (0) | 2007.06.17 |
[Dev] XP에서 말하는 code branch 관리에 대한 의문점... (0) | 2007.06.15 |