+1 JFDI. I've not seen anything but +1s across the board. We have consensus. This is no different than any other code change.
-Taylor > On Aug 18, 2016, at 8:53 PM, Jungtaek Lim <[email protected]> wrote: > > Before stalling, whether this should need VOTE or not, we confirmed our > consensus regarding this and all positive. > > I'll go on merging the pull request. Please let me know if you feel > it's inappropriate so that I can revert. > > - Jungtaek Lim (HeartSaVioR) > > On Wednesday, August 17, 2016, Bobby Evans <[email protected]> > wrote: > >> OK I think we should clarify that in the case of code changes. >> - Bobby >> >> On Wednesday, August 17, 2016 9:40 AM, Jungtaek Lim <[email protected] >> <javascript:;>> wrote: >> >> >> As Harsha said, I also think everyone has different interpretation of >> BYLAWS. I requested Harsha to go on voting before applying actual change, >> because BYLAWS [1] clearly states that, >> >> "Decisions regarding the project are made by votes on the primary project >> development mailing list. ... Votes are clearly indicated by subject line >> starting with [VOTE]. ... Voting is carried out by replying to the vote >> mail." >> >> I interpret this as it is, since it clearly states about what the vote is, >> and how to vote. We could even more strictly like this, "Every decisions >> regarding the project should pass VOTE for making effect on project", but >> we implicitly allowed general consensus. >> >> I just thought this is beyond the thing which can be handled with general >> consensus, but I'm also fine if we all agree this can be handled as a code >> change. >> >> - Jungtaek Lim (HeartSaVioR) >> >> [1] http://storm.apache.org/contribute/BYLAWS.html >> >> >> 2016년 8월 17일 (수) 오후 11:21, Bobby Evans <[email protected]>님이 작성: >> >>> I don't think there is anything wrong with checking with others around a >>> fairly major change like this, which by the way I am +1 on, but switching >>> the travis config and changing a 7 to an 8 in the pom.xml is technically >> a >>> code change, and only really needs the votes accordingly for that. If >> you >>> want that vote to happen here and not on the JIRA for visibility that >>> technically is not according to the bylaws but it follows the spirit so I >>> personally am OK with it. http://storm.apache.org/ >> contribute/BYLAWS.html >>> >>> Which on a side note, that whole discussion about changing which mailing >>> lists get updated when, we might want to either change the bylaws or >> update >>> some documentation so that votes specifically are forwarded to the dev >>> list. Otherwise we start to run into a situation where an important vote >>> for a code change is happening like this, and some people are not aware >> of >>> it, because they are only watching the dev list. - Bobby >>> >>> On Tuesday, August 16, 2016 11:59 PM, Harsha Chintalapani < >>> [email protected] <javascript:;>> wrote: >>> >>> >>> I guess everyone has different interpretation of what Bylaws means . >> More >>> context >>> >>> https://github.com/apache/storm/pull/1628 >>> >>> anything wrong with Vote thread? >>> >>> >>> On Tue, Aug 16, 2016 at 8:04 PM P. Taylor Goetz <[email protected] >> <javascript:;>> wrote: >>> >>>> Why is this a VOTE? >>>> >>>> >>>>> On Aug 16, 2016, at 9:18 PM, Harsha Chintalapani <[email protected] >> <javascript:;>> >>>> wrote: >>>>> >>>>> Hi All, >>>>> We had a discussion thread for removing Java 7 support for >> Storm >>>>> 2.0. >>>>> Here is a formal voting thread and the JIRA >>>>> https://issues.apache.org/jira/browse/STORM-2041. >>>>> >>>>> Thanks, >>>>> Harsha >>>> >>>> >>> >>> >>> >> >> > > > > -- > Name : Jungtaek Lim > Blog : http://medium.com/@heartsavior > Twitter : http://twitter.com/heartsavior > LinkedIn : http://www.linkedin.com/in/heartsavior
