You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Balazs Donat Bessenyei <be...@cloudera.com> on 2016/09/30 08:46:08 UTC
[DISCUSS] Flume 1.7 release plan
Hi All,
We have almost 100 commits since 1.6.0, and a bunch of new features
and improvements including a Taildir Source, many upgrades,
performance increases, plus a lot of fixes and documentation
additions.
It seems to me that it's time to cut a 1.7 release soon. I would be
happy to volunteer to RM or co-RM the release (possibly together with
Lior Zeno who has previously volunteered for such).
I know that we have already had a discussion about this. However, as
progress seems to have slowed down recently, I suggest re-triaging the
tickets to unblock the release and moving forward with the release
process right away.
Below is the list of tickets that have patches submitted and are
scheduled for 1.7.0:
https://issues.apache.org/jira/browse/FLUME-2998?jql=project%20%3D%20FLUME%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.7.0
(18 tickets)
There are more tickets that have no patch submitted:
https://issues.apache.org/jira/browse/FLUME-2998?jql=project%20%3D%20FLUME%20AND%20issuetype%20in%20standardIssueTypes()%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.7.0
(30 tickets)
I suggest tracking the release process using the JIRA previously filed
by Lior at https://issues.apache.org/jira/browse/FLUME-2924
If this all sounds OK, I'd like to suggest targeting the week of
October 10 for a first RC. (Also, anything that is non-trivial should
get in by October 7. Any feature or big change that is not committed
by then would be scheduled for the next release.)
That should leave enough time for people to get moving on patches and
reviews for their documentation improvements, critical bug fixes, and
low-risk enhancements, etc.
Also, I would like to propose October 7 (one week from today) for the
branch date.
Please let me know your thoughts.
Best Regards,
Donat
Re: [DISCUSS] Flume 1.7 release plan
Posted by Balazs Donat Bessenyei <be...@cloudera.com>.
Hi All,
I moved all the open 1.7 tickets to 1.8, branched 1.7 and pushed the
tag release-1.7.0-rc1
I am going to create the rc1 release artifacts in the next 12 hours
and I'll start a vote thread at that time.
Donat
On Fri, Oct 7, 2016 at 2:05 PM, Mike Percy <mp...@apache.org> wrote:
> +1 from me, keep up the good work guys.
>
> Mike
>
> On Fri, Oct 7, 2016 at 12:59 PM, Balazs Donat Bessenyei <bessbd@cloudera.com
>> wrote:
>
>> Considering Attila's request, I'll do the branching on Monday and the
>> first RC soon after that.
>>
>> Is that okay for everyone?
>>
>>
>> Thank you,
>>
>> Donat
>>
>> On Fri, Oct 7, 2016 at 12:53 PM, Attila Simon <sa...@cloudera.com> wrote:
>> > Hi,
>> >
>> > Since we have a few patches in flight from me,Tristan,etc let me suggest
>> > giving the weekend for code review rounds and branch on Monday.
>> >
>> > Cheers,
>> > Attila
>> >
>> >
>> > *Attila Simon*
>> > Software Engineer
>> > Email: sati@cloudera.com
>> >
>> > [image: Cloudera Inc.]
>> >
>> > On Thu, Oct 6, 2016 at 12:05 PM, Balazs Donat Bessenyei <
>> bessbd@cloudera.com
>> >> wrote:
>> >
>> >> Thank you all for the responses.
>> >>
>> >> @Lior: I have reviewed the change you have mentioned (FLUME-2994). If
>> >> we manage to have the code done and +1/2-d soon, I'll commit the
>> >> patch.
>> >>
>> >> @Denes: the change looks good to me. I'll leave some time for others
>> >> to review, though.
>> >>
>> >> @Saikat: I've wanted to put integrations in the User Guide for Flume
>> >> for so long. For example Flume with Spark (
>> >> http://spark.apache.org/docs/latest/streaming-flume-integration.html
>> >> ).
>> >> I know it is available on the internet and I don't think we should
>> >> increase redundancy this way, but I'd really like to have such
>> >> examples in the docs.
>> >> What do you all think of this?
>> >>
>> >> Misc: any help with the tickets I've mentioned in my last e-mail would
>> >> be super welcome. (Even just triaging them and maybe deciding if they
>> >> are not that important as I first thought.)
>> >>
>> >>
>> >> Thank you,
>> >>
>> >> Donat
>> >>
>> >> On Wed, Oct 5, 2016 at 2:03 AM, Hari Shreedharan
>> >> <hs...@apache.org> wrote:
>> >> > +1 for the release, and the branching and RC dates
>> >> >
>> >> > On Tue, Oct 4, 2016 at 10:54 AM Saikat Kanjilal <sx...@hotmail.com>
>> >> wrote:
>> >> >
>> >> >> Hi Donat,
>> >> >>
>> >> >> I can pickup any documentation related issues, are there anymore at
>> this
>> >> >> point outside of the FLUME-2971, I would be willing to pickup one of
>> the
>> >> >> ones below but cant guarantee that it'll be fixed in the timeframe
>> for
>> >> 1.7
>> >> >> , let me know the best path for helping.
>> >> >>
>> >> >> Thanks
>> >> >>
>> >> >>
>> >> >> ________________________________
>> >> >> From: Balazs Donat Bessenyei <be...@cloudera.com>
>> >> >> Sent: Tuesday, October 4, 2016 8:01 AM
>> >> >> To: dev@flume.apache.org
>> >> >> Subject: Re: [DISCUSS] Flume 1.7 release plan
>> >> >>
>> >> >> As there have been no objections, I am going to proceed with the plan
>> >> >> I have outlined in my original mail.
>> >> >>
>> >> >> I will try to work a little more on some flaky tests to help with the
>> >> >> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
>> >> >> are flaky.)
>> >> >>
>> >> >> It would be awesome if someone could fix FLUME-2971 (Document
>> Kerberos
>> >> >> set-up for Kafka Sink and Kafka Source).
>> >> >>
>> >> >> Also, I have found a few more tickets that could use a little care:
>> >> >> FLUME-2689 (reloading conf file leads syslogTcpSource not receives
>> any
>> >> >> event) - probably only needs some more reviews,
>> >> >> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
>> >> >> missing a test,
>> >> >> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing
>> test
>> >> >> Patch-less (Needs some investigation and a fix. I am not sure about
>> >> >> their complexity):
>> >> >> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
>> >> >> principal in format with hostname)
>> >> >> FLUME-2871 (avro sink reset-connection-interval cause
>> >> >> EventDeliveryException)
>> >> >> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
>> >> >>
>> >> >> However, none of these seem to be a release blocker, so if they are
>> >> >> not done by Oct 7-10, it would still be fine.
>> >> >>
>> >> >>
>> >> >> Please, let me know your thoughts
>> >> >>
>> >> >> Donat
>> >> >>
>> >> >> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org>
>> wrote:
>> >> >> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <
>> sxk1969@hotmail.com
>> >> >
>> >> >> > wrote:
>> >> >> >
>> >> >> >> I'd be willing to help, I've been heads down on other stuff and
>> have
>> >> had
>> >> >> >> to postpone the graph sink implementation (
>> >> https://issues.apache.org/
>> >> >> >> jira/browse/FLUME-2035) but am looking to resume work and
>> targeting
>> >> an
>> >> >> >> initial implementation by mid November sometime. In the meantime
>> >> let me
>> >> >> >> know how I can get more deeply involved in the next release.
>> >> >> >>
>> >> >> >
>> >> >> > I'd recommend taking a look at things like documentation and
>> filling
>> >> in
>> >> >> > gaps so that we don't release with undocumented stuff. Other types
>> of
>> >> >> > polish seem like a helpful thing to do right before a release as
>> well.
>> >> >> >
>> >> >> > Mike
>> >> >>
>> >>
>>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Mike Percy <mp...@apache.org>.
+1 from me, keep up the good work guys.
Mike
On Fri, Oct 7, 2016 at 12:59 PM, Balazs Donat Bessenyei <bessbd@cloudera.com
> wrote:
> Considering Attila's request, I'll do the branching on Monday and the
> first RC soon after that.
>
> Is that okay for everyone?
>
>
> Thank you,
>
> Donat
>
> On Fri, Oct 7, 2016 at 12:53 PM, Attila Simon <sa...@cloudera.com> wrote:
> > Hi,
> >
> > Since we have a few patches in flight from me,Tristan,etc let me suggest
> > giving the weekend for code review rounds and branch on Monday.
> >
> > Cheers,
> > Attila
> >
> >
> > *Attila Simon*
> > Software Engineer
> > Email: sati@cloudera.com
> >
> > [image: Cloudera Inc.]
> >
> > On Thu, Oct 6, 2016 at 12:05 PM, Balazs Donat Bessenyei <
> bessbd@cloudera.com
> >> wrote:
> >
> >> Thank you all for the responses.
> >>
> >> @Lior: I have reviewed the change you have mentioned (FLUME-2994). If
> >> we manage to have the code done and +1/2-d soon, I'll commit the
> >> patch.
> >>
> >> @Denes: the change looks good to me. I'll leave some time for others
> >> to review, though.
> >>
> >> @Saikat: I've wanted to put integrations in the User Guide for Flume
> >> for so long. For example Flume with Spark (
> >> http://spark.apache.org/docs/latest/streaming-flume-integration.html
> >> ).
> >> I know it is available on the internet and I don't think we should
> >> increase redundancy this way, but I'd really like to have such
> >> examples in the docs.
> >> What do you all think of this?
> >>
> >> Misc: any help with the tickets I've mentioned in my last e-mail would
> >> be super welcome. (Even just triaging them and maybe deciding if they
> >> are not that important as I first thought.)
> >>
> >>
> >> Thank you,
> >>
> >> Donat
> >>
> >> On Wed, Oct 5, 2016 at 2:03 AM, Hari Shreedharan
> >> <hs...@apache.org> wrote:
> >> > +1 for the release, and the branching and RC dates
> >> >
> >> > On Tue, Oct 4, 2016 at 10:54 AM Saikat Kanjilal <sx...@hotmail.com>
> >> wrote:
> >> >
> >> >> Hi Donat,
> >> >>
> >> >> I can pickup any documentation related issues, are there anymore at
> this
> >> >> point outside of the FLUME-2971, I would be willing to pickup one of
> the
> >> >> ones below but cant guarantee that it'll be fixed in the timeframe
> for
> >> 1.7
> >> >> , let me know the best path for helping.
> >> >>
> >> >> Thanks
> >> >>
> >> >>
> >> >> ________________________________
> >> >> From: Balazs Donat Bessenyei <be...@cloudera.com>
> >> >> Sent: Tuesday, October 4, 2016 8:01 AM
> >> >> To: dev@flume.apache.org
> >> >> Subject: Re: [DISCUSS] Flume 1.7 release plan
> >> >>
> >> >> As there have been no objections, I am going to proceed with the plan
> >> >> I have outlined in my original mail.
> >> >>
> >> >> I will try to work a little more on some flaky tests to help with the
> >> >> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
> >> >> are flaky.)
> >> >>
> >> >> It would be awesome if someone could fix FLUME-2971 (Document
> Kerberos
> >> >> set-up for Kafka Sink and Kafka Source).
> >> >>
> >> >> Also, I have found a few more tickets that could use a little care:
> >> >> FLUME-2689 (reloading conf file leads syslogTcpSource not receives
> any
> >> >> event) - probably only needs some more reviews,
> >> >> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
> >> >> missing a test,
> >> >> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing
> test
> >> >> Patch-less (Needs some investigation and a fix. I am not sure about
> >> >> their complexity):
> >> >> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
> >> >> principal in format with hostname)
> >> >> FLUME-2871 (avro sink reset-connection-interval cause
> >> >> EventDeliveryException)
> >> >> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
> >> >>
> >> >> However, none of these seem to be a release blocker, so if they are
> >> >> not done by Oct 7-10, it would still be fine.
> >> >>
> >> >>
> >> >> Please, let me know your thoughts
> >> >>
> >> >> Donat
> >> >>
> >> >> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org>
> wrote:
> >> >> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <
> sxk1969@hotmail.com
> >> >
> >> >> > wrote:
> >> >> >
> >> >> >> I'd be willing to help, I've been heads down on other stuff and
> have
> >> had
> >> >> >> to postpone the graph sink implementation (
> >> https://issues.apache.org/
> >> >> >> jira/browse/FLUME-2035) but am looking to resume work and
> targeting
> >> an
> >> >> >> initial implementation by mid November sometime. In the meantime
> >> let me
> >> >> >> know how I can get more deeply involved in the next release.
> >> >> >>
> >> >> >
> >> >> > I'd recommend taking a look at things like documentation and
> filling
> >> in
> >> >> > gaps so that we don't release with undocumented stuff. Other types
> of
> >> >> > polish seem like a helpful thing to do right before a release as
> well.
> >> >> >
> >> >> > Mike
> >> >>
> >>
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Balazs Donat Bessenyei <be...@cloudera.com>.
Considering Attila's request, I'll do the branching on Monday and the
first RC soon after that.
Is that okay for everyone?
Thank you,
Donat
On Fri, Oct 7, 2016 at 12:53 PM, Attila Simon <sa...@cloudera.com> wrote:
> Hi,
>
> Since we have a few patches in flight from me,Tristan,etc let me suggest
> giving the weekend for code review rounds and branch on Monday.
>
> Cheers,
> Attila
>
>
> *Attila Simon*
> Software Engineer
> Email: sati@cloudera.com
>
> [image: Cloudera Inc.]
>
> On Thu, Oct 6, 2016 at 12:05 PM, Balazs Donat Bessenyei <bessbd@cloudera.com
>> wrote:
>
>> Thank you all for the responses.
>>
>> @Lior: I have reviewed the change you have mentioned (FLUME-2994). If
>> we manage to have the code done and +1/2-d soon, I'll commit the
>> patch.
>>
>> @Denes: the change looks good to me. I'll leave some time for others
>> to review, though.
>>
>> @Saikat: I've wanted to put integrations in the User Guide for Flume
>> for so long. For example Flume with Spark (
>> http://spark.apache.org/docs/latest/streaming-flume-integration.html
>> ).
>> I know it is available on the internet and I don't think we should
>> increase redundancy this way, but I'd really like to have such
>> examples in the docs.
>> What do you all think of this?
>>
>> Misc: any help with the tickets I've mentioned in my last e-mail would
>> be super welcome. (Even just triaging them and maybe deciding if they
>> are not that important as I first thought.)
>>
>>
>> Thank you,
>>
>> Donat
>>
>> On Wed, Oct 5, 2016 at 2:03 AM, Hari Shreedharan
>> <hs...@apache.org> wrote:
>> > +1 for the release, and the branching and RC dates
>> >
>> > On Tue, Oct 4, 2016 at 10:54 AM Saikat Kanjilal <sx...@hotmail.com>
>> wrote:
>> >
>> >> Hi Donat,
>> >>
>> >> I can pickup any documentation related issues, are there anymore at this
>> >> point outside of the FLUME-2971, I would be willing to pickup one of the
>> >> ones below but cant guarantee that it'll be fixed in the timeframe for
>> 1.7
>> >> , let me know the best path for helping.
>> >>
>> >> Thanks
>> >>
>> >>
>> >> ________________________________
>> >> From: Balazs Donat Bessenyei <be...@cloudera.com>
>> >> Sent: Tuesday, October 4, 2016 8:01 AM
>> >> To: dev@flume.apache.org
>> >> Subject: Re: [DISCUSS] Flume 1.7 release plan
>> >>
>> >> As there have been no objections, I am going to proceed with the plan
>> >> I have outlined in my original mail.
>> >>
>> >> I will try to work a little more on some flaky tests to help with the
>> >> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
>> >> are flaky.)
>> >>
>> >> It would be awesome if someone could fix FLUME-2971 (Document Kerberos
>> >> set-up for Kafka Sink and Kafka Source).
>> >>
>> >> Also, I have found a few more tickets that could use a little care:
>> >> FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
>> >> event) - probably only needs some more reviews,
>> >> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
>> >> missing a test,
>> >> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
>> >> Patch-less (Needs some investigation and a fix. I am not sure about
>> >> their complexity):
>> >> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
>> >> principal in format with hostname)
>> >> FLUME-2871 (avro sink reset-connection-interval cause
>> >> EventDeliveryException)
>> >> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
>> >>
>> >> However, none of these seem to be a release blocker, so if they are
>> >> not done by Oct 7-10, it would still be fine.
>> >>
>> >>
>> >> Please, let me know your thoughts
>> >>
>> >> Donat
>> >>
>> >> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
>> >> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sxk1969@hotmail.com
>> >
>> >> > wrote:
>> >> >
>> >> >> I'd be willing to help, I've been heads down on other stuff and have
>> had
>> >> >> to postpone the graph sink implementation (
>> https://issues.apache.org/
>> >> >> jira/browse/FLUME-2035) but am looking to resume work and targeting
>> an
>> >> >> initial implementation by mid November sometime. In the meantime
>> let me
>> >> >> know how I can get more deeply involved in the next release.
>> >> >>
>> >> >
>> >> > I'd recommend taking a look at things like documentation and filling
>> in
>> >> > gaps so that we don't release with undocumented stuff. Other types of
>> >> > polish seem like a helpful thing to do right before a release as well.
>> >> >
>> >> > Mike
>> >>
>>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Attila Simon <sa...@cloudera.com>.
Hi,
Since we have a few patches in flight from me,Tristan,etc let me suggest
giving the weekend for code review rounds and branch on Monday.
Cheers,
Attila
*Attila Simon*
Software Engineer
Email: sati@cloudera.com
[image: Cloudera Inc.]
On Thu, Oct 6, 2016 at 12:05 PM, Balazs Donat Bessenyei <bessbd@cloudera.com
> wrote:
> Thank you all for the responses.
>
> @Lior: I have reviewed the change you have mentioned (FLUME-2994). If
> we manage to have the code done and +1/2-d soon, I'll commit the
> patch.
>
> @Denes: the change looks good to me. I'll leave some time for others
> to review, though.
>
> @Saikat: I've wanted to put integrations in the User Guide for Flume
> for so long. For example Flume with Spark (
> http://spark.apache.org/docs/latest/streaming-flume-integration.html
> ).
> I know it is available on the internet and I don't think we should
> increase redundancy this way, but I'd really like to have such
> examples in the docs.
> What do you all think of this?
>
> Misc: any help with the tickets I've mentioned in my last e-mail would
> be super welcome. (Even just triaging them and maybe deciding if they
> are not that important as I first thought.)
>
>
> Thank you,
>
> Donat
>
> On Wed, Oct 5, 2016 at 2:03 AM, Hari Shreedharan
> <hs...@apache.org> wrote:
> > +1 for the release, and the branching and RC dates
> >
> > On Tue, Oct 4, 2016 at 10:54 AM Saikat Kanjilal <sx...@hotmail.com>
> wrote:
> >
> >> Hi Donat,
> >>
> >> I can pickup any documentation related issues, are there anymore at this
> >> point outside of the FLUME-2971, I would be willing to pickup one of the
> >> ones below but cant guarantee that it'll be fixed in the timeframe for
> 1.7
> >> , let me know the best path for helping.
> >>
> >> Thanks
> >>
> >>
> >> ________________________________
> >> From: Balazs Donat Bessenyei <be...@cloudera.com>
> >> Sent: Tuesday, October 4, 2016 8:01 AM
> >> To: dev@flume.apache.org
> >> Subject: Re: [DISCUSS] Flume 1.7 release plan
> >>
> >> As there have been no objections, I am going to proceed with the plan
> >> I have outlined in my original mail.
> >>
> >> I will try to work a little more on some flaky tests to help with the
> >> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
> >> are flaky.)
> >>
> >> It would be awesome if someone could fix FLUME-2971 (Document Kerberos
> >> set-up for Kafka Sink and Kafka Source).
> >>
> >> Also, I have found a few more tickets that could use a little care:
> >> FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
> >> event) - probably only needs some more reviews,
> >> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
> >> missing a test,
> >> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
> >> Patch-less (Needs some investigation and a fix. I am not sure about
> >> their complexity):
> >> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
> >> principal in format with hostname)
> >> FLUME-2871 (avro sink reset-connection-interval cause
> >> EventDeliveryException)
> >> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
> >>
> >> However, none of these seem to be a release blocker, so if they are
> >> not done by Oct 7-10, it would still be fine.
> >>
> >>
> >> Please, let me know your thoughts
> >>
> >> Donat
> >>
> >> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
> >> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sxk1969@hotmail.com
> >
> >> > wrote:
> >> >
> >> >> I'd be willing to help, I've been heads down on other stuff and have
> had
> >> >> to postpone the graph sink implementation (
> https://issues.apache.org/
> >> >> jira/browse/FLUME-2035) but am looking to resume work and targeting
> an
> >> >> initial implementation by mid November sometime. In the meantime
> let me
> >> >> know how I can get more deeply involved in the next release.
> >> >>
> >> >
> >> > I'd recommend taking a look at things like documentation and filling
> in
> >> > gaps so that we don't release with undocumented stuff. Other types of
> >> > polish seem like a helpful thing to do right before a release as well.
> >> >
> >> > Mike
> >>
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Balazs Donat Bessenyei <be...@cloudera.com>.
Thank you all for the responses.
@Lior: I have reviewed the change you have mentioned (FLUME-2994). If
we manage to have the code done and +1/2-d soon, I'll commit the
patch.
@Denes: the change looks good to me. I'll leave some time for others
to review, though.
@Saikat: I've wanted to put integrations in the User Guide for Flume
for so long. For example Flume with Spark (
http://spark.apache.org/docs/latest/streaming-flume-integration.html
).
I know it is available on the internet and I don't think we should
increase redundancy this way, but I'd really like to have such
examples in the docs.
What do you all think of this?
Misc: any help with the tickets I've mentioned in my last e-mail would
be super welcome. (Even just triaging them and maybe deciding if they
are not that important as I first thought.)
Thank you,
Donat
On Wed, Oct 5, 2016 at 2:03 AM, Hari Shreedharan
<hs...@apache.org> wrote:
> +1 for the release, and the branching and RC dates
>
> On Tue, Oct 4, 2016 at 10:54 AM Saikat Kanjilal <sx...@hotmail.com> wrote:
>
>> Hi Donat,
>>
>> I can pickup any documentation related issues, are there anymore at this
>> point outside of the FLUME-2971, I would be willing to pickup one of the
>> ones below but cant guarantee that it'll be fixed in the timeframe for 1.7
>> , let me know the best path for helping.
>>
>> Thanks
>>
>>
>> ________________________________
>> From: Balazs Donat Bessenyei <be...@cloudera.com>
>> Sent: Tuesday, October 4, 2016 8:01 AM
>> To: dev@flume.apache.org
>> Subject: Re: [DISCUSS] Flume 1.7 release plan
>>
>> As there have been no objections, I am going to proceed with the plan
>> I have outlined in my original mail.
>>
>> I will try to work a little more on some flaky tests to help with the
>> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
>> are flaky.)
>>
>> It would be awesome if someone could fix FLUME-2971 (Document Kerberos
>> set-up for Kafka Sink and Kafka Source).
>>
>> Also, I have found a few more tickets that could use a little care:
>> FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
>> event) - probably only needs some more reviews,
>> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
>> missing a test,
>> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
>> Patch-less (Needs some investigation and a fix. I am not sure about
>> their complexity):
>> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
>> principal in format with hostname)
>> FLUME-2871 (avro sink reset-connection-interval cause
>> EventDeliveryException)
>> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
>>
>> However, none of these seem to be a release blocker, so if they are
>> not done by Oct 7-10, it would still be fine.
>>
>>
>> Please, let me know your thoughts
>>
>> Donat
>>
>> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
>> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
>> > wrote:
>> >
>> >> I'd be willing to help, I've been heads down on other stuff and have had
>> >> to postpone the graph sink implementation (https://issues.apache.org/
>> >> jira/browse/FLUME-2035) but am looking to resume work and targeting an
>> >> initial implementation by mid November sometime. In the meantime let me
>> >> know how I can get more deeply involved in the next release.
>> >>
>> >
>> > I'd recommend taking a look at things like documentation and filling in
>> > gaps so that we don't release with undocumented stuff. Other types of
>> > polish seem like a helpful thing to do right before a release as well.
>> >
>> > Mike
>>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Hari Shreedharan <hs...@apache.org>.
+1 for the release, and the branching and RC dates
On Tue, Oct 4, 2016 at 10:54 AM Saikat Kanjilal <sx...@hotmail.com> wrote:
> Hi Donat,
>
> I can pickup any documentation related issues, are there anymore at this
> point outside of the FLUME-2971, I would be willing to pickup one of the
> ones below but cant guarantee that it'll be fixed in the timeframe for 1.7
> , let me know the best path for helping.
>
> Thanks
>
>
> ________________________________
> From: Balazs Donat Bessenyei <be...@cloudera.com>
> Sent: Tuesday, October 4, 2016 8:01 AM
> To: dev@flume.apache.org
> Subject: Re: [DISCUSS] Flume 1.7 release plan
>
> As there have been no objections, I am going to proceed with the plan
> I have outlined in my original mail.
>
> I will try to work a little more on some flaky tests to help with the
> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
> are flaky.)
>
> It would be awesome if someone could fix FLUME-2971 (Document Kerberos
> set-up for Kafka Sink and Kafka Source).
>
> Also, I have found a few more tickets that could use a little care:
> FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
> event) - probably only needs some more reviews,
> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
> missing a test,
> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
> Patch-less (Needs some investigation and a fix. I am not sure about
> their complexity):
> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
> principal in format with hostname)
> FLUME-2871 (avro sink reset-connection-interval cause
> EventDeliveryException)
> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
>
> However, none of these seem to be a release blocker, so if they are
> not done by Oct 7-10, it would still be fine.
>
>
> Please, let me know your thoughts
>
> Donat
>
> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
> > wrote:
> >
> >> I'd be willing to help, I've been heads down on other stuff and have had
> >> to postpone the graph sink implementation (https://issues.apache.org/
> >> jira/browse/FLUME-2035) but am looking to resume work and targeting an
> >> initial implementation by mid November sometime. In the meantime let me
> >> know how I can get more deeply involved in the next release.
> >>
> >
> > I'd recommend taking a look at things like documentation and filling in
> > gaps so that we don't release with undocumented stuff. Other types of
> > polish seem like a helpful thing to do right before a release as well.
> >
> > Mike
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Saikat Kanjilal <sx...@hotmail.com>.
Hi Donat,
I can pickup any documentation related issues, are there anymore at this point outside of the FLUME-2971, I would be willing to pickup one of the ones below but cant guarantee that it'll be fixed in the timeframe for 1.7 , let me know the best path for helping.
Thanks
________________________________
From: Balazs Donat Bessenyei <be...@cloudera.com>
Sent: Tuesday, October 4, 2016 8:01 AM
To: dev@flume.apache.org
Subject: Re: [DISCUSS] Flume 1.7 release plan
As there have been no objections, I am going to proceed with the plan
I have outlined in my original mail.
I will try to work a little more on some flaky tests to help with the
release process. (Such as FLUME-3002: Some tests in TestBucketWriter
are flaky.)
It would be awesome if someone could fix FLUME-2971 (Document Kerberos
set-up for Kafka Sink and Kafka Source).
Also, I have found a few more tickets that could use a little care:
FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
event) - probably only needs some more reviews,
FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
missing a test,
FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
Patch-less (Needs some investigation and a fix. I am not sure about
their complexity):
FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
principal in format with hostname)
FLUME-2871 (avro sink reset-connection-interval cause EventDeliveryException)
FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
However, none of these seem to be a release blocker, so if they are
not done by Oct 7-10, it would still be fine.
Please, let me know your thoughts
Donat
On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
> On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
> wrote:
>
>> I'd be willing to help, I've been heads down on other stuff and have had
>> to postpone the graph sink implementation (https://issues.apache.org/
>> jira/browse/FLUME-2035) but am looking to resume work and targeting an
>> initial implementation by mid November sometime. In the meantime let me
>> know how I can get more deeply involved in the next release.
>>
>
> I'd recommend taking a look at things like documentation and filling in
> gaps so that we don't release with undocumented stuff. Other types of
> polish seem like a helpful thing to do right before a release as well.
>
> Mike
Re: [DISCUSS] Flume 1.7 release plan
Posted by Denes Arvay <de...@cloudera.com>.
Hi All,
Donat, thanks for the list. I'd like add FLUME-3003 (flaky test in
TestSyslogUdpSource) to it, patch submitted, review in progress.
Lior, I already started to review the FLUME-2994, I have a windows
environment set up to validate it, I'm happy to do it, so +1 from me for
including it in the release.
I can also have a look on FLUME-2461 (memoryChannel bytesRemaining counting
error).
Cheers,
Denes
On Tue, Oct 4, 2016 at 5:14 PM Lior Zeno <li...@gmail.com> wrote:
> I would love to see FLUME-2994 getting into the release (low-hanging
> fruit).
>
> On Tue, Oct 4, 2016 at 6:01 PM, Balazs Donat Bessenyei <
> bessbd@cloudera.com>
> wrote:
>
> > As there have been no objections, I am going to proceed with the plan
> > I have outlined in my original mail.
> >
> > I will try to work a little more on some flaky tests to help with the
> > release process. (Such as FLUME-3002: Some tests in TestBucketWriter
> > are flaky.)
> >
> > It would be awesome if someone could fix FLUME-2971 (Document Kerberos
> > set-up for Kafka Sink and Kafka Source).
> >
> > Also, I have found a few more tickets that could use a little care:
> > FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
> > event) - probably only needs some more reviews,
> > FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
> > missing a test,
> > FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
> > Patch-less (Needs some investigation and a fix. I am not sure about
> > their complexity):
> > FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
> > principal in format with hostname)
> > FLUME-2871 (avro sink reset-connection-interval cause
> > EventDeliveryException)
> > FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
> >
> > However, none of these seem to be a release blocker, so if they are
> > not done by Oct 7-10, it would still be fine.
> >
> >
> > Please, let me know your thoughts
> >
> > Donat
> >
> > On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
> > > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
> > > wrote:
> > >
> > >> I'd be willing to help, I've been heads down on other stuff and have
> had
> > >> to postpone the graph sink implementation (https://issues.apache.org/
> > >> jira/browse/FLUME-2035) but am looking to resume work and targeting an
> > >> initial implementation by mid November sometime. In the meantime let
> me
> > >> know how I can get more deeply involved in the next release.
> > >>
> > >
> > > I'd recommend taking a look at things like documentation and filling in
> > > gaps so that we don't release with undocumented stuff. Other types of
> > > polish seem like a helpful thing to do right before a release as well.
> > >
> > > Mike
> >
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Lior Zeno <li...@gmail.com>.
I would love to see FLUME-2994 getting into the release (low-hanging fruit).
On Tue, Oct 4, 2016 at 6:01 PM, Balazs Donat Bessenyei <be...@cloudera.com>
wrote:
> As there have been no objections, I am going to proceed with the plan
> I have outlined in my original mail.
>
> I will try to work a little more on some flaky tests to help with the
> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
> are flaky.)
>
> It would be awesome if someone could fix FLUME-2971 (Document Kerberos
> set-up for Kafka Sink and Kafka Source).
>
> Also, I have found a few more tickets that could use a little care:
> FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
> event) - probably only needs some more reviews,
> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
> missing a test,
> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
> Patch-less (Needs some investigation and a fix. I am not sure about
> their complexity):
> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
> principal in format with hostname)
> FLUME-2871 (avro sink reset-connection-interval cause
> EventDeliveryException)
> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
>
> However, none of these seem to be a release blocker, so if they are
> not done by Oct 7-10, it would still be fine.
>
>
> Please, let me know your thoughts
>
> Donat
>
> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
> > wrote:
> >
> >> I'd be willing to help, I've been heads down on other stuff and have had
> >> to postpone the graph sink implementation (https://issues.apache.org/
> >> jira/browse/FLUME-2035) but am looking to resume work and targeting an
> >> initial implementation by mid November sometime. In the meantime let me
> >> know how I can get more deeply involved in the next release.
> >>
> >
> > I'd recommend taking a look at things like documentation and filling in
> > gaps so that we don't release with undocumented stuff. Other types of
> > polish seem like a helpful thing to do right before a release as well.
> >
> > Mike
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Attila Simon <sa...@cloudera.com>.
Hi,
Awesome. I just recently picked up FLUME-2971.
Cheers,
Attila
On Tue, Oct 4, 2016 at 5:01 PM, Balazs Donat Bessenyei <be...@cloudera.com>
wrote:
> As there have been no objections, I am going to proceed with the plan
> I have outlined in my original mail.
>
> I will try to work a little more on some flaky tests to help with the
> release process. (Such as FLUME-3002: Some tests in TestBucketWriter
> are flaky.)
>
> It would be awesome if someone could fix FLUME-2971 (Document Kerberos
> set-up for Kafka Sink and Kafka Source).
>
> Also, I have found a few more tickets that could use a little care:
> FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
> event) - probably only needs some more reviews,
> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
> missing a test,
> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
> Patch-less (Needs some investigation and a fix. I am not sure about
> their complexity):
> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
> principal in format with hostname)
> FLUME-2871 (avro sink reset-connection-interval cause
> EventDeliveryException)
> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
>
> However, none of these seem to be a release blocker, so if they are
> not done by Oct 7-10, it would still be fine.
>
>
> Please, let me know your thoughts
>
> Donat
>
> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
> > wrote:
> >
> >> I'd be willing to help, I've been heads down on other stuff and have had
> >> to postpone the graph sink implementation (https://issues.apache.org/
> >> jira/browse/FLUME-2035) but am looking to resume work and targeting an
> >> initial implementation by mid November sometime. In the meantime let me
> >> know how I can get more deeply involved in the next release.
> >>
> >
> > I'd recommend taking a look at things like documentation and filling in
> > gaps so that we don't release with undocumented stuff. Other types of
> > polish seem like a helpful thing to do right before a release as well.
> >
> > Mike
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Balazs Donat Bessenyei <be...@cloudera.com>.
As there have been no objections, I am going to proceed with the plan
I have outlined in my original mail.
I will try to work a little more on some flaky tests to help with the
release process. (Such as FLUME-3002: Some tests in TestBucketWriter
are flaky.)
It would be awesome if someone could fix FLUME-2971 (Document Kerberos
set-up for Kafka Sink and Kafka Source).
Also, I have found a few more tickets that could use a little care:
FLUME-2689 (reloading conf file leads syslogTcpSource not receives any
event) - probably only needs some more reviews,
FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) -
missing a test,
FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test
Patch-less (Needs some investigation and a fix. I am not sure about
their complexity):
FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos
principal in format with hostname)
FLUME-2871 (avro sink reset-connection-interval cause EventDeliveryException)
FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown)
However, none of these seem to be a release blocker, so if they are
not done by Oct 7-10, it would still be fine.
Please, let me know your thoughts
Donat
On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mp...@apache.org> wrote:
> On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
> wrote:
>
>> I'd be willing to help, I've been heads down on other stuff and have had
>> to postpone the graph sink implementation (https://issues.apache.org/
>> jira/browse/FLUME-2035) but am looking to resume work and targeting an
>> initial implementation by mid November sometime. In the meantime let me
>> know how I can get more deeply involved in the next release.
>>
>
> I'd recommend taking a look at things like documentation and filling in
> gaps so that we don't release with undocumented stuff. Other types of
> polish seem like a helpful thing to do right before a release as well.
>
> Mike
Re: [DISCUSS] Flume 1.7 release plan
Posted by Mike Percy <mp...@apache.org>.
On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sx...@hotmail.com>
wrote:
> I'd be willing to help, I've been heads down on other stuff and have had
> to postpone the graph sink implementation (https://issues.apache.org/
> jira/browse/FLUME-2035) but am looking to resume work and targeting an
> initial implementation by mid November sometime. In the meantime let me
> know how I can get more deeply involved in the next release.
>
I'd recommend taking a look at things like documentation and filling in
gaps so that we don't release with undocumented stuff. Other types of
polish seem like a helpful thing to do right before a release as well.
Mike
Re: [DISCUSS] Flume 1.7 release plan
Posted by Balazs Donat Bessenyei <be...@cloudera.com>.
Hi All,
Thank you for all the feedback and responses.
Regarding the open tickets, I had something similar to Mike's idea in
mind: we review the tickets and if there's nothing blocking a release,
we reschedule the unresolved ones for 1.8 or so.
I agree that we should have more frequent releases. Aiming for
something quarterly sounds like a good thing.
Thank you,
Donat
On Fri, Sep 30, 2016 at 8:01 PM, Saikat Kanjilal <sx...@hotmail.com> wrote:
> I'd be willing to help, I've been heads down on other stuff and have had to postpone the graph sink implementation (https://issues.apache.org/jira/browse/FLUME-2035) but am looking to resume work and targeting an initial implementation by mid November sometime. In the meantime let me know how I can get more deeply involved in the next release.
>
>
> Regards
>
>
> ________________________________
> From: Ralph Goers <ra...@dslextreme.com>
> Sent: Friday, September 30, 2016 10:15 AM
> To: dev@flume.apache.org
> Subject: Re: [DISCUSS] Flume 1.7 release plan
>
> FWIW, missing the train wouldn't be that big a deal if you knew the next release wouldn't be too far out. A release a quarter would be a nice target.
>
> Ralph
>
>> On Sep 30, 2016, at 8:36 AM, Mike Percy <mp...@apache.org> wrote:
>>
>> On Fri, Sep 30, 2016 at 2:13 PM, Denes Arvay <de...@cloudera.com> wrote:
>>
>>> What are your plans regarding to the mentioned 18 issues in patch available
>>> state? Should we decide on a one-by-one basis whether we'd like to include
>>> in the release or should we reschedule all of them to a next release?
>>>
>>
>> I'd personally recommend committing whatever is ready and reasonably
>> low-risk, and whatever doesn't make the deadline should "miss the train"
>> unless it's a particularly critical issue. This approach has worked well
>> for me in the past.
>>
>> Best,
>> Mike
>
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Saikat Kanjilal <sx...@hotmail.com>.
I'd be willing to help, I've been heads down on other stuff and have had to postpone the graph sink implementation (https://issues.apache.org/jira/browse/FLUME-2035) but am looking to resume work and targeting an initial implementation by mid November sometime. In the meantime let me know how I can get more deeply involved in the next release.
Regards
________________________________
From: Ralph Goers <ra...@dslextreme.com>
Sent: Friday, September 30, 2016 10:15 AM
To: dev@flume.apache.org
Subject: Re: [DISCUSS] Flume 1.7 release plan
FWIW, missing the train wouldn't be that big a deal if you knew the next release wouldn't be too far out. A release a quarter would be a nice target.
Ralph
> On Sep 30, 2016, at 8:36 AM, Mike Percy <mp...@apache.org> wrote:
>
> On Fri, Sep 30, 2016 at 2:13 PM, Denes Arvay <de...@cloudera.com> wrote:
>
>> What are your plans regarding to the mentioned 18 issues in patch available
>> state? Should we decide on a one-by-one basis whether we'd like to include
>> in the release or should we reschedule all of them to a next release?
>>
>
> I'd personally recommend committing whatever is ready and reasonably
> low-risk, and whatever doesn't make the deadline should "miss the train"
> unless it's a particularly critical issue. This approach has worked well
> for me in the past.
>
> Best,
> Mike
Re: [DISCUSS] Flume 1.7 release plan
Posted by Mike Percy <mp...@apache.org>.
On Fri, Sep 30, 2016 at 6:15 PM, Ralph Goers <ra...@dslextreme.com>
wrote:
> FWIW, missing the train wouldn’t be that big a deal if you knew the next
> release wouldn’t be too far out. A release a quarter would be a nice
> target.
>
+1, every 2-3 months would be ideal IMHO.
Mike
Re: [DISCUSS] Flume 1.7 release plan
Posted by Ralph Goers <ra...@dslextreme.com>.
FWIW, missing the train wouldn’t be that big a deal if you knew the next release wouldn’t be too far out. A release a quarter would be a nice target.
Ralph
> On Sep 30, 2016, at 8:36 AM, Mike Percy <mp...@apache.org> wrote:
>
> On Fri, Sep 30, 2016 at 2:13 PM, Denes Arvay <de...@cloudera.com> wrote:
>
>> What are your plans regarding to the mentioned 18 issues in patch available
>> state? Should we decide on a one-by-one basis whether we'd like to include
>> in the release or should we reschedule all of them to a next release?
>>
>
> I'd personally recommend committing whatever is ready and reasonably
> low-risk, and whatever doesn't make the deadline should "miss the train"
> unless it's a particularly critical issue. This approach has worked well
> for me in the past.
>
> Best,
> Mike
Re: [DISCUSS] Flume 1.7 release plan
Posted by Mike Percy <mp...@apache.org>.
On Fri, Sep 30, 2016 at 2:13 PM, Denes Arvay <de...@cloudera.com> wrote:
> What are your plans regarding to the mentioned 18 issues in patch available
> state? Should we decide on a one-by-one basis whether we'd like to include
> in the release or should we reschedule all of them to a next release?
>
I'd personally recommend committing whatever is ready and reasonably
low-risk, and whatever doesn't make the deadline should "miss the train"
unless it's a particularly critical issue. This approach has worked well
for me in the past.
Best,
Mike
Re: [DISCUSS] Flume 1.7 release plan
Posted by Attila Simon <sa...@cloudera.com>.
Hi Gents,
Cutting for a release is a great idea! I fully agree with Donat's and
Mike's comments.
Related to Denes's question: I'm in favour of the one-by-one decision and the
deadline idea for giving the still open tickets a chance to get resolved.
Also I'm here to help with review or patch or any other release related
tasks.
Cheers,
Attila
On Fri, Sep 30, 2016 at 3:13 PM, Denes Arvay <de...@cloudera.com> wrote:
> Hi Donat,
>
> Sounds like a great plan, I really like the idea, I'm ok with the release
> timeline and you being (co-)RM.
> What are your plans regarding to the mentioned 18 issues in patch available
> state? Should we decide on a one-by-one basis whether we'd like to include
> in the release or should we reschedule all of them to a next release?
> I see no blocker issues among them, on the other hand we might want to
> include some in the release.
> In this case we could set a deadline and the patches having +1/shipit by
> the deadline could be included in the release. I'd be happy to help with
> prioritization and review.
>
> What do you think?
>
> Regards,
> Denes
>
>
>
> On Fri, Sep 30, 2016 at 12:06 PM Mike Percy <mp...@apache.org> wrote:
>
> > Hi Donat,
> > Thanks for bringing this up again.
> >
> > +1 on doing a Flume 1.7.0 release right away. It's really long overdue
> and
> > I don't know of anything that should block the release; I think we met
> the
> > criteria for having enough improvements to do a release quite a while
> ago.
> >
> > +1 on you being RM or co-RM. I also don't mind helping with the
> logistics.
> >
> > Mike
> >
> >
> > On Fri, Sep 30, 2016 at 9:46 AM, Balazs Donat Bessenyei <
> > bessbd@cloudera.com
> > > wrote:
> >
> > > Hi All,
> > >
> > > We have almost 100 commits since 1.6.0, and a bunch of new features
> > > and improvements including a Taildir Source, many upgrades,
> > > performance increases, plus a lot of fixes and documentation
> > > additions.
> > >
> > > It seems to me that it's time to cut a 1.7 release soon. I would be
> > > happy to volunteer to RM or co-RM the release (possibly together with
> > > Lior Zeno who has previously volunteered for such).
> > >
> > > I know that we have already had a discussion about this. However, as
> > > progress seems to have slowed down recently, I suggest re-triaging the
> > > tickets to unblock the release and moving forward with the release
> > > process right away.
> > >
> > > Below is the list of tickets that have patches submitted and are
> > > scheduled for 1.7.0:
> > > https://issues.apache.org/jira/browse/FLUME-2998?jql=project
> > > %20%3D%20FLUME%20AND%20status%20%3D%20%22Patch%20Available%
> > >
> > 22%20AND%20resolution%20%3D%20Unresolved%20AND%
> 20fixVersion%20%3D%20v1.7.0
> > > (18 tickets)
> > >
> > > There are more tickets that have no patch submitted:
> > > https://issues.apache.org/jira/browse/FLUME-2998?jql=project
> > > %20%3D%20FLUME%20AND%20issuetype%20in%20standardIssueTypes()
> > > %20AND%20resolution%20%3D%20Unresolved%20AND%
> 20fixVersion%20%3D%20v1.7.0
> > > (30 tickets)
> > >
> > > I suggest tracking the release process using the JIRA previously filed
> > > by Lior at https://issues.apache.org/jira/browse/FLUME-2924
> > >
> > > If this all sounds OK, I'd like to suggest targeting the week of
> > > October 10 for a first RC. (Also, anything that is non-trivial should
> > > get in by October 7. Any feature or big change that is not committed
> > > by then would be scheduled for the next release.)
> > >
> > > That should leave enough time for people to get moving on patches and
> > > reviews for their documentation improvements, critical bug fixes, and
> > > low-risk enhancements, etc.
> > >
> > > Also, I would like to propose October 7 (one week from today) for the
> > > branch date.
> > >
> > > Please let me know your thoughts.
> > >
> > >
> > > Best Regards,
> > >
> > > Donat
> > >
> >
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Denes Arvay <de...@cloudera.com>.
Hi Donat,
Sounds like a great plan, I really like the idea, I'm ok with the release
timeline and you being (co-)RM.
What are your plans regarding to the mentioned 18 issues in patch available
state? Should we decide on a one-by-one basis whether we'd like to include
in the release or should we reschedule all of them to a next release?
I see no blocker issues among them, on the other hand we might want to
include some in the release.
In this case we could set a deadline and the patches having +1/shipit by
the deadline could be included in the release. I'd be happy to help with
prioritization and review.
What do you think?
Regards,
Denes
On Fri, Sep 30, 2016 at 12:06 PM Mike Percy <mp...@apache.org> wrote:
> Hi Donat,
> Thanks for bringing this up again.
>
> +1 on doing a Flume 1.7.0 release right away. It's really long overdue and
> I don't know of anything that should block the release; I think we met the
> criteria for having enough improvements to do a release quite a while ago.
>
> +1 on you being RM or co-RM. I also don't mind helping with the logistics.
>
> Mike
>
>
> On Fri, Sep 30, 2016 at 9:46 AM, Balazs Donat Bessenyei <
> bessbd@cloudera.com
> > wrote:
>
> > Hi All,
> >
> > We have almost 100 commits since 1.6.0, and a bunch of new features
> > and improvements including a Taildir Source, many upgrades,
> > performance increases, plus a lot of fixes and documentation
> > additions.
> >
> > It seems to me that it's time to cut a 1.7 release soon. I would be
> > happy to volunteer to RM or co-RM the release (possibly together with
> > Lior Zeno who has previously volunteered for such).
> >
> > I know that we have already had a discussion about this. However, as
> > progress seems to have slowed down recently, I suggest re-triaging the
> > tickets to unblock the release and moving forward with the release
> > process right away.
> >
> > Below is the list of tickets that have patches submitted and are
> > scheduled for 1.7.0:
> > https://issues.apache.org/jira/browse/FLUME-2998?jql=project
> > %20%3D%20FLUME%20AND%20status%20%3D%20%22Patch%20Available%
> >
> 22%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.7.0
> > (18 tickets)
> >
> > There are more tickets that have no patch submitted:
> > https://issues.apache.org/jira/browse/FLUME-2998?jql=project
> > %20%3D%20FLUME%20AND%20issuetype%20in%20standardIssueTypes()
> > %20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.7.0
> > (30 tickets)
> >
> > I suggest tracking the release process using the JIRA previously filed
> > by Lior at https://issues.apache.org/jira/browse/FLUME-2924
> >
> > If this all sounds OK, I'd like to suggest targeting the week of
> > October 10 for a first RC. (Also, anything that is non-trivial should
> > get in by October 7. Any feature or big change that is not committed
> > by then would be scheduled for the next release.)
> >
> > That should leave enough time for people to get moving on patches and
> > reviews for their documentation improvements, critical bug fixes, and
> > low-risk enhancements, etc.
> >
> > Also, I would like to propose October 7 (one week from today) for the
> > branch date.
> >
> > Please let me know your thoughts.
> >
> >
> > Best Regards,
> >
> > Donat
> >
>
Re: [DISCUSS] Flume 1.7 release plan
Posted by Mike Percy <mp...@apache.org>.
Hi Donat,
Thanks for bringing this up again.
+1 on doing a Flume 1.7.0 release right away. It's really long overdue and
I don't know of anything that should block the release; I think we met the
criteria for having enough improvements to do a release quite a while ago.
+1 on you being RM or co-RM. I also don't mind helping with the logistics.
Mike
On Fri, Sep 30, 2016 at 9:46 AM, Balazs Donat Bessenyei <bessbd@cloudera.com
> wrote:
> Hi All,
>
> We have almost 100 commits since 1.6.0, and a bunch of new features
> and improvements including a Taildir Source, many upgrades,
> performance increases, plus a lot of fixes and documentation
> additions.
>
> It seems to me that it's time to cut a 1.7 release soon. I would be
> happy to volunteer to RM or co-RM the release (possibly together with
> Lior Zeno who has previously volunteered for such).
>
> I know that we have already had a discussion about this. However, as
> progress seems to have slowed down recently, I suggest re-triaging the
> tickets to unblock the release and moving forward with the release
> process right away.
>
> Below is the list of tickets that have patches submitted and are
> scheduled for 1.7.0:
> https://issues.apache.org/jira/browse/FLUME-2998?jql=project
> %20%3D%20FLUME%20AND%20status%20%3D%20%22Patch%20Available%
> 22%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.7.0
> (18 tickets)
>
> There are more tickets that have no patch submitted:
> https://issues.apache.org/jira/browse/FLUME-2998?jql=project
> %20%3D%20FLUME%20AND%20issuetype%20in%20standardIssueTypes()
> %20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.7.0
> (30 tickets)
>
> I suggest tracking the release process using the JIRA previously filed
> by Lior at https://issues.apache.org/jira/browse/FLUME-2924
>
> If this all sounds OK, I'd like to suggest targeting the week of
> October 10 for a first RC. (Also, anything that is non-trivial should
> get in by October 7. Any feature or big change that is not committed
> by then would be scheduled for the next release.)
>
> That should leave enough time for people to get moving on patches and
> reviews for their documentation improvements, critical bug fixes, and
> low-risk enhancements, etc.
>
> Also, I would like to propose October 7 (one week from today) for the
> branch date.
>
> Please let me know your thoughts.
>
>
> Best Regards,
>
> Donat
>