On 2009-Jun-02 13:01:26 -0700, gsw <georgswe...@googlemail.com> wrote: >a "Configuration Management Plan" would be quite helpful (fancy >wording from professional software development). > >In down-to-earth terms, (and with a grain of salt) this would be a >check-list "first you do this ..., remember always to ..., then you do >that ..., and don't you forget to ..., and at the end you have to ..., >right before uploading it here ..., and as a last thing ...".
If you want some ideas for what might be useful to have in the "release engineering" part of the Sage Configuration Management Plan, you might like to check out FreeBSD Release Engineering: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html The actual details are very different but the overall objective (to provide a repeatable process for generating a tested software release) is the same. There are probably similar documents associated with the other free OSs and larger applications but I can't provide URLs offhand. >Motto: If you are a "first time" release manager, and you have any >question at all, that is not answered by this chapter(s), then 1) Put >this question into the Sage Development Guide; and once you got to >know the answer, then 2) Update the Sage Development Guide >accordingly, so the next ones after you will have a yet easier time. >("Frequently Answered Questions" is just another wording for this.) This is worthwhile but I don't believe a FAQ approach is the best way to document a process. -- Peter Jeremy
pgpV5I2w8BIBN.pgp
Description: PGP signature
