On Jan 15, 2008 1:09 PM, Dale Newfield <[EMAIL PROTECTED]> wrote: > Frank W. Zammetti wrote: > > my feeling is that until a project deprecates a release, then > > no, there would be no expiration. Anyone who +1'd a release is implying > > they are willing to support it until it's officially deprecated. > > Do we ever deprecate any releases except non-current patch-level ones? > (I.E.: is W.X.Y automatically deprecated when W.X.Z (where Z>Y) is > released? Is A.B.C ever deprecated if there exists no A.B.D where D>C?)
Not in so many words. Though, once we move on to the next minor series (x.1 to x.2), it seems unlikely that we would go back and add new features to x.1. But if a committer wanted to do it for some reason, and the release plan and quality vote passed, then it would happen. The Apache Way favors individual initiative tempered by peer review. We do deprecate features regularly ... and we even try to remove them after deprecation :) The strange part is that while the release plan is lazy majority, and the quality vote is active majority (3 +1s for quorum and +1s>-1s), each individual code change is subject to a lazy consensus vote, where a PMC member has a unilateral veto. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
