Timeline for DVCS and different versions of the same Product
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2012 at 20:48 | comment | added | William Payne | @Macniel: I strongly agree with everything that you have said so far. Furthermore, I believe in the notion that development cost control & cost amortization through software reuse needs to be explicitly factored in to the organization's management and financial structure through the use of product line centric organizational structures. I also believe that the structure of the source document repository used by the organization is a quick and easy way to communicate organizational structures and axes of reuse. This is largely an extension of Conway's law. | |
| Jun 7, 2012 at 19:42 | comment | added | Macneil | @WilliamPayne: It's an alternative to the problem posed. (I would not recommend using version control for the above purpose. If you were to, however, a DVCS like Teamware/Hg/Git is the way to go.) | |
| May 30, 2012 at 22:58 | comment | added | William Payne | Does this actually answer the question? (Not that I am disagreeing with anything that you have said, mind you). | |
| Dec 24, 2010 at 7:09 | vote | accept | Nikos Steiakakis | ||
| Dec 24, 2010 at 7:09 | comment | added | Nikos Steiakakis | I really like the Product Line approach because this is mostly what we need, and as most answers prove, the choice of version control is irrelevant. Perhaps I was thinking more in terms of Developer A working on the main core, whilst developer b works on the feature of the Pro version and having the changes merged etc. But that does not have to do with the version control model. | |
| Dec 23, 2010 at 17:36 | history | answered | Macneil | CC BY-SA 2.5 |