RE: Documenting code changes

Cyndi,

I don't belong to a larger group, as you seem to, but I do the first steps:
Put documentation into the header and put the ticket (in my case, Project)
number in the left-hand side of the code. I do *not* keep the old lines in
the production source; that just gets too hard to read the next time (and
there always is a 'next time'). BUT I do keep a backup of the source prior
to the change; in fact I archive all versions of a program there. PGM001,
for example, gets archived as PGM00101, PGM00102, etc., before the latest
changes are made. Only a couple of times have I had to go there, but, when
I needed to, it was good to have.

Your ticket number probably relates to my project number. That is, it
specifies the requirements and includes all of the documentation, as well as
the original request. I keep mine in electronic documents with attachments
in a folder in the IFS, which is backed up with the application libraries
nightly. I have worked at organizations that were more paranoid then I am,
but this has served my purposes adequately for the last 20 years.

Sorry, I know I did not answer you're original question/request: I don't
have any links to "best practices."

Jerry C. Adams
IBM i Programmer/Analyst
Women and cats will do as they please, and men and dogs should relax and get
used to the idea.