| |||||||||||||
Controvery over commit stylesControvery over commit stylesPosted May 29, 2010 3:20 UTC (Sat) by giraffedata (subscriber, #1954)In reply to: Controvery over commit styles by epa Parent article: Interesting times for Linux Flash support
Isn't the point of "commit early and often" to get your code in front of everybody? Using a distributed version control system does that only insignificantly better than just keeping it in your CVS working directory. (Better, I guess, because someone sufficiently motivated could see your work early). Breaking things for everybody is the acknowledged downside of commit early and often. Obviously, there's a difference of opinion in this project over whether the upside outweighs that. Automated test suites that are part of a quality control strategy don't seem to me consistent with commit early and often, which admits that the code is going to be broken a lot.
(Log in to post comments)
Controvery over commit styles Posted Jun 1, 2010 16:17 UTC (Tue) by epa (subscriber, #39769) [Link]
Well, there's the distributed side, and there's the 'make branches and merge them without going insane' side. If your version control system supports easy branching and merging, you can commit your stuff to an unstable branch or a personal work branch, where they are visible to everyone but don't break things for others until you're ready to push them to the main branch.
|
|||||||||||||