ugh, ya, that sort of thing leads to design by committee and voting blocks. lets not.
On Wed, May 1, 2013 at 3:43 PM, Filip Maj <[email protected]> wrote: > +1 lazy consensus. Cordova has a consistent release schedule so voting on > something that is predictable seems overkill. > > If you feel you'd like to change the release process to include an > official vote, Andrew, then we should start a vote on the private list, > I.e. Vote-to-change-the-process kind of vote. > > On 5/1/13 3:37 PM, "Brian LeRoux" <[email protected]> wrote: > >>Ultimately its up to us how we want to run with it. Far prefer lazy >>consensus to voting. >> >>On Wed, May 1, 2013 at 3:15 PM, Andrew Grieve <[email protected]> >>wrote: >>> Even in the pre-updated release steps, it explicitly says we need a vote >>> and refers to this "apache way" doc: >>> >>> http://www.apache.org/dev/release.html#approving-a-release >>> >>> >>> On Wed, May 1, 2013 at 4:23 PM, Filip Maj <[email protected]> wrote: >>> >>>> We decided on voting for each release? I thought it was lazy consensus >>>>(as >>>> with all decisions we make)? >>>> >>>> On 5/1/13 1:17 PM, "Andrew Grieve" <[email protected]> wrote: >>>> >>>> >I'm not sure I saw the vote thread, nor an announcement release, but >>>> >issues >>>> >are being closed that indicate that it has happened. >>>> > >>>> >I appreciate everyone's effort in getting it out, but the vote is a >>>>super >>>> >important step because it's our last chance to say "is everyone >>>> >comfortable >>>> >with this release". >>>> > >>>> >I'd like to say that it was clearly documented on the release wiki >>>>page >>>> >(which it is)... but the wiki's been down for two days :P. >>>> >>>> >
