You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Mike Percy <mp...@apache.org> on 2013/06/12 02:33:31 UTC

Flume 1.4 scope

Hi everyone,
I'd like to cut an RC and start a Flume 1.4 vote on June 20th (9 days from
now).

These are the currently resolved issues in Flume 1.4:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20Status%20%3D%20Resolved%20ORDER%20BY%20created%20ASC

These are the current JIRAs marked Patch Available with a fixVersion of
v1.4.0, plus anything marked as a Bug Blocker against v1.4.0:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20((Status%20%3D%20%22Patch%20Available%22)%20OR%20(Resolution%20%3D%20Unresolved%20and%20Type%20%3D%20Bug%20AND%20Priority%20%3D%20Blocker))%20ORDER%20BY%20priority%20DESC%2C%20created%20ASC

If you would like a JIRA to be considered for inclusion into Flume 1.4,
please mark it as fixVersion = v1.4.0 and mark it as Patch Available, or
set it to Type = Bug and Priority = Blocker if you really think it is a
critical bug that we cannot release without fixing.

Let's crunch through these patches and come up with an RC next week.

Thanks!
Mike

Re: Flume 1.4 scope

Posted by Mike Percy <mp...@apache.org>.
Here is the latest list of open JIRAs that have a chance of making it into
v1.4.0:

FLUME-2037 testDataFilesRequiredByBackupNotDeleted is flakey
FLUME-1947 ExecSource should optionally block if the channel is full.
FLUME-2076 JMX metrics support for HTTP Source
FLUME-2005 Minor improvements to Flume assembly config
FLUME-1874 Ship with log4j.properties file that has a reliable time based
rolling policy
FLUME-1285 FileChannel has a dependency on Hadoop IO classes
FLUME-2094 Remove the deprecated - Recoverable Memory Channel
FLUME-2089 ElasticSearchSink raises YAMLException when event body has
unexpected encoding.
FLUME-1938 Flume UDP Source for Windows Events being trimmed at \n
characters by SyslogUtils.extractEvent() function

I will triage / review / commit these as time permits. If any other
committers can pitch in with triage / review I would appreciate it. Please
holler if you have any concerns about known issues or anything else.

Here is the link to the JIRA query: http://s.apache.org/Olm

Thanks,
Mike




On Fri, Jun 21, 2013 at 1:27 AM, Mike Percy <mp...@apache.org> wrote:

> A couple things came up on my side, let's get in the last commits soon and
> do the RC in the next 1-2 days.
>
> Thanks,
> Mike
>
>
> On Jun 13, 2013, at 11:49 AM, Mike Percy <mp...@apache.org> wrote:
>
> Hi Roshan, sure, I'll commit it.
>
> Thanks!
> Mike
>
>
>
> On Thu, Jun 13, 2013 at 11:13 AM, Roshan Naik <ro...@hortonworks.com>wrote:
>
>> FYI... i am thinking of adding a blocker jira for removal of the
>> deprecated
>>   'Recoverable Memory Channel'.
>>
>>
>> On Tue, Jun 11, 2013 at 5:33 PM, Mike Percy <mp...@apache.org> wrote:
>>
>> > Hi everyone,
>> > I'd like to cut an RC and start a Flume 1.4 vote on June 20th (9 days
>> from
>> > now).
>> >
>> > These are the currently resolved issues in Flume 1.4:
>> >
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20Status%20%3D%20Resolved%20ORDER%20BY%20created%20ASC
>> >
>> > These are the current JIRAs marked Patch Available with a fixVersion of
>> > v1.4.0, plus anything marked as a Bug Blocker against v1.4.0:
>> >
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20((Status%20%3D%20%22Patch%20Available%22)%20OR%20(Resolution%20%3D%20Unresolved%20and%20Type%20%3D%20Bug%20AND%20Priority%20%3D%20Blocker))%20ORDER%20BY%20priority%20DESC%2C%20created%20ASC
>> >
>> > If you would like a JIRA to be considered for inclusion into Flume 1.4,
>> > please mark it as fixVersion = v1.4.0 and mark it as Patch Available, or
>> > set it to Type = Bug and Priority = Blocker if you really think it is a
>> > critical bug that we cannot release without fixing.
>> >
>> > Let's crunch through these patches and come up with an RC next week.
>> >
>> > Thanks!
>> > Mike
>> >
>>
>
>

Re: Flume 1.4 scope

Posted by Mike Percy <mp...@apache.org>.
A couple things came up on my side, let's get in the last commits soon and do the RC in the next 1-2 days.

Thanks,
Mike


On Jun 13, 2013, at 11:49 AM, Mike Percy <mp...@apache.org> wrote:

