Re: Release Process suggestion

At 14:27 3/5/2001, Cynic wrote:

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.)

It doesn't necessarily have to be one of us, by the way; in 4.0.4 for instance, it was Sascha.

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?

Yes, it makes sense. I know that many companies work that way (including the one I work for). In PHP I emulated it at the CVS level, and built the final release based on the last RC tag. The only reason for this today is that the NEWS, main/php_version.h and ./configure.in include the version number and/or date, that have to be changed once the final release it out. Zeev