<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 10, 2012, at 12:44 PM, Quinn Weaver wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>If you have to homebrew, are you thinking of using your distro's packaging system? Some packaging systems will allow you to write post-install hooks[1]. You could write one that mails a list of stakeholders whenever a new version of a package is installed (in, say, QA), it mails a list of stakeholders. That might or might not work, depending on your client's procedures around installing things in different environments.</div></span></blockquote><div><br></div><div>Unfortunately, the software is not deployed with any packaging system. Individual teams just throw files into production at will. Sigh.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>If you need to get fancy (and it sounds like you might), you could store each package's list of stakeholders in a database and write a web UI for it, rather than hard-coding it into the RPM.</div></span></blockquote><div><br></div><div>That is basically what they have started to build. Each project in Subversion has a magical XML file that declares who owns it and what it depends on. Then they've build a system that periodically collects this data into a DB and a web UI for browsing it. From what I've seen, the system generally works but few projects participate (however, that is a management problem).</div><div><br></div><div>For reasons unclear to me, folks are re-examining the requirements and implementation. But the discussions are often unproductive. I'd like to propose that they just buy something and be done with it. So my task is to go find that something.</div><div><br></div><div>-Jeff</div></div><br></body></html>