>>> In article <[EMAIL PROTECTED]>, Ronan Flood <[EMAIL PROTECTED]> writes:
Ronan> Harlan Stenn <[EMAIL PROTECTED]> wrote: >> OK, so y'all want there to be an RC release that is identical to the >> released version? Ronan> Seems sensible to me, but I know nothing about release engineering Ronan> :-/ I'm trying to see the point. It seems to me this would only add an extra delay to the release process. I guess it depends on whether or not folks only grab the first RCx tarball or if they grab the subsequent snapshot tarballs as well. Ronan> How does ISC do it for BIND? It has RCs. Is there a difference Ronan> between an RC and a beta? I'm not sure about BIND, but I can find out soon. As for RC and beta, I think a useful metaphor might be a theatrical performance. The play (and music) are delivered to the performers "ready to go" and need to be integrated. Once any local changes are finalized one could say it's in beta. The dress rehearsal is the RC. I suspect we could say that 'beta' means there is a feature freeze and only (blocking?) bug fixes go in. Ronan> It was just a suggestion -- proceed as you deem appropriate ... I have been contemplating all of these things lately - it's good to rehash and understand the cause/effect and interactions. H _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
