Timeline for Extreme Programming Daily Commits
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2013 at 12:58 | comment | added | sleske | @Ingo: "You bet what happens next monday: desperate users calling help desk, ..." How can this happen? Do you deploy a freshly committed version to production without any testing? With appropriate code review, branches and CI this should not be a problem. | |
| Mar 9, 2013 at 5:37 | comment | added | Carson63000 | Well said, I've always taken the philosophy of daily commits as meaning "don't work all day on something without at least one commit", not as "commit right before you down tools at the end of the day". | |
| Mar 9, 2013 at 5:09 | comment | added | Eric King | I agree with this sentiment. Time of day should have nothing to do with when you commit your code. You commit whenever you have added a working subset of code, and you want to save your progress and move on. If that happens to be at the end of the day, so be it, but you should have been committing your code throughout the day to begin with. | |
| Mar 8, 2013 at 23:22 | comment | added | Ingo | I know people that do interface changes friday afternoon in the middleware, then leave for 3 weeks holiday. You bet what happens next monday: desperate users calling help desk, nobody knows what's happening, .... | |
| Mar 8, 2013 at 22:10 | history | answered | ZeroOne | CC BY-SA 3.0 |