Re: Cleaning source code repositories

2015-02-15 Thread Viktor Sadovnikov
Hi Curtis, Yes, I believe, we are concerned about the same challenges, however with slightly different approach. I'm trying to come with a recipe or recipes for: - determining impact of introduction of a backward incompatible change; - determining delivered (released) versions of

Cleaning source code repositories

2015-02-13 Thread Viktor Sadovnikov
Good day, I wonder if this community can provide some hints on handling the following. At a few last projects I was asked to set (or clean) automated builds up, so they can get (at least) deployable software package(s) after code changes in a minimum time. Starting from the final desirable

Re: Cleaning source code repositories

2015-02-13 Thread Curtis Rueden
Hi Viktor, Do you actually consider this situation as a problem or is it just a perfectionist talking to me? ;-) I would say it is a very real challenge of managing projects with many components. how would you approach determining those, which are required for final deliveries, and those,

Re: Cleaning source code repositories

2015-02-13 Thread Viktor Sadovnikov
Hi Curtis, Thank you very much for your thoughtful reply. I'll review your links... very curious Thanks, Viktor --- Sent on go On 13/2/2015, at 17:33, Curtis Rueden ctrue...@wisc.edu wrote: Hi Viktor, Do you actually consider this situation as a problem or is it just a perfectionist