Timeline for How to manage/control software versions? [duplicate]
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2014 at 16:41 | review | Reopen votes | |||
| Mar 15, 2014 at 17:16 | |||||
| Apr 8, 2013 at 14:32 | history | closed | gnat CommunityBot Bart van Ingen Schenau Jalayn Bill | exact duplicate | |
| Apr 8, 2013 at 13:59 | comment | added | Caleb | It sounds like your task is to manage the actual binaries rather than source code. In that case, you should search for information about configuration management instead of or in addition to version control. | |
| Apr 8, 2013 at 13:56 | review | Close votes | |||
| Apr 8, 2013 at 14:32 | |||||
| Sep 24, 2012 at 7:27 | comment | added | Zwie | Simplified: We provide an interface for webbased fameworks, which they implement in various modules. Since the version nr haven't been published yet, the customers implemented different versions without knowing - depending on the specification they got from us. Until now, there is no EOL - even the 10 year old versions are supported... I've to create (and further manage) a version overview, so that we hopefully can communicate the versions to the customers and set some EOLs. | |
| Sep 23, 2012 at 12:01 | history | tweeted | twitter.com/#!/StackProgrammer/status/249840893333471233 | ||
| Sep 21, 2012 at 15:09 | comment | added | Doc Brown | What means "external" to you? Software of your customers? Do you really know what software they have written using your modules? What kind of "interfaces" exist for external use, and how stable are they? What life cycle does your software have? Does your customer contract even allow to change that interfaces? Do your write about desktop software, mobile, server modules, games, web software? I don't get the picture because of so many missing pieces of information. | |
| Sep 21, 2012 at 14:03 | comment | added | Zwie | We are already using a VCS in our company. The goal is to match intern known versions with external software modules depending on our system and communicate this (some time in the future) to the customer. Doing this, we hope to get ride of some older and still used interfaces. - I'll inform myself a bit more configuration management, thank you for the hint. | |
| Sep 21, 2012 at 13:29 | answer | added | rmac | timeline score: 6 | |
| Sep 21, 2012 at 13:19 | history | edited | Ryathal | CC BY-SA 3.0 | added 8 characters in body |
| Sep 21, 2012 at 13:16 | answer | added | GlenPeterson | timeline score: 1 | |
| Sep 21, 2012 at 13:15 | comment | added | Ryathal | searching configuration management might help lead you to some useful things | |
| Sep 21, 2012 at 13:15 | comment | added | Doc Brown | What is your aim? Writing a paper about how to use a specific VCS in your company? Or document which versions of your software parts exists and which ones are compatible (which has not much to do with version-control, that's a more general thing called "configuration management"). Please clarify! | |
| Sep 21, 2012 at 13:14 | answer | added | Patkos Csaba | timeline score: 3 | |
| Sep 21, 2012 at 13:07 | history | edited | yannis | CC BY-SA 3.0 | deleted 23 characters in body |
| Sep 21, 2012 at 12:58 | review | First posts | |||
| Sep 23, 2012 at 17:43 | |||||
| Sep 21, 2012 at 12:57 | history | asked | Zwie | CC BY-SA 3.0 |