Published to dist/ and npm.
On Tue, Jul 8, 2014 at 11:28 AM, Mark Koudritsky <[email protected]> wrote: > The vote has now closed. The results are: > Positive Binding Votes: 3 > > Mark Koudritsky > Andrew Grieve > Michal Mocny > > Negative Binding Votes: None > Other Votes: None > The vote has passed. > > > On Tue, Jul 8, 2014 at 11:26 AM, Mark Koudritsky <[email protected]> > wrote: > >> This went slowly, but we got 3 votes now, declaring this vote as passed >> and publishing this release. >> >> >> On Mon, Jul 7, 2014 at 10:32 AM, Michal Mocny <[email protected]> >> wrote: >> >>> Well, I took a look at the CI, which is currently red but wasn't recently >>> and covered an overlap of patches here. It may not be a perfect test in >>> this case, but the release instructions specifically state that its not a >>> requirement to run all tests manually. If you use/test the tools on a >>> regular basis, I think it should just be a matter of verifying that the >>> release is a sane cut. We want to get these out with minimal effort, so >>> that people actually look at releases and vote! >>> >>> (Speaking of, Josh would you mind testing and voting, so we can get a >>> non-Googler before EOD? Thanks!) >>> >>> >>> On Mon, Jul 7, 2014 at 10:14 AM, Josh Soref <[email protected]> >>> wrote: >>> >>> > Michal Mocny wrote: >>> > > +1, verified archives, created sample project, added/removed >>> > > plugins&platforms, ran apps, all successfully. >>> > >>> > Could I ask people to include "running the tests" and "running serve" >>> in >>> > their list of testing steps? :) >>> > >>> > >>> >> >> >