> Hi Roshan, sure, I'll commit it.
> 
> Thanks!
> Mike
> 
> 
> 
> On Thu, Jun 13, 2013 at 11:13 AM, Roshan Naik <ro...@hortonworks.com> wrote:
>> FYI... i am thinking of adding a blocker jira for removal of the deprecated
>>   'Recoverable Memory Channel'.
>> 
>> 
>> On Tue, Jun 11, 2013 at 5:33 PM, Mike Percy <mp...@apache.org> wrote:
>> 
>> > Hi everyone,
>> > I'd like to cut an RC and start a Flume 1.4 vote on June 20th (9 days from
>> > now).
>> >
>> > These are the currently resolved issues in Flume 1.4:
>> >
>> >
>> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20Status%20%3D%20Resolved%20ORDER%20BY%20created%20ASC
>> >
>> > These are the current JIRAs marked Patch Available with a fixVersion of
>> > v1.4.0, plus anything marked as a Bug Blocker against v1.4.0:
>> >
>> >
>> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20((Status%20%3D%20%22Patch%20Available%22)%20OR%20(Resolution%20%3D%20Unresolved%20and%20Type%20%3D%20Bug%20AND%20Priority%20%3D%20Blocker))%20ORDER%20BY%20priority%20DESC%2C%20created%20ASC
>> >
>> > If you would like a JIRA to be considered for inclusion into Flume 1.4,
>> > please mark it as fixVersion = v1.4.0 and mark it as Patch Available, or
>> > set it to Type = Bug and Priority = Blocker if you really think it is a
>> > critical bug that we cannot release without fixing.
>> >
>> > Let's crunch through these patches and come up with an RC next week.
>> >
>> > Thanks!
>> > Mike
>> >
>

Re: Flume 1.4 scope

Posted by Mike Percy <mp...@apache.org>.
Hi Roshan, sure, I'll commit it.

Thanks!
Mike



On Thu, Jun 13, 2013 at 11:13 AM, Roshan Naik <ro...@hortonworks.com>wrote:

> FYI... i am thinking of adding a blocker jira for removal of the deprecated
>   'Recoverable Memory Channel'.
>
>
> On Tue, Jun 11, 2013 at 5:33 PM, Mike Percy <mp...@apache.org> wrote:
>
> > Hi everyone,
> > I'd like to cut an RC and start a Flume 1.4 vote on June 20th (9 days
> from
> > now).
> >
> > These are the currently resolved issues in Flume 1.4:
> >
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20Status%20%3D%20Resolved%20ORDER%20BY%20created%20ASC
> >
> > These are the current JIRAs marked Patch Available with a fixVersion of
> > v1.4.0, plus anything marked as a Bug Blocker against v1.4.0:
> >
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20((Status%20%3D%20%22Patch%20Available%22)%20OR%20(Resolution%20%3D%20Unresolved%20and%20Type%20%3D%20Bug%20AND%20Priority%20%3D%20Blocker))%20ORDER%20BY%20priority%20DESC%2C%20created%20ASC
> >
> > If you would like a JIRA to be considered for inclusion into Flume 1.4,
> > please mark it as fixVersion = v1.4.0 and mark it as Patch Available, or
> > set it to Type = Bug and Priority = Blocker if you really think it is a
> > critical bug that we cannot release without fixing.
> >
> > Let's crunch through these patches and come up with an RC next week.
> >
> > Thanks!
> > Mike
> >
>

Re: Flume 1.4 scope

Posted by Roshan Naik <ro...@hortonworks.com>.
FYI... i am thinking of adding a blocker jira for removal of the deprecated
  'Recoverable Memory Channel'.


On Tue, Jun 11, 2013 at 5:33 PM, Mike Percy <mp...@apache.org> wrote:

> Hi everyone,
> I'd like to cut an RC and start a Flume 1.4 vote on June 20th (9 days from
> now).
>
> These are the currently resolved issues in Flume 1.4:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20Status%20%3D%20Resolved%20ORDER%20BY%20created%20ASC
>
> These are the current JIRAs marked Patch Available with a fixVersion of
> v1.4.0, plus anything marked as a Bug Blocker against v1.4.0:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20((Status%20%3D%20%22Patch%20Available%22)%20OR%20(Resolution%20%3D%20Unresolved%20and%20Type%20%3D%20Bug%20AND%20Priority%20%3D%20Blocker))%20ORDER%20BY%20priority%20DESC%2C%20created%20ASC
>
> If you would like a JIRA to be considered for inclusion into Flume 1.4,
> please mark it as fixVersion = v1.4.0 and mark it as Patch Available, or
> set it to Type = Bug and Priority = Blocker if you really think it is a
> critical bug that we cannot release without fixing.
>
> Let's crunch through these patches and come up with an RC next week.
>
> Thanks!
> Mike
>