[jira] [Resolved] (FLUME-2924) Flume 1.7.0 release

[JIRA]

 [ 
https://issues.apache.org/jira/browse/FLUME-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bessenyei Balázs Donát resolved FLUME-2924.
---
Resolution: Fixed
  Assignee: Bessenyei Balázs Donát

> Flume 1.7.0 release
> ---
>
> Key: FLUME-2924
> URL: https://issues.apache.org/jira/browse/FLUME-2924
> Project: Flume
>  Issue Type: Umbrella
>Affects Versions: v1.7.0
>Reporter: Lior Zeno
>Assignee: Bessenyei Balázs Donát
> Fix For: v1.7.0
>
>
> Release 1.7.0 umbrella issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [RESULT] Flume 1.7.0 release vote

[Mike Percy]

I just pushed the RC2 artifacts to dist and the staged Maven repo to
central.

it's best to wait 24 hours for the bits to propagate to the dist mirrors
before announcing the release, so users don't get confused when the
download links don't work for their local mirror yet.

Mike

On Mon, Oct 17, 2016 at 2:20 PM, Balazs Donat Bessenyei <bes...@cloudera.com
> wrote:

> Thank you for the help, Mike!
>
> On Mon, Oct 17, 2016 at 1:53 PM, Mike Percy <mpe...@apache.org> wrote:
> > Thanks for running the vote, Donat!
> >
> > I will help to deploy the staged artifacts.
> >
> > Mike
> >
> > On Mon, Oct 17, 2016 at 10:57 AM, Balazs Donat Bessenyei <
> > bes...@cloudera.com> wrote:
> >
> >> The release vote for Apache Flume 1.7.0 has been completed in this
> >> thread: https://lists.apache.org/thread.html/
> >> 3cf114125dbea6e662b69d1312c34184690af327900e8dcccea5edde@%
> >> 3Cdev.flume.apache.org%3E
> >>
> >> The vote has received 3 binding +1 votes from the following PMC members:
> >> Mike Percy
> >> Hari Shreedharan
> >> Brock Noland
> >>
> >> Four non-binding +1 votes were received from:
> >> Denes Arvay
> >> Bessenyei Balázs Donát
> >> Lior Zeno
> >> Attila Simon
> >>
> >> No +0 or -1 votes were received.
> >>
> >> Since three +1 votes were received from the PMC with no -1 votes, the
> >> vote passes and Flume 1.7.0 RC2 will be promoted to the Flume 1.7.0
> >> release.
> >>
> >> Thanks to all who voted!
> >>
> >>
> >> Thank you,
> >>
> >> Donat
> >>
>

Re: [RESULT] Flume 1.7.0 release vote

[Balazs Donat Bessenyei]

Thank you for the help, Mike!

On Mon, Oct 17, 2016 at 1:53 PM, Mike Percy <mpe...@apache.org> wrote:
> Thanks for running the vote, Donat!
>
> I will help to deploy the staged artifacts.
>
> Mike
>
> On Mon, Oct 17, 2016 at 10:57 AM, Balazs Donat Bessenyei <
> bes...@cloudera.com> wrote:
>
>> The release vote for Apache Flume 1.7.0 has been completed in this
>> thread: https://lists.apache.org/thread.html/
>> 3cf114125dbea6e662b69d1312c34184690af327900e8dcccea5edde@%
>> 3Cdev.flume.apache.org%3E
>>
>> The vote has received 3 binding +1 votes from the following PMC members:
>> Mike Percy
>> Hari Shreedharan
>> Brock Noland
>>
>> Four non-binding +1 votes were received from:
>> Denes Arvay
>> Bessenyei Balázs Donát
>> Lior Zeno
>> Attila Simon
>>
>> No +0 or -1 votes were received.
>>
>> Since three +1 votes were received from the PMC with no -1 votes, the
>> vote passes and Flume 1.7.0 RC2 will be promoted to the Flume 1.7.0
>> release.
>>
>> Thanks to all who voted!
>>
>>
>> Thank you,
>>
>> Donat
>>

Re: [RESULT] Flume 1.7.0 release vote

[Mike Percy]

Thanks for running the vote, Donat!

I will help to deploy the staged artifacts.

Mike

On Mon, Oct 17, 2016 at 10:57 AM, Balazs Donat Bessenyei <
bes...@cloudera.com> wrote:

> The release vote for Apache Flume 1.7.0 has been completed in this
> thread: https://lists.apache.org/thread.html/
> 3cf114125dbea6e662b69d1312c34184690af327900e8dcccea5edde@%
> 3Cdev.flume.apache.org%3E
>
> The vote has received 3 binding +1 votes from the following PMC members:
> Mike Percy
> Hari Shreedharan
> Brock Noland
>
> Four non-binding +1 votes were received from:
> Denes Arvay
> Bessenyei Balázs Donát
> Lior Zeno
> Attila Simon
>
> No +0 or -1 votes were received.
>
> Since three +1 votes were received from the PMC with no -1 votes, the
> vote passes and Flume 1.7.0 RC2 will be promoted to the Flume 1.7.0
> release.
>
> Thanks to all who voted!
>
>
> Thank you,
>
> Donat
>

[RESULT] Flume 1.7.0 release vote

[Balazs Donat Bessenyei]

The release vote for Apache Flume 1.7.0 has been completed in this
thread: 
https://lists.apache.org/thread.html/3cf114125dbea6e662b69d1312c34184690af327900e8dcccea5edde@%3Cdev.flume.apache.org%3E

The vote has received 3 binding +1 votes from the following PMC members:
Mike Percy
Hari Shreedharan
Brock Noland

Four non-binding +1 votes were received from:
Denes Arvay
Bessenyei Balázs Donát
Lior Zeno
Attila Simon

No +0 or -1 votes were received.

Since three +1 votes were received from the PMC with no -1 votes, the
vote passes and Flume 1.7.0 RC2 will be promoted to the Flume 1.7.0
release.

Thanks to all who voted!


Thank you,

Donat

[jira] [Assigned] (FLUME-2924) Flume 1.7.0 release

[Attila Simon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLUME-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Simon reassigned FLUME-2924:
---

Assignee: (was: Attila Simon)

> Flume 1.7.0 release
> ---
>
> Key: FLUME-2924
> URL: https://issues.apache.org/jira/browse/FLUME-2924
> Project: Flume
>  Issue Type: Umbrella
>Affects Versions: v1.7.0
>Reporter: Lior Zeno
> Fix For: v1.7.0
>
>
> Release 1.7.0 umbrella issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (FLUME-2924) Flume 1.7.0 release

[Attila Simon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLUME-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Simon reassigned FLUME-2924:
---

Assignee: Attila Simon

> Flume 1.7.0 release
> ---
>
> Key: FLUME-2924
> URL: https://issues.apache.org/jira/browse/FLUME-2924
> Project: Flume
>  Issue Type: Umbrella
>Affects Versions: v1.7.0
>Reporter: Lior Zeno
>Assignee: Attila Simon
> Fix For: v1.7.0
>
>
> Release 1.7.0 umbrella issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FLUME-2924) Flume 1.7.0 release

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563531#comment-15563531
 ] 

Hudson commented on FLUME-2924:
---

UNSTABLE: Integrated in Jenkins build Flume-trunk-hbase-1 #210 (See 
[https://builds.apache.org/job/Flume-trunk-hbase-1/210/])
FLUME-2924. Update POM versions to 1.8.0-SNAPSHOT (bessbd: 
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git=commit=bb0eba0b2000bbd0ec6602f6221279412cc208b4])
* (edit) flume-ng-node/pom.xml
* (edit) flume-shared/pom.xml
* (edit) flume-ng-configuration/pom.xml
* (edit) flume-ng-embedded-agent/pom.xml
* (edit) flume-ng-sdk/pom.xml
* (edit) flume-ng-sinks/flume-irc-sink/pom.xml
* (edit) flume-ng-sources/flume-jms-source/pom.xml
* (edit) flume-ng-sinks/flume-ng-elasticsearch-sink/pom.xml
* (edit) flume-ng-tests/pom.xml
* (edit) flume-shared/flume-shared-kafka-test/pom.xml
* (edit) flume-ng-sinks/flume-ng-morphline-solr-sink/pom.xml
* (edit) flume-ng-doc/sphinx/index.rst
* (edit) flume-ng-legacy-sources/pom.xml
* (edit) flume-ng-channels/pom.xml
* (edit) flume-ng-dist/pom.xml
* (edit) flume-ng-auth/pom.xml
* (edit) flume-ng-sources/flume-scribe-source/pom.xml
* (edit) flume-ng-sinks/flume-ng-hbase-sink/pom.xml
* (edit) flume-ng-sinks/flume-dataset-sink/pom.xml
* (edit) pom.xml
* (edit) flume-ng-sinks/flume-hdfs-sink/pom.xml
* (edit) flume-ng-sinks/flume-hive-sink/pom.xml
* (edit) flume-ng-channels/flume-kafka-channel/pom.xml
* (edit) flume-ng-channels/flume-jdbc-channel/pom.xml
* (edit) flume-checkstyle/pom.xml
* (edit) flume-ng-sinks/flume-ng-kafka-sink/pom.xml
* (edit) flume-ng-sources/flume-taildir-source/pom.xml
* (edit) flume-ng-clients/pom.xml
* (edit) flume-ng-doc/sphinx/FlumeUserGuide.rst
* (edit) flume-ng-legacy-sources/flume-avro-source/pom.xml
* (edit) flume-ng-legacy-sources/flume-thrift-source/pom.xml
* (edit) flume-ng-sources/pom.xml
* (edit) flume-ng-sinks/pom.xml
* (edit) flume-ng-channels/flume-file-channel/pom.xml
* (edit) flume-ng-sources/flume-kafka-source/pom.xml
* (edit) flume-ng-sources/flume-twitter-source/pom.xml
* (edit) flume-tools/pom.xml
* (edit) flume-ng-doc/sphinx/FlumeDeveloperGuide.rst
* (edit) flume-ng-clients/flume-ng-log4jappender/pom.xml
* (edit) flume-ng-core/pom.xml
* (edit) flume-ng-channels/flume-spillable-memory-channel/pom.xml


> Flume 1.7.0 release
> ---
>
> Key: FLUME-2924
> URL: https://issues.apache.org/jira/browse/FLUME-2924
> Project: Flume
>  Issue Type: Umbrella
>Affects Versions: v1.7.0
>Reporter: Lior Zeno
> Fix For: v1.7.0
>
>
> Release 1.7.0 umbrella issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Labels on issues blocking the Flume 1.7.0 release

[Mike Percy]

Hi Donat,
Seems ok. Thanks for telling us what you're up to.

Best,
Mike

On Fri, Jul 22, 2016 at 7:00 AM, Balazs Donat Bessenyei  wrote:

> Hello All,
>
> Some fellow collaborators (@denes, @sati) and I would like to help out
> with the 1.7.0 release.
> In order to do that, we started triaging and reviewing patches. (
> https://issues.apache.org/jira/browse/FLUME-2953?filter=12338032 )
> As part of this process, we are labelling tickets
> (reviewboard-missing, unit-test-missing, docs-missing and
> rebase-needed) so that it would be easier to track the progress with
> the issues (in a queryable way).
>
> If you have any ideas how this could be improved, please do tell.
>
>
> Thank you
>
> Donat
>

Labels on issues blocking the Flume 1.7.0 release

[Balazs Donat Bessenyei]

Hello All,

Some fellow collaborators (@denes, @sati) and I would like to help out
with the 1.7.0 release.
In order to do that, we started triaging and reviewing patches. (
https://issues.apache.org/jira/browse/FLUME-2953?filter=12338032 )
As part of this process, we are labelling tickets
(reviewboard-missing, unit-test-missing, docs-missing and
rebase-needed) so that it would be easier to track the progress with
the issues (in a queryable way).

If you have any ideas how this could be improved, please do tell.


Thank you

Donat

Re: Flume 1.7.0 release

[Mike Percy]

; >> > > 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
> > > > > >> > &

[jira] [Updated] (FLUME-2924) Flume 1.7.0 release

[Lior Zeno (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLUME-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lior Zeno updated FLUME-2924:
-
Fix Version/s: v1.7.0

> Flume 1.7.0 release
> ---
>
> Key: FLUME-2924
> URL: https://issues.apache.org/jira/browse/FLUME-2924
> Project: Flume
>  Issue Type: Umbrella
>Affects Versions: v1.7.0
>Reporter: Lior Zeno
> Fix For: v1.7.0
>
>
> Release 1.7.0 umbrella issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Flume 1.7.0 release

[Lior Zeno]

Thanks Mike!

BTW, what should we do with unresolved issues with fixVersion in unreleased
versions (other than 1.7.0) or released versions? Will it be ok to remove
the fixVersion and then check them later? I need to do at least one
maintenance pass over old issues.

On Mon, Jun 20, 2016 at 11:49 AM, Mike Percy <mpe...@apache.org> wrote:

> Thanks for doing the JIRA triage, Lior!
>
> This query might work a little better to find all of the open 1.7.0 issues:
>
> https://issues.apache.org/jira/browse/FLUME-2716?jql=project%20%3D%20Flume%20AND%20Resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.7.0
>
> It looks like some of these have patches and some don't. For the ones that
> have patches, I'll try to take a look at a couple of them, unfortunately
> not all because I'm really tight on time these days.
>
> Mike
>
> On Thu, Jun 16, 2016 at 11:49 AM, Lior Zeno <liorz...@gmail.com> wrote:
>
> > In addition, I opened an umbrella issue for this release:
> > https://issues.apache.org/jira/browse/FLUME-2674
> >
> > On Thu, Jun 16, 2016 at 9:35 PM, Lior Zeno <liorz...@gmail.com> wrote:
> >
> > > Hi guys,
> > >
> > > We still have the following issues to resolve in order to release:
> > >
> > >
> >
> https://issues.apache.org/jira/browse/FLUME-2340?jql=project%20%3D%20Flume%20AND%20(Status%20!%3D%20Resolved%20OR%20Resolution%20!%3D%20Fixed)%20AND%20fixVersion%20%3D%20v1.7.0
> > >
> > > Please review/submit a patch.
> > >
> > > In the second iteration we will look at issues that have patches
> attached
> > > to them but haven't been reviewed.
> > >
> > > Thanks!
> > >
> > > On Tue, Jun 14, 2016 at 8:56 AM, Hari Shreedharan <
> > hshreedha...@apache.org
> > > > wrote:
> > >
> > >> Sure. I can help with the release. My time to work on this would be
> > >> limited, so it might take me a day or two between updates.
> > >> On Mon, Jun 13, 2016 at 9:29 PM Saikat Kanjilal <sxk1...@hotmail.com>
> > >> wrote:
> > >>
> > >> > 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
> > >>

Re: Flume 1.7.0 release

[Lior Zeno]

In addition, I opened an umbrella issue for this release:
https://issues.apache.org/jira/browse/FLUME-2674

On Thu, Jun 16, 2016 at 9:35 PM, Lior Zeno <liorz...@gmail.com> wrote:

> Hi guys,
>
> We still have the following issues to resolve in order to release:
>
> https://issues.apache.org/jira/browse/FLUME-2340?jql=project%20%3D%20Flume%20AND%20(Status%20!%3D%20Resolved%20OR%20Resolution%20!%3D%20Fixed)%20AND%20fixVersion%20%3D%20v1.7.0
>
> Please review/submit a patch.
>
> In the second iteration we will look at issues that have patches attached
> to them but haven't been reviewed.
>
> Thanks!
>
> On Tue, Jun 14, 2016 at 8:56 AM, Hari Shreedharan <hshreedha...@apache.org
> > wrote:
>
>> Sure. I can help with the release. My time to work on this would be
>> limited, so it might take me a day or two between updates.
>> On Mon, Jun 13, 2016 at 9:29 PM Saikat Kanjilal <sxk1...@hotmail.com>
>> wrote:
>>
>> > 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 :)
>> > >

[jira] [Created] (FLUME-2924) Flume 1.7.0 release

[Lior Zeno (JIRA)]

Lior Zeno created FLUME-2924:


 Summary: Flume 1.7.0 release
 Key: FLUME-2924
 URL: https://issues.apache.org/jira/browse/FLUME-2924
 Project: Flume
  Issue Type: Umbrella
Affects Versions: v1.7.0
Reporter: Lior Zeno


Release 1.7.0 umbrella issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Flume 1.7.0 release

[Lior Zeno]

Hi guys,

We still have the following issues to resolve in order to release:
https://issues.apache.org/jira/browse/FLUME-2340?jql=project%20%3D%20Flume%20AND%20(Status%20!%3D%20Resolved%20OR%20Resolution%20!%3D%20Fixed)%20AND%20fixVersion%20%3D%20v1.7.0

Please review/submit a patch.

In the second iteration we will look at issues that have patches attached
to them but haven't been reviewed.

Thanks!

On Tue, Jun 14, 2016 at 8:56 AM, Hari Shreedharan <hshreedha...@apache.org>
wrote:

> Sure. I can help with the release. My time to work on this would be
> limited, so it might take me a day or two between updates.
> On Mon, Jun 13, 2016 at 9:29 PM Saikat Kanjilal <sxk1...@hotmail.com>
> wrote:
>
> > 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
> > >>>>&g

Re: Flume 1.7.0 release

[Hari Shreedharan]

Sure. I can help with the release. My time to work on this would be
limited, so it might take me a day or two between updates.
On Mon, Jun 13, 2016 at 9:29 PM Saikat Kanjilal <sxk1...@hotmail.com> wrote:

> 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
> >>>>>>>

Re: Flume 1.7.0 release

[Saikat Kanjilal]

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
>>>>

Re: Flume 1.7.0 release

[Hari Shreedharan]

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
> > >> >

RE: Flume 1.7.0 release

[Saikat Kanjilal]

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 peo

Re: Flume 1.7.0 release

[Lior Zeno]

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
>> feat

Re: Flume 1.7.0 release

[Lior Zeno]

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
> > > > >>
> > >
> > >
> >
>

Re: Flume 1.7.0 release

[Attila Simon]

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
> > >>
>
>

RE: Flume 1.7.0 release

[Saikat Kanjilal]

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
> >>
  

Re: Flume 1.7.0 release

[Lior Zeno]

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  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 
> 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  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  wrote:
>
> Anybody?
>
>> On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  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
>>

Re: Flume 1.7.0 release

[Saikat Kanjilal]

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  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 
> 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  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  wrote:
> 
> Anybody?
> 
>> On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  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
>> 

Re: Flume 1.7.0 release

[Saikat Kanjilal]

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  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 
> 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  wrote:
>>> 
>>> Anybody?
>>> 
 On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  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
>> 

Re: Flume 1.7.0 release

[Lior Zeno]

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 
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  wrote:
>
> > Anybody?
> >
> > On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  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
> > >
> >
>

Re: Flume 1.7.0 release

[Hari Shreedharan]

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  wrote:

> Anybody?
>
> On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  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
> >
>

Re: Flume 1.7.0 release

[Lior Zeno]

Anybody?

On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno  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
>

Flume 1.7.0 release

[Lior Zeno]

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