Works for me, let me know how I can get involved/help. Sent from my iPhone
> On Jun 13, 2016, at 9:24 PM, Lior Zeno <liorz...@gmail.com> wrote: > > Saikat, I still think that we should discuss it here. We can talk in > private about specific issues if you'd like. > > I'll open an umbrella issue for this release. It will include all necessary > steps, e.g. keys and docs, but also jira cleaning and reviewing all pending > patches we have. I know it's a lot of work, but it has to be done. > > Hari, thank you. Would you please mentor? >> On Jun 14, 2016 3:21 AM, "Hari Shreedharan" <hshreedha...@apache.org> wrote: >> >> Only committers can commit to the repo. In the past, when release managers >> were not committers, one committer mentored the release manager. For the >> release, patches would be posted as usual on a release and the committer >> would commit the patches. Basically follow all steps as is, and then just >> post patches to jiras. See the umbrella jira for Flume 1.6 release: >> https://issues.apache.org/jira/browse/FLUME-2674 >> >> Lior - I have added you as a contributor on jira. This should allow you to >> create jira tickets and assign them to yourself. >> >> On Mon, Jun 13, 2016 at 4:31 PM Saikat Kanjilal <sxk1...@hotmail.com> >> wrote: >> >>> Should we have a google hangout session to figure this out? >>> >>>> From: liorz...@gmail.com >>>> Date: Mon, 13 Jun 2016 22:44:29 +0300 >>>> Subject: Re: Flume 1.7.0 release >>>> To: dev@flume.apache.org >>>> >>>> Guys, thank you for your support and motivation. There are still two >> big >>>> issues we need to figure out before we can proceed: >>>> (a) Who can commit to the repo? >>>> (b) Who has JIRA permissions? >>>> >>>> Hari, I'll be happy to run this release, if that's fine by everyone. >>>> >>>>> On Mon, Jun 13, 2016 at 6:52 AM, Lior Zeno <liorz...@gmail.com> wrote: >>>>> >>>>> Hi Shiwei, >>>>> >>>>> Please see this: >>>>> https://cwiki.apache.org/confluence/display/FLUME/How+to+Contribute. >>>>> In a nutshell, issues are manages on JIRA, and code contributions are >>> done >>>>> via patches (not pull requests). >>>>> Regarding a release plan, that is true, we will need to discuss a >>> roadmap >>>>> and manage more carefully our release plans. However, since there was >>> not >>>>> any new release in the past year, the next version of Flume will have >>>>> plenty of new features and bug fixes :) >>>>> >>>>> On Mon, Jun 13, 2016 at 6:26 AM, shiwei qin <qinshiw...@gmail.com> >>> wrote: >>>>> >>>>>> I'd like to be able to release the new version as soon as possible. >>> Also I >>>>>> never see release plan. In fact, I most want is the ability to flex >>>>>> developers migrate to github, There are a lot of people do not >> really >>> know >>>>>> how to contribute code to flume, like me. >>>>>> >>>>>> 2016-06-13 6:43 GMT+08:00 Attila Simon <s...@cloudera.com>: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> I would love to hear more and get involved. >>>>>>> >>>>>>> Just another enthusiastic developer candidate, >>>>>>> Attila >>>>>>> >>>>>>> >>>>>>> On Sun, Jun 12, 2016 at 7:09 AM, Saikat Kanjilal < >>> sxk1...@hotmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Sure will do, meanwhile should we get together over google >>> hangout to >>>>>>>> discuss the outstanding JIRA's. I'm looking to get more >> actively >>>>>>> involved >>>>>>>> in the project. >>>>>>>> >>>>>>>>> Date: Sun, 12 Jun 2016 16:56:30 +0300 >>>>>>>>> Subject: Re: Flume 1.7.0 release >>>>>>>>> From: liorz...@gmail.com >>>>>>>>> To: dev@flume.apache.org >>>>>>>>> >>>>>>>>> Please open a new thread on your proposal with motivation, >>> design >>>>>> and >>>>>>> an >>>>>>>>> example. If other shipping frameworks, such as fluentd or >>> logstash, >>>>>>> have >>>>>>>> a >>>>>>>>> similar feature then please add it as a reference. >>>>>>>>> >>>>>>>>> In this thread, we will continue discussing the next release >> and >>>>>> how we >>>>>>>> can >>>>>>>>> solve our problems in order to release more than once a year. >>>>>>>>> Actually I never even got to patch submit page, I just wanted >>>>>> feedback >>>>>>>> from >>>>>>>>> the community around interest for a graph sink to write or >> read >>> from >>>>>>>>> neo4j/orientdb, I've started dev efforts but am worried that >> no >>> one >>>>>> has >>>>>>>>> responded. What are active next steps to get to a more >> vibrant >>>>>>>> community >>>>>>>>> and move this plugin along? I am in the initial dev and >> design >>>>>> stage >>>>>>> for >>>>>>>>> the plugin. >>>>>>>>> >>>>>>>>> Sent from my iPhone >>>>>>>>> >>>>>>>>>> On Jun 12, 2016, at 2:03 AM, Lior Zeno <liorz...@gmail.com> >>>>>> wrote: >>>>>>>>>> >>>>>>>>>> This is absolutely true. The availability of the project's >>>>>> committers >>>>>>>> is >>>>>>>>>> very low, which leads to cases like yours where people >> submit >>>>>> patches >>>>>>>> and >>>>>>>>>> never get a response, even after a year of waiting. I >> believe >>>>>> that we >>>>>>>> have >>>>>>>>>> to be more active and available, since low availability >>>>>> discourages >>>>>>>>>> contributors. >>>>>>>>>> I think that such discussions should take place either here >>> or on >>>>>>> JIRA, >>>>>>>>>> since it does not limit the discussion to a small group of >>> people, >>>>>>> but >>>>>>>>>> instead allows the community to be a part of the project's >>> future. >>>>>>>>>> >>>>>>>>>> On Sun, Jun 12, 2016 at 2:09 AM, Saikat Kanjilal < >>>>>>> sxk1...@hotmail.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> I would like to help out managing Jira's but never heard >> back >>>>>> from >>>>>>> the >>>>>>>>>>> community about the graph sink that I've been working on. >>> Does it >>>>>>> make >>>>>>>>>>> sense to do a google hangout to discuss roadmap/upcoming >>>>>> features? >>>>>>>>>>> >>>>>>>>>>> Sent from my iPhone >>>>>>>>>>> >>>>>>>>>>>> On Jun 11, 2016, at 10:19 AM, Lior Zeno < >> liorz...@gmail.com >>>> >>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Let's first examine our JIRA issues. We have fixed issues >>> with >>>>>> an >>>>>>>> empty >>>>>>>>>>>> fixVersion. In addition, we still have unresolved issues >>> with >>>>>>>>>>>> fixVersion=v1.7.0. Let's deal with these first. I would do >>> it >>>>>>> myself, >>>>>>>>>>> but I >>>>>>>>>>>> don't have the appropriate permissions for that. >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Jun 11, 2016 at 8:10 PM, Hari Shreedharan < >>>>>>>>>>> hshreedha...@apache.org> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Sound good to me. If we have a volunteer to run the >>> release I >>>>>> will >>>>>>>>>>> gladly >>>>>>>>>>>>> help out. >>>>>>>>>>>>>> On Sat, Jun 11, 2016 at 6:54 AM Lior Zeno < >>> liorz...@gmail.com >>>>>>> >>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Anybody? >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno < >>>>>> liorz...@gmail.com> >>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi guys, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I think we should work together towards a new release. >>> It has >>>>>>>> been a >>>>>>>>>>>>> year >>>>>>>>>>>>>>> since the last release, and there are many new features >>> that >>>>>>> were >>>>>>>>>>> added >>>>>>>>>>>>>> in >>>>>>>>>>>>>>> this year. >>>>>>>>>>>>>>> What do you think? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Lior >>
