Application Versioning

[dwighty]

Hi guys,
this is a bit of a broad question but was just wandering a) if anyone does this and b) any recommendations as to how to do it
_________________________
The idea:

There is a web application (for example: project management), this app is only used a clients and not open to the general public to register a free account.
Different clients are at different stages of development so require different versions of the application.

for example:
Client A has been a client for 4 years and their requirements are such that they do not need the latest version of the application.
Client B is a new client who needs a full indepth/latest version of the app.
__________________________

There are going to be some files that do not change with a new release of the version, take for example the login file. So I do not really want to have different directorys for different versions.

1 solution i though of was to have a different config file for each major version of the app. This config file then includes the required version of that page.

Is there any other way of doing this?

[phranque]

you might look into using cvs or similar configuration management/version control system.

[ashishp]

The problem with not using a versioning system and thinking that you might simply not include the new version function definitions/classes for the older site, is that you have to be worrying if the function exists in all your scripts and compensate or skip that functionality.

Using a versioning system will give you the benefits of having two (or more) application environments running with the ability to switch them when you wish.

Many people recommend Subversion (SVN) to maintain your project, havent used it yet but am busy reading up on it.

O'reilly has a book too!

HTH

[dwighty]

Thanks for this. will look into it a bit more.