how to handle multi-release of a project -


i have maintain 3 separate releases of project, (1) development (2) uat (3) production. each have separate db, servers, , machines.

project same 1 3 releases based on.

now best way handle below:

  1. do need 3 separate cvs repositories ?
  2. when applying fixes ? how maintain fixes , applying 1 one
  3. in long run, how keep them separate if issue appear on 1 place , should not effect others, or apply fix @ 1 place only.

thanks

if difference between these 3 environments in settings database servers or other configurations, can still keep code in same repository or branch easy maintenance.

instead, have having configuration file different settings different environments. example, practice or concept used in zend framework project.

application.ini

; production site configuration data [production] webhost                  = www.example.com database.adapter         = pdo_mysql database.params.host     = db.example.com database.params.username = dbuser database.params.password = secret database.params.dbname   = dbname  ; staging site configuration data inherits production , ; overrides values necessary [staging : production] database.params.host     = dev.example.com database.params.username = devuser database.params.password = devsecret 

Comments

Popular posts from this blog

blackberry 10 - how to add multiple markers on the google map just by url? -

php - guestbook returning database data to flash -

delphi - Dynamic file type icon -