Voters intending to veto an action item should make their opinions known to the group immediately so that the problem can be remedied as early as possible. Long term plans are simply announcements that group members are working on particular issues related to the Project. These are not voted on, but Developers who do not agree with a particular plan, or think that an alternative plan would be better, are obligated to inform the group of their feelings. Short term plans are announcements that a developer is working on a particular set of documentation or code files with the implication that other developers should avoid them or try to coordinate their changes. A release plan is used to keep all Developers aware of when a release is desired, who will be the release manager, when the repository will be frozen to create a release, and other assorted information to keep Developers from tripping over each other.
Lazy majority decides each issue in a release plan.
After a new release is built, it must be tested before being released to the public. Majority approval is required before the release can be made. Showstoppers Showstoppers are issues that require a fix be in place before the next public release. They are listed in the status file in order to focus special attention on these problems. An issue becomes a showstopper when it is listed as such in the status file and remains so by lazy consensus.