A release plan is used to keep all the developers aware of when a release is desired, who will be the release manager, when the repository will be frozen in order to create the release, and assorted other trivia to keep us from tripping over ourselves during the final moments. Lazy majority decides each issue in the release plan. Showstoppers Showstoppers are issues that require a fix be in place before the next public release. An issue becomes a showstopper when it is considered such by an active developer and remains so by lazy consensus. Votes are being requested early so as to uncover conflicts before too much work is done.
All product changes to the currently active repository are subject to lazy consensus.
Doubtful changes, new features, and large-scale overhauls need to be discussed before being committed to a repository. Any change that affects the semantics of arguments to configurable directives, significantly adds to the runtime size of the program, or changes the semantics of an existing API function must receive consensus approval on the mailing list before being committed. Each developer is responsible for notifying the appropriate mail list when they have an idea for a new feature or major change to propose for the product. No advance notice is required to commit singular bug fixes. Related changes should be committed as a group, or very closely together.