Release Process suggestion

If I understand these things right, current state is this: after a certain number of RC's, Andi or Zeev decide it's time and announce the plan to tag a release in, say, two days. When no one complains, they tag current release branch, package, and the new release is officialy announced. (Correct me if I'm wrong.) Could this be changed so that after a certain number of RC's, and a number (two... five?) after the last one, when there aren't any issues warranting another RC, the release is packaged from the last RC? Something along the way ASF do it - they "pre-release" releases for testing, and if it's ok, the release is made public. Does it make any sense? cynic@mail.cz ------------- And the eyes of them both were opened and they saw that their files were world readable and writable, so they chmoded 600 their files. - Book of Installation chapt 3 sec 7