[rt-users] Change control

[Michael Erana]

I'd venture that a good backup and then perhaps comitting the sql backup into Subversion or CVS is one way to control those elements. In practice we normally commit the production base install for the files and also our local customizations into Subversion for control and tracking. No reason why you couldn't script a regular dump of the relevant tables and then commit those to one of the branches...

Michael Eraña, CISSP
CTO
PC Network, Inc.          


 

|=> -----Original Message-----
|=> From: rt-users-bounces at lists.bestpractical.com 
|=> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf 
|=> Of Chuck Boeheim
|=> Sent: Tuesday, March 14, 2006 12:04 PM
|=> To: rt-users at lists.bestpractical.com
|=> Subject: [rt-users] Change control
|=> 
|=> Hi Folks,
|=> Has anyone come up with any good methodologies for change 
|=> control of an RT installation?  Many of the components are 
|=> database records that don't seem amenable to CVS control, 
|=> scrips and templates as well as custom field definitions 
|=> and queue setups.  We'd like to have a record of what 
|=> changed when and by whom, and be able to reconstruct the 
|=> state of the system or back out a change.  Even an audit 
|=> record of  what changed would be better than nothing, even 
|=> if it can't be used directly for backing out a change.  Has 
|=> anyone tackled this?
|=> Best,
|=> -Chuck Boeheim
|=> Stanford Linear Accelerator Center
|=>