Thread: Patch Docs
View Single Post
  #4 (permalink)  
Old September 26th, 2007, 12:47
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
 
Join Date: Jun 2006
Location: West Chester, PA
Posts: 821
Blog Entries: 7
Thanks: 53
Thanked 201 Times in 121 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Patch Docs

Nikesh,

In that case, each company handles the distribution of the custom patches differently and there isn't a standardized process. You'll need to look at the customizations that you've made, the files included and determine the best way to package them up for installation -- making it easy for the customer and as straightforward and error-proof as possible. More important than the installation procedure is having complete and proper documentation.

I created the OTM installer, so I'm comfortable with tools like InstallAnywhere and will often use it for large, complex customizations. Other times, a simple zip or jar file works best.

Regardless, we utilize an internal source control system to manage versions and changes to the custom code and I highly recommend that you do the same.

--Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com
Reply With Quote
The Following User Says Thank You to chrisplough For This Useful Post:
nikesh mohanlal (September 26th, 2007)