Hi infrastructure team -- A question (sorry if this isn't the right forum, it's the nearest thing I could find ;).
To date in SpamAssassin, we've used a "role account", namely a user called "release", to build releases. Our build procedure relies on using a role account in order to insulate itself from user-specific environmental settings. This has proved to be a useful convention in the past, where occasionally an overlooked environmental detail turned out to be important to how the resulting tarballs came out; we've learned from experience that having a defined host and defined user-account to do releases from, works well to avoid that. Another bonus: it also means that if PMC member A is the guy with all the build tools etc. installed in his home dir, and he ups and leaves the project, the build scripts are insulated from having to be changed to reflect this. (by "build tools" in this case, BTW, I mean for example the entire compiled perl 5.8.x install and required modules; too big to be put in svn in my opinion, although I may be wrong there.) Is the "release role account" concept used in the ASF at all? What would you all suggest? --j.
