Jan, Help me understand this procedure a little bit better.
I assume that if a new release candidate file is created, that rescinds the previous votes, because they could not be about that version of the file. (Maybe calling this a [PRE-VOTE] is not a good choice, but since [VOTE]s are being collected, I am not certain what to call this procedure.) I also assume, were this a [VOTE] and the candidate changed, it would need to be a new candidate (identified differently) and a new [VOTE] would have to start? Presumably those who checked it before would double-check the new RC and vote accordingly. Is that your understanding? - Dennis PS: Abstentions (0), like +1, require no explanation. An abstention is an abstention. I have nothing that I wish to say about the "=0". -----Original Message----- From: jan i [mailto:[email protected]] Sent: Friday, August 14, 2015 09:13 To: [email protected]; Dennis Hamilton <[email protected]> Subject: Re: [PRE-VOTE] Release candidate 0.1 On 14 August 2015 at 17:48, Dennis E. Hamilton <[email protected]> wrote: > =0 (binding) > > I do not give permission for this to be applied automatically to a genuine > [VOTE]. > there is no request for you to vote now, it is an option for those who want to save mails, as I wrote, so no need not to give perission. It is much more interesting, if you found something wrong with the release candidate, since you have a 0 and not a +1. rgds jan i. [ ... ]
