On Monday 30 March 2009, Sebastian Kuzminsky wrote: > play around in your own sandbox, building up and tearing down stuff, > testing things, all outside the attention of other developers.
Scenario 1 - Each developer runs their own VCS outside of Sourceforge adding "features", fixing bugs and generally rehashing code. Result: Little, if any real testing takes place, and when it gets committed to the "real" repository, massive conflicts arise as everyone else attempts to cherry pick. The change log gets consigned to the bin and future reviews will miss out on the development history. Due to the prospect of dealing with conflicts, the GeeWhiz features get consigned to the CBA pile. Meanwhile, the cvs-commit list & CIA gets flooded with multiple messages triggered by a single commit - Smacks of a badly configured server. Scenario 2 - Each developer runs their own branch rehashing stuff, adding "features" and fixing bugs. Result: So many branches on the go, little, if any real testing takes place. Merging changes in to trunk turns in to a major headache and other branches end up being irrelevant so stuff gets consigned to the CBA pile. Scenario 3 - Features get worked in trunk and potential breakages are resolved at an early stage. Result: Fewer resources are wasted chasing bugs, icky code has the potential to be weeded out at an earlier stage and conflicts are resolved before they become an issue. > When you have something that's pretty good and ready for wider review and > testing, *then* you merge it into the main line. If only... ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
