Hi,
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 ...".
Since (the Sage review process and) the Sage release process have been
pretty stable for more than a year now, this should go right into a
new chapter in the Sage Development Guide. (IIRC Minh already has
compiled some notes there about the Sage review process.)
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.)
>From experience, and surprisingly fast, nobody will want to miss such
check-lists again.
Especially, if you're going to rotate fast through the half dozen guys
you mentioned.
Cheers,
gsw
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
