Timeline for Method for integrating various version control systems or choosing one over others, due to mergers and acquisitions?
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2010 at 10:15 | history | edited | barjak | CC BY-SA 2.5 |
edit on dependencies management
|
| Dec 7, 2010 at 14:58 | comment | added | therobyouknow | PS. +1 Lucky you, barjak, for being in an organisation that tolerates a varied computing environment. | |
| Dec 7, 2010 at 14:57 | comment | added | therobyouknow | Need for integrating different systems ? Yes if the work of one team is used by another team. The integration can be tight or lose depending on the level of necessity and staff resource available. No if the projects are completely independent. The only remaining concern is supporting more than one system and whether that is perceived to be a good or a bad thing. Good if we accept that we live in a varied computing world or bad if we think that we should focus and show decisiveness for their own sakes, by choosing one tool itself that might be overly solipstistic! | |
| Dec 7, 2010 at 13:38 | history | answered | barjak | CC BY-SA 2.5 |