new or upgrade the old??

[sach0111]

lets say we have an existing software with version 1.0. if this is upgraded to 1.2, then do we create a new CI or just replace the older one??

[Ed]

The simple answer is create a new CI - otherwise the potential for losing the functionality of the software is huge. Essentially they are different beasts- similar, but not the same.

After all you wouldn't class 'Windows for Workgroups' as the same as XP and one is only an upgrade of the other (Acording to Microsoft)

Regards

Ed

[Guerino1]

Sach0111,

This depends on your versioning implementation. For software, the answer is "Both" depending on how your versioning mechanism works. There are versioning solutions that will always create a totally new CI when you check one out and then check it back in. There are versioning solutions that work based on overlaying "delta differences" over the source code control repository. It also depends on what previous Release and it's state (environment and Changes) you baseline your new Release off of.

For hardware and infrastructure, it simply depends on what is being replaced or modified.

For SW, which is what your original question was about, we "always" create completely new CIs and manage them going forward. Whenever we create a new Release trunk, we create a new Release repository in the Definitive Software Library (DSL) and baseline (replicate) Changes and their files from a previous Release, in a specific environment, into the new Release, specifically into the Common Development Environment, which is the place all Changes and their modified source code will be merged into for common builds, before the Changes moves on to other testing environments.

I hope this helps.

Regards,
_________________
[Edited by Admin to remove link]

[sach0111]

Thanks for the replies guys!!!