> The third option is also necessary. DON'T CHANGE. > > As many/several files could have customizations applied to them > rolling up > could overwrite and cause ??. Anyone applying the patches as they were > available would loose all the changes made to files in prior patches. > Perhaps offering rolled up and individual would help folks who > don't make > changes regularly. A list of what changes were made and where would be > helpful so one could do a search and replace within a customized file. Regarding the DON'T CHANGE option, I agree that I should have included that one, and that would actually be my personal preference, since the hotfixes would be kept small and very specific. Hotfixes would then need to be applied in sequence. So, anyone agreeing with that should click this VOTE link: mailto:[EMAIL PROTECTED]?subject=3-DONT_CHANGE_Current_System Regarding keeping a list of changes, I realize that more advance coders are digging into the guts of other html and js files with changes, but we cannot be responsible for such changes, and making change records to the level necessary for integration with such customized files would increase our hotfixing time by at least a factor of 5. I would recommend that if you're editing code in templates we don't intend to be edited, that you should keep detailed notes of your changes on your end in case you need to reproduce them in new files. The webmail system is big and complex, and small changes in one bit of JavaScript can often have repercussions in other places and files. Regards, Ron ______________________________________________________________________ The HKSI-IMail Admin List is hosted by........ Humankind Systems, Inc. Questions, Comments or Complain like Hell.. mailto:[EMAIL PROTECTED] Message Archive... http://www.tallylist.com/archives/index.cfm/mlist.4 To Manage your Subscription......... http://humankindsystems.com/lists
