So what is change management to an IBM i person?

Anytime on this list people talk about source control management, someone
points out that source control management is only a subset of what an IBM i
change management solution provides. Coming from a windows/linux world, I
get that. Git or subversion is used by your developers. Change management
refers to a whole bunch of policies that you show your auditors. However,
unless your using something like chef or puppet that uses a git based
system for change management, there really isn't an off the shelf or OSS
system I could call a "change management system".

But exactly what does an IBM i person expect a holistic change management
system to do? I think once theinks like jenkins, chef and puppet get
working on PASE, such a system could be built with OSS stuff, and IBM i
people could develop a set of best practices for managing the PASE side of
things that would be very interesting to linux admins.

Justin