cvs tagging for 3.0

Now that we've got a final build of 3.0 we need to
tag the tree.  I'm sure we actually have a policy
but with several people responsible for several
different parts of the tree (spec/runtime-test/tools)
it would be really good to be sure that we uniformly
tag the cvs tree as the various part release.  
Except for test, which I haven't looked at, I know
we did this right for 2.x, because I'm able to check
out a 2.x branch with a single tag.

Who's doing the tagging, and what's the tag going
to be? (note Andrew already tagged the runtime-test
tree, so we may have somethig to follow).