On 10/19/06, Daniel Kulp <[EMAIL PROTECTED]> wrote:
The problem is that this is not ALLOWED. The artifacts that were voted on MUST be the artifacts that are released. You cannot vote on one set of artifacts, then build a whole new set of artifacts for the release.
In practice, this does actually happen. Jakarta Commons uses release candidates, calls a vote, and then it's up to the release manager to make the final changes (usually just the version number, maybe minor editing of release notes,) and build/publish the final version. See: http://www.nabble.com/forum/Search.jtp?forum=317&local=y&query=VOTE+release Some projects don't do preliminary tags and release candidates, they build 2.0.7 once and if any problems are found, they just move on to 2.0.8. Then there are others that don't like to "skip" release numbers, so they'll just keep rebuilding 2.0.7 until they get it right. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
