On Sun, 19 Oct 2003, Waldek Hebisch wrote:
Frank Heckenbach wrote:
Conclusion (as far as I'm concerned):
Never make a release under pressure anymore. (Everyone, if you want to tell me why a new release is urgently needed at any time, please redirect to /dev/null.)
Never do post-release updates, even if serious bugs. (Except perhaps for the proposed alpha/beta scheme.)
Frank, I was surprised that the updates have the same version number as original release, and that is the repeating complaint. I do not know what your release scripts do, but AFIKS just renaming tarballs and the main source directory would completely avoided any confusion.
Suggestion: when you upload a new tarball that has the same version number change the name of the tarball to add a revision number. thus the third revision of gpc-20030830 would be gpc-20030830-r3.tar.gz and the untared tree would still be gpc-20030830/
Last step would be to remove the old tarball as it is no longer being overwritten.
Therefor a new version number would only be required if there were major changes or if you wanted to keep the old version around for some reason.
Hope this is helpful Russ