For those who are not familiar with the voting procedure, if you have tested epic4-2.1.1, and have found it to be substantially without defect, and you're willing to publicly go on the record to say that, you may vote. *Everyone* who tests epic4-2.1.1 is eligible to vote, no matter who you are or what your "qualifications" are.
The voting remains open until the vote reaches 15-0. This means 15 people vote Aye, and will have their names put into the VOTES file that will ship with epic4-2.2. If any proper NO votes are receieved, this is considered a "block" and the release will not occur until the problem is fixed, or substantially reasonable steps have been taken to minimize the problem. A proper NO vote indicates a specific, particular, reproducable problem that substantially limits EPIC in some way (eg, a crash). An improper NO vote would be along the lines of asking for a feature to be added, or disagreeing over whether a feature should behave the way it does. I always promise to exercise good faith in trying to determine if a NO vote is proper. (Yes, I have gotten improper NO votes in the past by people who were trying to be difficult, and I've had to ignore them. I don't like to do this, though.) Right now the vote is 3 votes AYE and 0 votes NO. The election stands open until the vote is 15-0. This will take as long as necessary. EPIC4-2.0 took a month to pass the vote. I wouldn't be suprised if EPIC4-2.2 took that long. If you've voted, I ask for your patience. If you've not voted, then test it and vote! Jeremy _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
