This is the second release for Apache Flume as a top-level project,
version 1.3.0. We are voting on release candidate rc0.

*** Please cast your vote within the next 72 hours ***

The list of fixed issues:
https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=8b748e3851f9378bc319af0c8b08c9ff0a044c1b

The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
for the source and binary artifacts can be found at:
http://people.apache.org/~brock/flume-1.3.0-rc0/

The tag to be voted on:
https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8b748e3851f9378bc319af0c8b08c9ff0a044c1b

The KEYS file can be found here:
https://dist.apache.org/repos/dist/release/flume/KEYS

and here is my vote

+1 release rc0 as flume-1.3.0

On Sun, Nov 11, 2012 at 6:27 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc0.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc0/
>
> The tag to be voted on:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>
> The KEYS file can be found here:
> https://dist.apache.org/repos/dist/release/flume/KEYS

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Here my vote:

+1 rc0

- ALex

On Nov 12, 2012, at 1:28 AM, Brock Noland <[EMAIL PROTECTED]> wrote:

> and here is my vote
>
> +1 release rc0 as flume-1.3.0
>
> On Sun, Nov 11, 2012 at 6:27 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>> This is the second release for Apache Flume as a top-level project,
>> version 1.3.0. We are voting on release candidate rc0.
>>
>> *** Please cast your vote within the next 72 hours ***
>>
>> The list of fixed issues:
>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>>
>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> for the source and binary artifacts can be found at:
>> http://people.apache.org/~brock/flume-1.3.0-rc0/
>>
>> The tag to be voted on:
>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>>
>> The KEYS file can be found here:
>> https://dist.apache.org/repos/dist/release/flume/KEYS
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

-1 (please see my notes below for show stopper).

Hi Brock,
thank you very much for your great work on this release candidate. I'm sorry for my -1, however I've noticed licensing issues that I believe needs to be resolved first.

Show stoppers:
* LICENSE file in binary artifact seems to be missing license notes for following third party jars: gson-2.2.2.jar, protobuf-java-2.4.1.jar, mina-core-2.0.4.jar

Notes:
* Both artifacts seems to have directory apache-flume-1.3.0. It would be nice if artifact apache-flume-1.3.0.tar.gz would have directory apache-flume-1.3.0 (e.g. current state) and apache-flume-1.3.0-bin.tar.gz would have directory apache-flume-1.3.0-bin. It's very nice practise to distribute tarballs that have directory with exactly the same name as the tarball itself minus suffix. I know that flume 1.2.0 was released with this already, so this is merely a suggestion :-)
* It seems that we're still depending on "export MAVEN_OPTS="-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m"". It would be nice do document it somewhere, but again, no difference from flume 1.2.0, so just a suggestion.

Validations:
* Verified checksums
* Tests seems to be passing

Jarcec

On Sun, Nov 11, 2012 at 06:27:49PM -0600, Brock Noland wrote:
> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc0.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc0/
>
> The tag to be voted on:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>
> The KEYS file can be found here:
> https://dist.apache.org/repos/dist/release/flume/KEYS

Hi,

OK, sounds good. I will resolve those today and send out another RC.

On Mon, Nov 12, 2012 at 10:18 AM, Jarek Jarcec Cecho <[EMAIL PROTECTED]> wrote:
> -1 (please see my notes below for show stopper).
>
> Hi Brock,
> thank you very much for your great work on this release candidate. I'm sorry for my -1, however I've noticed licensing issues that I believe needs to be resolved first.
>
> Show stoppers:
> * LICENSE file in binary artifact seems to be missing license notes for following third party jars: gson-2.2.2.jar, protobuf-java-2.4.1.jar, mina-core-2.0.4.jar
>
> Notes:
> * Both artifacts seems to have directory apache-flume-1.3.0. It would be nice if artifact apache-flume-1.3.0.tar.gz would have directory apache-flume-1.3.0 (e.g. current state) and apache-flume-1.3.0-bin.tar.gz would have directory apache-flume-1.3.0-bin. It's very nice practise to distribute tarballs that have directory with exactly the same name as the tarball itself minus suffix. I know that flume 1.2.0 was released with this already, so this is merely a suggestion :-)
> * It seems that we're still depending on "export MAVEN_OPTS="-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m"". It would be nice do document it somewhere, but again, no difference from flume 1.2.0, so just a suggestion.
>
> Validations:
> * Verified checksums
> * Tests seems to be passing
>
> Jarcec
>
> On Sun, Nov 11, 2012 at 06:27:49PM -0600, Brock Noland wrote:
>> This is the second release for Apache Flume as a top-level project,
>> version 1.3.0. We are voting on release candidate rc0.
>>
>> *** Please cast your vote within the next 72 hours ***
>>
>> The list of fixed issues:
>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>>
>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> for the source and binary artifacts can be found at:
>> http://people.apache.org/~brock/flume-1.3.0-rc0/
>>
>> The tag to be voted on:
>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8b748e3851f9378bc319af0c8b08c9ff0a044c1b
>>
>> The KEYS file can be found here:
>> https://dist.apache.org/repos/dist/release/flume/KEYS

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

This is the second release for Apache Flume as a top-level project,
version 1.3.0. We are voting on release candidate rc1.

*** Please cast your vote within the next 72 hours ***

The list of fixed issues:
https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=9636067d4e1241032749c0d2fdf8b61d3237b1ca

The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
for the source and binary artifacts can be found at:
http://people.apache.org/~brock/flume-1.3.0-rc1/

The tag to be voted on:
https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=9636067d4e1241032749c0d2fdf8b61d3237b1ca

The KEYS file can be found here:
https://dist.apache.org/repos/dist/release/flume/KEYS

+1 verified hashs, sigs, tarball directory structure and a sanity test passes

On Mon, Nov 12, 2012 at 12:57 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc1.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=9636067d4e1241032749c0d2fdf8b61d3237b1ca
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc1/
>
> The tag to be voted on:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=9636067d4e1241032749c0d2fdf8b61d3237b1ca
>
> The KEYS file can be found here:
> https://dist.apache.org/repos/dist/release/flume/KEYS

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

-1  (non binding)

I see the following Integration tests .. sepcifically (TestFileChannel,
TestRpcClient, TestRpcClientCommunicationFailure )

The nature of the error is the same...

 <testcase time="0.095"
classname="org.apache.flume.test.agent.TestFileChannel" name="testInOut">
    <error message="Failed to locate tar-ball distribution. Please specify
explicitly via system property: flume.dist.tarball"
type="java.lang.Exception">java.lang.Exception: Failed to locate tar-ball
distribution. Please specify explicitly via system property:
flume.dist.tarball
        at
org.apache.flume.test.util.StagedInstall.<init>(StagedInstall.java:207)
        at
org.apache.flume.test.util.StagedInstall.getInstance(StagedInstall.java:75)

Build Steps:...

- mvn package -DskipTests
- mvn test

I got the same erors with ... mvn clean install.

See attachment for more details on the error. fyi.. I am building on a
macbook pro.
-roshan

Hi,

Hmm, my test alias adds that property. Looks like StagedInstall does
hard code the -dist name,

                && name.endsWith("-dist.tar.gz")) {

Brock

On Mon, Nov 12, 2012 at 6:33 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
> -1  (non binding)
>
> I see the following Integration tests .. sepcifically (TestFileChannel,
> TestRpcClient, TestRpcClientCommunicationFailure )
>
> The nature of the error is the same...
>
>  <testcase time="0.095"
> classname="org.apache.flume.test.agent.TestFileChannel" name="testInOut">
>     <error message="Failed to locate tar-ball distribution. Please specify
> explicitly via system property: flume.dist.tarball"
> type="java.lang.Exception">java.lang.Exception: Failed to locate tar-ball
> distribution. Please specify explicitly via system property:
> flume.dist.tarball
>         at
> org.apache.flume.test.util.StagedInstall.<init>(StagedInstall.java:207)
>         at
> org.apache.flume.test.util.StagedInstall.getInstance(StagedInstall.java:75)
>
> Build Steps:...
>
> - mvn package -DskipTests
> - mvn test
>
> I got the same erors with ... mvn clean install.
>
> See attachment for more details on the error. fyi.. I am building on a
> macbook pro.
> -roshan

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

https://issues.apache.org/jira/browse/FLUME-1701

On Mon, Nov 12, 2012 at 6:38 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Hmm, my test alias adds that property. Looks like StagedInstall does
> hard code the -dist name,
>
>                 && name.endsWith("-dist.tar.gz")) {
>
> Brock
>
> On Mon, Nov 12, 2012 at 6:33 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
>> -1  (non binding)
>>
>> I see the following Integration tests .. sepcifically (TestFileChannel,
>> TestRpcClient, TestRpcClientCommunicationFailure )
>>
>> The nature of the error is the same...
>>
>>  <testcase time="0.095"
>> classname="org.apache.flume.test.agent.TestFileChannel" name="testInOut">
>>     <error message="Failed to locate tar-ball distribution. Please specify
>> explicitly via system property: flume.dist.tarball"
>> type="java.lang.Exception">java.lang.Exception: Failed to locate tar-ball
>> distribution. Please specify explicitly via system property:
>> flume.dist.tarball
>>         at
>> org.apache.flume.test.util.StagedInstall.<init>(StagedInstall.java:207)
>>         at
>> org.apache.flume.test.util.StagedInstall.getInstance(StagedInstall.java:75)
>>
>> Build Steps:...
>>
>> - mvn package -DskipTests
>> - mvn test
>>
>> I got the same erors with ... mvn clean install.
>>
>> See attachment for more details on the error. fyi.. I am building on a
>> macbook pro.
>> -roshan
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Looks like the Jenkins build also failed the unit tests because of this.  

Hari

--
Hari Shreedharan
On Monday, November 12, 2012 at 4:40 PM, Brock Noland wrote:

> https://issues.apache.org/jira/browse/FLUME-1701
>
> On Mon, Nov 12, 2012 at 6:38 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > Hi,
> >
> > Hmm, my test alias adds that property. Looks like StagedInstall does
> > hard code the -dist name,
> >
> > && name.endsWith("-dist.tar.gz")) {
> >
> > Brock
> >
> > On Mon, Nov 12, 2012 at 6:33 PM, Roshan Naik <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > -1 (non binding)
> > >
> > > I see the following Integration tests .. sepcifically (TestFileChannel,
> > > TestRpcClient, TestRpcClientCommunicationFailure )
> > >
> > > The nature of the error is the same...
> > >
> > > <testcase time="0.095"
> > > classname="org.apache.flume.test.agent.TestFileChannel" name="testInOut">
> > > <error message="Failed to locate tar-ball distribution. Please specify
> > > explicitly via system property: flume.dist.tarball"
> > > type="java.lang.Exception">java.lang.Exception: Failed to locate tar-ball
> > > distribution. Please specify explicitly via system property:
> > > flume.dist.tarball
> > > at
> > > org.apache.flume.test.util.StagedInstall.<init>(StagedInstall.java:207)
> > > at
> > > org.apache.flume.test.util.StagedInstall.getInstance(StagedInstall.java:75)
> > >
> > > Build Steps:...
> > >
> > > - mvn package -DskipTests
> > > - mvn test
> > >
> > > I got the same erors with ... mvn clean install.
> > >
> > > See attachment for more details on the error. fyi.. I am building on a
> > > macbook pro.
> > > -roshan
> > >
> >
> >
> >
> >
> > --
> > Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
> >
>
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>
>

Yeah my environment didn't hit this issue... I'll fix it and re-spin
this morning.

On Tue, Nov 13, 2012 at 12:57 AM, Hari Shreedharan
<[EMAIL PROTECTED]> wrote:
> Looks like the Jenkins build also failed the unit tests because of this.
>
> Hari
>
> --
> Hari Shreedharan
>
>
> On Monday, November 12, 2012 at 4:40 PM, Brock Noland wrote:
>
>> https://issues.apache.org/jira/browse/FLUME-1701
>>
>> On Mon, Nov 12, 2012 at 6:38 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>> > Hi,
>> >
>> > Hmm, my test alias adds that property. Looks like StagedInstall does
>> > hard code the -dist name,
>> >
>> > && name.endsWith("-dist.tar.gz")) {
>> >
>> > Brock
>> >
>> > On Mon, Nov 12, 2012 at 6:33 PM, Roshan Naik <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>> > > -1 (non binding)
>> > >
>> > > I see the following Integration tests .. sepcifically (TestFileChannel,
>> > > TestRpcClient, TestRpcClientCommunicationFailure )
>> > >
>> > > The nature of the error is the same...
>> > >
>> > > <testcase time="0.095"
>> > > classname="org.apache.flume.test.agent.TestFileChannel" name="testInOut">
>> > > <error message="Failed to locate tar-ball distribution. Please specify
>> > > explicitly via system property: flume.dist.tarball"
>> > > type="java.lang.Exception">java.lang.Exception: Failed to locate tar-ball
>> > > distribution. Please specify explicitly via system property:
>> > > flume.dist.tarball
>> > > at
>> > > org.apache.flume.test.util.StagedInstall.<init>(StagedInstall.java:207)
>> > > at
>> > > org.apache.flume.test.util.StagedInstall.getInstance(StagedInstall.java:75)
>> > >
>> > > Build Steps:...
>> > >
>> > > - mvn package -DskipTests
>> > > - mvn test
>> > >
>> > > I got the same erors with ... mvn clean install.
>> > >
>> > > See attachment for more details on the error. fyi.. I am building on a
>> > > macbook pro.
>> > > -roshan
>> > >
>> >
>> >
>> >
>> >
>> > --
>> > Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>> >
>>
>>
>>
>>
>> --
>> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>>
>>
>
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

This is the second release for Apache Flume as a top-level project,
version 1.3.0. We are voting on release candidate rc2.

*** Please cast your vote within the next 72 hours ***

The list of fixed issues:
http://s.apache.org/A9x

The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
for the source and binary artifacts can be found at:
http://people.apache.org/~brock/flume-1.3.0-rc2/

The tag to be voted on:
http://s.apache.org/aVa

The KEYS file can be found here:
https://dist.apache.org/repos/dist/release/flume/KEYS

+1 verified hashes, sigs, and performed single node sanity test

On Tue, Nov 13, 2012 at 10:39 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc2.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/A9x
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc2/
>
> The tag to be voted on:
> http://s.apache.org/aVa
>
> The KEYS file can be found here:
> https://dist.apache.org/repos/dist/release/flume/KEYS

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Looks good. Verified build and tests.
+1  (non binding)
-roshan
On Tue, Nov 13, 2012 at 8:41 AM, Brock Noland <[EMAIL PROTECTED]> wrote:

> +1 verified hashes, sigs, and performed single node sanity test
>
> On Tue, Nov 13, 2012 at 10:39 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
> > This is the second release for Apache Flume as a top-level project,
> > version 1.3.0. We are voting on release candidate rc2.
> >
> > *** Please cast your vote within the next 72 hours ***
> >
> > The list of fixed issues:
> > http://s.apache.org/A9x
> >
> > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > for the source and binary artifacts can be found at:
> > http://people.apache.org/~brock/flume-1.3.0-rc2/
> >
> > The tag to be voted on:
> > http://s.apache.org/aVa
> >
> > The KEYS file can be found here:
> > https://dist.apache.org/repos/dist/release/flume/KEYS
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce -
> http://incubator.apache.org/mrunit/
>

How can I verify the Maven artifacts?  It really is a problem to deploy them after the vote since the can't be verified.

What web site updates will be made?  How can we verify those?

Ralph

On Nov 13, 2012, at 8:39 AM, Brock Noland wrote:

> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc2.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/A9x
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc2/
>
> The tag to be voted on:
> http://s.apache.org/aVa
>
> The KEYS file can be found here:
> https://dist.apache.org/repos/dist/release/flume/KEYS

Blocker came up on the user list

https://issues.apache.org/jira/browse/FLUME-1705

Brock

On Tue, Nov 13, 2012 at 2:59 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
> Looks good. Verified build and tests.
> +1  (non binding)
> -roshan
>
>
> On Tue, Nov 13, 2012 at 8:41 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>
>> +1 verified hashes, sigs, and performed single node sanity test
>>
>> On Tue, Nov 13, 2012 at 10:39 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>> > This is the second release for Apache Flume as a top-level project,
>> > version 1.3.0. We are voting on release candidate rc2.
>> >
>> > *** Please cast your vote within the next 72 hours ***
>> >
>> > The list of fixed issues:
>> > http://s.apache.org/A9x
>> >
>> > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> > for the source and binary artifacts can be found at:
>> > http://people.apache.org/~brock/flume-1.3.0-rc2/
>> >
>> > The tag to be voted on:
>> > http://s.apache.org/aVa
>> >
>> > The KEYS file can be found here:
>> > https://dist.apache.org/repos/dist/release/flume/KEYS
>>
>>
>>
>> --
>> Apache MRUnit - Unit testing MapReduce -
>> http://incubator.apache.org/mrunit/
>>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Hi,

I actually thought the maven item as odd as well. MRUnit deploys to
the staging repository (See "Deploy to Nexus Staging Repository"
http://mrunit.apache.org/pmc/how_to_release.html).

The documentation will be updated, I believe these can verified
locally by using mvn site. Actually I have just looked at version I
generated earlier today and there are some updates needed.

Brock

On Tue, Nov 13, 2012 at 3:29 PM, Ralph Goers <[EMAIL PROTECTED]> wrote:
> How can I verify the Maven artifacts?  It really is a problem to deploy them after the vote since the can't be verified.
>
> What web site updates will be made?  How can we verify those?
>
> Ralph
>
> On Nov 13, 2012, at 8:39 AM, Brock Noland wrote:
>
>> This is the second release for Apache Flume as a top-level project,
>> version 1.3.0. We are voting on release candidate rc2.
>>
>> *** Please cast your vote within the next 72 hours ***
>>
>> The list of fixed issues:
>> http://s.apache.org/A9x
>>
>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> for the source and binary artifacts can be found at:
>> http://people.apache.org/~brock/flume-1.3.0-rc2/
>>
>> The tag to be voted on:
>> http://s.apache.org/aVa
>>
>> The KEYS file can be found here:
>> https://dist.apache.org/repos/dist/release/flume/KEYS
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Yeah, in
https://cwiki.apache.org/confluence/display/FLUME/How+to+Release#HowtoRelease-DeployMavenartifactsthere
is a section saying to do this at release time but you should
probably do it at RC vote time. Just push it to the staging repo, not the
release repo before the vote. It's a binary artifact, so technically we
aren't voting on it, but I agree with you guys that it's good practice to
do it early. Probably the wiki should be updated to make this process
explicit.

Regards,
Mike

On Tue, Nov 13, 2012 at 2:16 PM, Brock Noland <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I actually thought the maven item as odd as well. MRUnit deploys to
> the staging repository (See "Deploy to Nexus Staging Repository"
> http://mrunit.apache.org/pmc/how_to_release.html).
>
> The documentation will be updated, I believe these can verified
> locally by using mvn site. Actually I have just looked at version I
> generated earlier today and there are some updates needed.
>
> Brock
>
> On Tue, Nov 13, 2012 at 3:29 PM, Ralph Goers <[EMAIL PROTECTED]>
> wrote:
> > How can I verify the Maven artifacts?  It really is a problem to deploy
> them after the vote since the can't be verified.
> >
> > What web site updates will be made?  How can we verify those?
> >
> > Ralph
> >
> > On Nov 13, 2012, at 8:39 AM, Brock Noland wrote:
> >
> >> This is the second release for Apache Flume as a top-level project,
> >> version 1.3.0. We are voting on release candidate rc2.
> >>
> >> *** Please cast your vote within the next 72 hours ***
> >>
> >> The list of fixed issues:
> >> http://s.apache.org/A9x
> >>
> >> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> >> for the source and binary artifacts can be found at:
> >> http://people.apache.org/~brock/flume-1.3.0-rc2/
> >>
> >> The tag to be voted on:
> >> http://s.apache.org/aVa
> >>
> >> The KEYS file can be found here:
> >> https://dist.apache.org/repos/dist/release/flume/KEYS
> >
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce -
> http://incubator.apache.org/mrunit/
>

Patch attached. For this one -1 from me.

Thanks,
 Alex

On Nov 13, 2012, at 11:13 PM, Brock Noland <[EMAIL PROTECTED]> wrote:

> Blocker came up on the user list
>
> https://issues.apache.org/jira/browse/FLUME-1705
>
> Brock
>
> On Tue, Nov 13, 2012 at 2:59 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
>> Looks good. Verified build and tests.
>> +1  (non binding)
>> -roshan
>>
>>
>> On Tue, Nov 13, 2012 at 8:41 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>
>>> +1 verified hashes, sigs, and performed single node sanity test
>>>
>>> On Tue, Nov 13, 2012 at 10:39 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>>> This is the second release for Apache Flume as a top-level project,
>>>> version 1.3.0. We are voting on release candidate rc2.
>>>>
>>>> *** Please cast your vote within the next 72 hours ***
>>>>
>>>> The list of fixed issues:
>>>> http://s.apache.org/A9x
>>>>
>>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>>> for the source and binary artifacts can be found at:
>>>> http://people.apache.org/~brock/flume-1.3.0-rc2/
>>>>
>>>> The tag to be voted on:
>>>> http://s.apache.org/aVa
>>>>
>>>> The KEYS file can be found here:
>>>> https://dist.apache.org/repos/dist/release/flume/KEYS
>>>
>>>
>>>
>>> --
>>> Apache MRUnit - Unit testing MapReduce -
>>> http://incubator.apache.org/mrunit/
>>>
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

FLUME-1705 is committed (Commit: 491157104cda0e3fbd3dece2c6f3baf5e72308f5)

+1 from me for 1.3.0- RC2

Thanks,
 Alex

On Nov 14, 2012, at 8:17 AM, Alexander Alten-Lorenz <[EMAIL PROTECTED]> wrote:

> Patch attached. For this one -1 from me.
>
> Thanks,
> Alex
>
> On Nov 13, 2012, at 11:13 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>
>> Blocker came up on the user list
>>
>> https://issues.apache.org/jira/browse/FLUME-1705
>>
>> Brock
>>
>> On Tue, Nov 13, 2012 at 2:59 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
>>> Looks good. Verified build and tests.
>>> +1  (non binding)
>>> -roshan
>>>
>>>
>>> On Tue, Nov 13, 2012 at 8:41 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>>
>>>> +1 verified hashes, sigs, and performed single node sanity test
>>>>
>>>> On Tue, Nov 13, 2012 at 10:39 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>>>> This is the second release for Apache Flume as a top-level project,
>>>>> version 1.3.0. We are voting on release candidate rc2.
>>>>>
>>>>> *** Please cast your vote within the next 72 hours ***
>>>>>
>>>>> The list of fixed issues:
>>>>> http://s.apache.org/A9x
>>>>>
>>>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>>>> for the source and binary artifacts can be found at:
>>>>> http://people.apache.org/~brock/flume-1.3.0-rc2/
>>>>>
>>>>> The tag to be voted on:
>>>>> http://s.apache.org/aVa
>>>>>
>>>>> The KEYS file can be found here:
>>>>> https://dist.apache.org/repos/dist/release/flume/KEYS
>>>>
>>>>
>>>>
>>>> --
>>>> Apache MRUnit - Unit testing MapReduce -
>>>> http://incubator.apache.org/mrunit/
>>>>
>>
>>
>>
>> --
>> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>
> --
> Alexander Alten-Lorenz
> http://mapredit.blogspot.com
> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

This is the second release for Apache Flume as a top-level project,
version 1.3.0. We are voting on release candidate rc3.

*** Please cast your vote within the next 72 hours ***

The list of fixed issues:
https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3

The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
for the source and binary artifacts can be found at:
http://people.apache.org/~brock/flume-1.3.0-rc3/

(Note: attempting to deploy the artifacts to Nexus appears to have
locked me out of Apache LDAP so you'll have to use the artifacts from
the above link or via the source tag below.)

The tag to be voted on:
https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3

The KEYS file can be found here:
https://dist.apache.org/repos/dist/release/flume/KEYS

+1 verified sigs, hashes, built docs, and verified smoke test

On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc3.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc3/
>
> (Note: attempting to deploy the artifacts to Nexus appears to have
> locked me out of Apache LDAP so you'll have to use the artifacts from
> the above link or via the source tag below.)
>
> The tag to be voted on:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3
>
> The KEYS file can be found here:
> https://dist.apache.org/repos/dist/release/flume/KEYS

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

looks good to me, thanks.

+1

cheers,
 Alex

On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED]> wrote:

> +1 verified sigs, hashes, built docs, and verified smoke test
>
> On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>> This is the second release for Apache Flume as a top-level project,
>> version 1.3.0. We are voting on release candidate rc3.
>>
>> *** Please cast your vote within the next 72 hours ***
>>
>> The list of fixed issues:
>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
>>
>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> for the source and binary artifacts can be found at:
>> http://people.apache.org/~brock/flume-1.3.0-rc3/
>>
>> (Note: attempting to deploy the artifacts to Nexus appears to have
>> locked me out of Apache LDAP so you'll have to use the artifacts from
>> the above link or via the source tag below.)
>>
>> The tag to be voted on:
>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3
>>
>> The KEYS file can be found here:
>> https://dist.apache.org/repos/dist/release/flume/KEYS
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

I see the below errors.  Based on following Latest commit...
commit 656e049981df62316e0a817382087297209bf2f3
Author: Brock Noland <[EMAIL PROTECTED]>
Date:   Thu Nov 15 16:28:05 2012 -0600

    FLUME-1716: Update CHANGELOG for rc3

    (Brock Noland via Brock Noland)

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.flume.test.agent.TestFileChannel
Tests run: 2, Failures: 0, *Errors: 2,* Skipped: 0, Time elapsed: 5.248 sec
<<< FAILURE!
Running org.apache.flume.test.agent.TestRpcClient
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.854 sec
Running org.apache.flume.test.agent.TestRpcClientCommunicationFailure
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.413 sec

Results :

Tests in error:
  testInOut(org.apache.flume.test.agent.TestFileChannel): Cannot run
program
"/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin/bin/flume-ng"
(in directory
"/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin"):
error=13, Permission denied
  testInOut(org.apache.flume.test.agent.TestFileChannel): Process not found

Tests run: 4, Failures: 0, Errors: 2, Skipped: 0

[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Flume ...................................... SUCCESS [55.433s]
[INFO] Flume NG SDK ...................................... SUCCESS [59.447s]
[INFO] Flume NG Configuration ............................ SUCCESS [2.025s]
[INFO] Flume NG Core ..................................... SUCCESS
[2:49.995s]
[INFO] Flume NG Sinks .................................... SUCCESS [1.032s]
[INFO] Flume NG HDFS Sink ................................ SUCCESS [38.792s]
[INFO] Flume NG IRC Sink ................................. SUCCESS [1.812s]
[INFO] Flume NG HBase Sink ............................... SUCCESS
[1:20.950s]
[INFO] Flume NG ElasticSearch Sink ....................... SUCCESS [13.275s]
[INFO] Flume Sources ..................................... SUCCESS [0.565s]
[INFO] Flume Scribe Source ............................... SUCCESS [1.672s]
[INFO] Flume NG Channels ................................. SUCCESS [1.101s]
[INFO] Flume NG JDBC channel ............................. SUCCESS [42.526s]
[INFO] Flume NG Node ..................................... SUCCESS [20.195s]
[INFO] Flume NG file-based channel ....................... SUCCESS
[4:11.444s]
[INFO] Flume NG file backed Memory channel ............... SUCCESS [26.813s]
[INFO] Flume legacy Sources .............................. SUCCESS [0.573s]
[INFO] Flume legacy Avro source .......................... SUCCESS [2.035s]
[INFO] Flume legacy Thrift Source ........................ SUCCESS [1.634s]
[INFO] Flume NG Clients .................................. SUCCESS [0.538s]
[INFO] Flume NG Log4j Appender ........................... SUCCESS [2.833s]
[INFO] Flume NG distribution ............................. SUCCESS [22.601s]
[INFO] Flume NG Integration Tests ........................ *FAILURE*
 [27.408s]
[INFO]
------------------------------------------------------------------------

Can you try again or see if there is some environmental issue? I
cannot reproduce locally and jenkins ran find on all of last nights
commits:

https://builds.apache.org/job/flume-trunk/328/

Brock
On Fri, Nov 16, 2012 at 5:46 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
> I see the below errors.  Based on following Latest commit...
> commit 656e049981df62316e0a817382087297209bf2f3
> Author: Brock Noland <[EMAIL PROTECTED]>
> Date:   Thu Nov 15 16:28:05 2012 -0600
>
>     FLUME-1716: Update CHANGELOG for rc3
>
>     (Brock Noland via Brock Noland)
>
>
>
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.flume.test.agent.TestFileChannel
> Tests run: 2, Failures: 0, *Errors: 2,* Skipped: 0, Time elapsed: 5.248 sec
> <<< FAILURE!
> Running org.apache.flume.test.agent.TestRpcClient
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.854 sec
> Running org.apache.flume.test.agent.TestRpcClientCommunicationFailure
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.413 sec
>
> Results :
>
> Tests in error:
>   testInOut(org.apache.flume.test.agent.TestFileChannel): Cannot run
> program
> "/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin/bin/flume-ng"
> (in directory
> "/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin"):
> error=13, Permission denied
>   testInOut(org.apache.flume.test.agent.TestFileChannel): Process not found
>
>
>
> Tests run: 4, Failures: 0, Errors: 2, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Flume ...................................... SUCCESS [55.433s]
> [INFO] Flume NG SDK ...................................... SUCCESS [59.447s]
> [INFO] Flume NG Configuration ............................ SUCCESS [2.025s]
> [INFO] Flume NG Core ..................................... SUCCESS
> [2:49.995s]
> [INFO] Flume NG Sinks .................................... SUCCESS [1.032s]
> [INFO] Flume NG HDFS Sink ................................ SUCCESS [38.792s]
> [INFO] Flume NG IRC Sink ................................. SUCCESS [1.812s]
> [INFO] Flume NG HBase Sink ............................... SUCCESS
> [1:20.950s]
> [INFO] Flume NG ElasticSearch Sink ....................... SUCCESS [13.275s]
> [INFO] Flume Sources ..................................... SUCCESS [0.565s]
> [INFO] Flume Scribe Source ............................... SUCCESS [1.672s]
> [INFO] Flume NG Channels ................................. SUCCESS [1.101s]
> [INFO] Flume NG JDBC channel ............................. SUCCESS [42.526s]
> [INFO] Flume NG Node ..................................... SUCCESS [20.195s]
> [INFO] Flume NG file-based channel ....................... SUCCESS
> [4:11.444s]
> [INFO] Flume NG file backed Memory channel ............... SUCCESS [26.813s]
> [INFO] Flume legacy Sources .............................. SUCCESS [0.573s]
> [INFO] Flume legacy Avro source .......................... SUCCESS [2.035s]
> [INFO] Flume legacy Thrift Source ........................ SUCCESS [1.634s]
> [INFO] Flume NG Clients .................................. SUCCESS [0.538s]
> [INFO] Flume NG Log4j Appender ........................... SUCCESS [2.833s]
> [INFO] Flume NG distribution ............................. SUCCESS [22.601s]
> [INFO] Flume NG Integration Tests ........................ *FAILURE*
>  [27.408s]
> [INFO]
> ------------------------------------------------------------------------

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

I tried the again one two different systems (mac os lion and rhel 6.3)
and was unable to reproduce so I am guessing the issues are
environmental.

On Fri, Nov 16, 2012 at 5:51 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> Can you try again or see if there is some environmental issue? I
> cannot reproduce locally and jenkins ran find on all of last nights
> commits:
>
> https://builds.apache.org/job/flume-trunk/328/
>
> Brock
>
>
> On Fri, Nov 16, 2012 at 5:46 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
>> I see the below errors.  Based on following Latest commit...
>> commit 656e049981df62316e0a817382087297209bf2f3
>> Author: Brock Noland <[EMAIL PROTECTED]>
>> Date:   Thu Nov 15 16:28:05 2012 -0600
>>
>>     FLUME-1716: Update CHANGELOG for rc3
>>
>>     (Brock Noland via Brock Noland)
>>
>>
>>
>> -------------------------------------------------------
>>  T E S T S
>> -------------------------------------------------------
>> Running org.apache.flume.test.agent.TestFileChannel
>> Tests run: 2, Failures: 0, *Errors: 2,* Skipped: 0, Time elapsed: 5.248 sec
>> <<< FAILURE!
>> Running org.apache.flume.test.agent.TestRpcClient
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.854 sec
>> Running org.apache.flume.test.agent.TestRpcClientCommunicationFailure
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.413 sec
>>
>> Results :
>>
>> Tests in error:
>>   testInOut(org.apache.flume.test.agent.TestFileChannel): Cannot run
>> program
>> "/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin/bin/flume-ng"
>> (in directory
>> "/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin"):
>> error=13, Permission denied
>>   testInOut(org.apache.flume.test.agent.TestFileChannel): Process not found
>>
>>
>>
>> Tests run: 4, Failures: 0, Errors: 2, Skipped: 0
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Flume ...................................... SUCCESS [55.433s]
>> [INFO] Flume NG SDK ...................................... SUCCESS [59.447s]
>> [INFO] Flume NG Configuration ............................ SUCCESS [2.025s]
>> [INFO] Flume NG Core ..................................... SUCCESS
>> [2:49.995s]
>> [INFO] Flume NG Sinks .................................... SUCCESS [1.032s]
>> [INFO] Flume NG HDFS Sink ................................ SUCCESS [38.792s]
>> [INFO] Flume NG IRC Sink ................................. SUCCESS [1.812s]
>> [INFO] Flume NG HBase Sink ............................... SUCCESS
>> [1:20.950s]
>> [INFO] Flume NG ElasticSearch Sink ....................... SUCCESS [13.275s]
>> [INFO] Flume Sources ..................................... SUCCESS [0.565s]
>> [INFO] Flume Scribe Source ............................... SUCCESS [1.672s]
>> [INFO] Flume NG Channels ................................. SUCCESS [1.101s]
>> [INFO] Flume NG JDBC channel ............................. SUCCESS [42.526s]
>> [INFO] Flume NG Node ..................................... SUCCESS [20.195s]
>> [INFO] Flume NG file-based channel ....................... SUCCESS
>> [4:11.444s]
>> [INFO] Flume NG file backed Memory channel ............... SUCCESS [26.813s]
>> [INFO] Flume legacy Sources .............................. SUCCESS [0.573s]
>> [INFO] Flume legacy Avro source .......................... SUCCESS [2.035s]
>> [INFO] Flume legacy Thrift Source ........................ SUCCESS [1.634s]
>> [INFO] Flume NG Clients .................................. SUCCESS [0.538s]
>> [INFO] Flume NG Log4j Appender ........................... SUCCESS [2.833s]
>> [INFO] Flume NG distribution ............................. SUCCESS [22.601s]
>> [INFO] Flume NG Integration Tests ........................ *FAILURE*
>>  [27.408s]
>> [INFO]
>> ----------------------------------------------------
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

yup. i tried it on a different box myself.. it built cleanly. So ..
+1

-roshan
On Fri, Nov 16, 2012 at 4:33 PM, Brock Noland <[EMAIL PROTECTED]> wrote:

> I tried the again one two different systems (mac os lion and rhel 6.3)
> and was unable to reproduce so I am guessing the issues are
> environmental.
>
> On Fri, Nov 16, 2012 at 5:51 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> > Can you try again or see if there is some environmental issue? I
> > cannot reproduce locally and jenkins ran find on all of last nights
> > commits:
> >
> > https://builds.apache.org/job/flume-trunk/328/
> >
> > Brock
> >
> >
> > On Fri, Nov 16, 2012 at 5:46 PM, Roshan Naik <[EMAIL PROTECTED]>
> wrote:
> >> I see the below errors.  Based on following Latest commit...
> >> commit 656e049981df62316e0a817382087297209bf2f3
> >> Author: Brock Noland <[EMAIL PROTECTED]>
> >> Date:   Thu Nov 15 16:28:05 2012 -0600
> >>
> >>     FLUME-1716: Update CHANGELOG for rc3
> >>
> >>     (Brock Noland via Brock Noland)
> >>
> >>
> >>
> >> -------------------------------------------------------
> >>  T E S T S
> >> -------------------------------------------------------
> >> Running org.apache.flume.test.agent.TestFileChannel
> >> Tests run: 2, Failures: 0, *Errors: 2,* Skipped: 0, Time elapsed: 5.248
> sec
> >> <<< FAILURE!
> >> Running org.apache.flume.test.agent.TestRpcClient
> >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.854
> sec
> >> Running org.apache.flume.test.agent.TestRpcClientCommunicationFailure
> >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.413
> sec
> >>
> >> Results :
> >>
> >> Tests in error:
> >>   testInOut(org.apache.flume.test.agent.TestFileChannel): Cannot run
> >> program
> >>
> "/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin/bin/flume-ng"
> >> (in directory
> >>
> "/Users/roshan/Projects/flume-git-release/flume-ng-tests/target/test/flume7556416910922042256_stage_dir/apache-flume-1.3.0-bin"):
> >> error=13, Permission denied
> >>   testInOut(org.apache.flume.test.agent.TestFileChannel): Process not
> found
> >>
> >>
> >>
> >> Tests run: 4, Failures: 0, Errors: 2, Skipped: 0
> >>
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Reactor Summary:
> >> [INFO]
> >> [INFO] Apache Flume ...................................... SUCCESS
> [55.433s]
> >> [INFO] Flume NG SDK ...................................... SUCCESS
> [59.447s]
> >> [INFO] Flume NG Configuration ............................ SUCCESS
> [2.025s]
> >> [INFO] Flume NG Core ..................................... SUCCESS
> >> [2:49.995s]
> >> [INFO] Flume NG Sinks .................................... SUCCESS
> [1.032s]
> >> [INFO] Flume NG HDFS Sink ................................ SUCCESS
> [38.792s]
> >> [INFO] Flume NG IRC Sink ................................. SUCCESS
> [1.812s]
> >> [INFO] Flume NG HBase Sink ............................... SUCCESS
> >> [1:20.950s]
> >> [INFO] Flume NG ElasticSearch Sink ....................... SUCCESS
> [13.275s]
> >> [INFO] Flume Sources ..................................... SUCCESS
> [0.565s]
> >> [INFO] Flume Scribe Source ............................... SUCCESS
> [1.672s]
> >> [INFO] Flume NG Channels ................................. SUCCESS
> [1.101s]
> >> [INFO] Flume NG JDBC channel ............................. SUCCESS
> [42.526s]
> >> [INFO] Flume NG Node ..................................... SUCCESS
> [20.195s]
> >> [INFO] Flume NG file-based channel ....................... SUCCESS
> >> [4:11.444s]
> >> [INFO] Flume NG file backed Memory channel ............... SUCCESS
> [26.813s]
> >> [INFO] Flume legacy Sources .............................. SUCCESS
> [0.573s]
> >> [INFO] Flume legacy Avro source .......................... SUCCESS
> [2.035s]
> >> [INFO] Flume legacy Thrift Source ........................ SUCCESS
> [1.634s]
> >> [INFO] Flume NG Clients .................................. SUCCESS

I've noticed that LICENSE file contains entry protobuf-<version>.jar whereas our binary artifacts seems to be pulling protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a blocker to me, but it would be great if someone else with more deeper licensing knowledge would confirm that. As long as this is fine, I'm +1 on the release.

Checked:
* Checksums, signatures seems fine
* "mvn clean compile test verify package" passes for source artifact
* "mvn verify" passes for binary artifact
* CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me

Notes:
* Filled FLUME-1719: Example export command in README do not properly close the string
* Filled FLUME-1720: LICENSE file contain entry for protobuf-<version>.jar, however proper artifact name is protobuf-java-<version>.jar

Jarcec

Links:
1: https://issues.apache.org/jira/browse/FLUME-1720

On Fri, Nov 16, 2012 at 07:49:13AM +0100, Alexander Alten-Lorenz wrote:
> looks good to me, thanks.
>
> +1
>
> cheers,
>  Alex
>
> On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>
> > +1 verified sigs, hashes, built docs, and verified smoke test
> >
> > On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> >> This is the second release for Apache Flume as a top-level project,
> >> version 1.3.0. We are voting on release candidate rc3.
> >>
> >> *** Please cast your vote within the next 72 hours ***
> >>
> >> The list of fixed issues:
> >> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
> >>
> >> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> >> for the source and binary artifacts can be found at:
> >> http://people.apache.org/~brock/flume-1.3.0-rc3/
> >>
> >> (Note: attempting to deploy the artifacts to Nexus appears to have
> >> locked me out of Apache LDAP so you'll have to use the artifacts from
> >> the above link or via the source tag below.)
> >>
> >> The tag to be voted on:
> >> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3
> >>
> >> The KEYS file can be found here:
> >> https://dist.apache.org/repos/dist/release/flume/KEYS
> >
> >
> >
> > --
> > Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>
> --
> Alexander Alten-Lorenz
> http://mapredit.blogspot.com
> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>

Thanks Jarek, I don't think it's a blocker but we should definitely fix it.

FWIW, hadoop's LICENSE.txt doesn't even list the licenses of binaries
and Crunch was just released with many defects to this file.

On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]> wrote:
> I've noticed that LICENSE file contains entry protobuf-<version>.jar whereas our binary artifacts seems to be pulling protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a blocker to me, but it would be great if someone else with more deeper licensing knowledge would confirm that. As long as this is fine, I'm +1 on the release.
>
> Checked:
> * Checksums, signatures seems fine
> * "mvn clean compile test verify package" passes for source artifact
> * "mvn verify" passes for binary artifact
> * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
>
> Notes:
> * Filled FLUME-1719: Example export command in README do not properly close the string
> * Filled FLUME-1720: LICENSE file contain entry for protobuf-<version>.jar, however proper artifact name is protobuf-java-<version>.jar
>
> Jarcec
>
> Links:
> 1: https://issues.apache.org/jira/browse/FLUME-1720
>
> On Fri, Nov 16, 2012 at 07:49:13AM +0100, Alexander Alten-Lorenz wrote:
>> looks good to me, thanks.
>>
>> +1
>>
>> cheers,
>>  Alex
>>
>> On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>
>> > +1 verified sigs, hashes, built docs, and verified smoke test
>> >
>> > On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>> >> This is the second release for Apache Flume as a top-level project,
>> >> version 1.3.0. We are voting on release candidate rc3.
>> >>
>> >> *** Please cast your vote within the next 72 hours ***
>> >>
>> >> The list of fixed issues:
>> >> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
>> >>
>> >> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> >> for the source and binary artifacts can be found at:
>> >> http://people.apache.org/~brock/flume-1.3.0-rc3/
>> >>
>> >> (Note: attempting to deploy the artifacts to Nexus appears to have
>> >> locked me out of Apache LDAP so you'll have to use the artifacts from
>> >> the above link or via the source tag below.)
>> >>
>> >> The tag to be voted on:
>> >> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3
>> >>
>> >> The KEYS file can be found here:
>> >> https://dist.apache.org/repos/dist/release/flume/KEYS
>> >
>> >
>> >
>> > --
>> > Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>>
>> --
>> Alexander Alten-Lorenz
>> http://mapredit.blogspot.com
>> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

+1 on the release

On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED]> wrote:

> Thanks Jarek, I don't think it's a blocker but we should definitely fix it.
>
> FWIW, hadoop's LICENSE.txt doesn't even list the licenses of binaries
> and Crunch was just released with many defects to this file.
>
> On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]> wrote:
>> I've noticed that LICENSE file contains entry protobuf-<version>.jar whereas our binary artifacts seems to be pulling protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a blocker to me, but it would be great if someone else with more deeper licensing knowledge would confirm that. As long as this is fine, I'm +1 on the release.
>>
>> Checked:
>> * Checksums, signatures seems fine
>> * "mvn clean compile test verify package" passes for source artifact
>> * "mvn verify" passes for binary artifact
>> * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
>>
>> Notes:
>> * Filled FLUME-1719: Example export command in README do not properly close the string
>> * Filled FLUME-1720: LICENSE file contain entry for protobuf-<version>.jar, however proper artifact name is protobuf-java-<version>.jar
>>
>> Jarcec
>>
>> Links:
>> 1: https://issues.apache.org/jira/browse/FLUME-1720
>>
>> On Fri, Nov 16, 2012 at 07:49:13AM +0100, Alexander Alten-Lorenz wrote:
>>> looks good to me, thanks.
>>>
>>> +1
>>>
>>> cheers,
>>> Alex
>>>
>>> On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>>
>>>> +1 verified sigs, hashes, built docs, and verified smoke test
>>>>
>>>> On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>>>> This is the second release for Apache Flume as a top-level project,
>>>>> version 1.3.0. We are voting on release candidate rc3.
>>>>>
>>>>> *** Please cast your vote within the next 72 hours ***
>>>>>
>>>>> The list of fixed issues:
>>>>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
>>>>>
>>>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>>>> for the source and binary artifacts can be found at:
>>>>> http://people.apache.org/~brock/flume-1.3.0-rc3/
>>>>>
>>>>> (Note: attempting to deploy the artifacts to Nexus appears to have
>>>>> locked me out of Apache LDAP so you'll have to use the artifacts from
>>>>> the above link or via the source tag below.)
>>>>>
>>>>> The tag to be voted on:
>>>>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3
>>>>>
>>>>> The KEYS file can be found here:
>>>>> https://dist.apache.org/repos/dist/release/flume/KEYS
>>>>
>>>>
>>>>
>>>> --
>>>> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>>>
>>> --
>>> Alexander Alten-Lorenz
>>> http://mapredit.blogspot.com
>>> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

+1

- Alex

On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED]> wrote:

> +1 on the release
>
> On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>
>> Thanks Jarek, I don't think it's a blocker but we should definitely fix it.
>>
>> FWIW, hadoop's LICENSE.txt doesn't even list the licenses of binaries
>> and Crunch was just released with many defects to this file.
>>
>> On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]> wrote:
>>> I've noticed that LICENSE file contains entry protobuf-<version>.jar whereas our binary artifacts seems to be pulling protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a blocker to me, but it would be great if someone else with more deeper licensing knowledge would confirm that. As long as this is fine, I'm +1 on the release.
>>>
>>> Checked:
>>> * Checksums, signatures seems fine
>>> * "mvn clean compile test verify package" passes for source artifact
>>> * "mvn verify" passes for binary artifact
>>> * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
>>>
>>> Notes:
>>> * Filled FLUME-1719: Example export command in README do not properly close the string
>>> * Filled FLUME-1720: LICENSE file contain entry for protobuf-<version>.jar, however proper artifact name is protobuf-java-<version>.jar
>>>
>>> Jarcec
>>>
>>> Links:
>>> 1: https://issues.apache.org/jira/browse/FLUME-1720
>>>
>>> On Fri, Nov 16, 2012 at 07:49:13AM +0100, Alexander Alten-Lorenz wrote:
>>>> looks good to me, thanks.
>>>>
>>>> +1
>>>>
>>>> cheers,
>>>> Alex
>>>>
>>>> On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> +1 verified sigs, hashes, built docs, and verified smoke test
>>>>>
>>>>> On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>>>>> This is the second release for Apache Flume as a top-level project,
>>>>>> version 1.3.0. We are voting on release candidate rc3.
>>>>>>
>>>>>> *** Please cast your vote within the next 72 hours ***
>>>>>>
>>>>>> The list of fixed issues:
>>>>>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
>>>>>>
>>>>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>>>>> for the source and binary artifacts can be found at:
>>>>>> http://people.apache.org/~brock/flume-1.3.0-rc3/
>>>>>>
>>>>>> (Note: attempting to deploy the artifacts to Nexus appears to have
>>>>>> locked me out of Apache LDAP so you'll have to use the artifacts from
>>>>>> the above link or via the source tag below.)
>>>>>>
>>>>>> The tag to be voted on:
>>>>>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3
>>>>>>
>>>>>> The KEYS file can be found here:
>>>>>> https://dist.apache.org/repos/dist/release/flume/KEYS
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>>>>
>>>> --
>>>> Alexander Alten-Lorenz
>>>> http://mapredit.blogspot.com
>>>> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>>
>>
>>
>> --
>> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

+1.

Here is what I checked:
1. Checksums and signatures look good.
2. Verified license file, readme, change log and notice file (more on this below).
3. Built, ran unit tests, ran an agent with the sample config - looks good.
Additional notes:
The LICENSE file seems to list three libraries which we do not pull in:

commons logging
http-client
http-core
We probably should remove these from the license file too.

Thanks,
Hari
--
Hari Shreedharan
On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz wrote:

> +1
>
> - Alex
>
> On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>
> > +1 on the release
> >
> > On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> >
> > > Thanks Jarek, I don't think it's a blocker but we should definitely fix it.
> > >
> > > FWIW, hadoop's LICENSE.txt doesn't even list the licenses of binaries
> > > and Crunch was just released with many defects to this file.
> > >
> > > On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > I've noticed that LICENSE file contains entry protobuf-<version>.jar whereas our binary artifacts seems to be pulling protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a blocker to me, but it would be great if someone else with more deeper licensing knowledge would confirm that. As long as this is fine, I'm +1 on the release.
> > > >
> > > > Checked:
> > > > * Checksums, signatures seems fine
> > > > * "mvn clean compile test verify package" passes for source artifact
> > > > * "mvn verify" passes for binary artifact
> > > > * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
> > > >
> > > > Notes:
> > > > * Filled FLUME-1719: Example export command in README do not properly close the string
> > > > * Filled FLUME-1720: LICENSE file contain entry for protobuf-<version>.jar, however proper artifact name is protobuf-java-<version>.jar
> > > >
> > > > Jarcec
> > > >
> > > > Links:
> > > > 1: https://issues.apache.org/jira/browse/FLUME-1720
> > > >
> > > > On Fri, Nov 16, 2012 at 07:49:13AM +0100, Alexander Alten-Lorenz wrote:
> > > > > looks good to me, thanks.
> > > > >
> > > > > +1
> > > > >
> > > > > cheers,
> > > > > Alex
> > > > >
> > > > > On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > >
> > > > > > +1 verified sigs, hashes, built docs, and verified smoke test
> > > > > >
> > > > > > On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > > > > This is the second release for Apache Flume as a top-level project,
> > > > > > > version 1.3.0. We are voting on release candidate rc3.
> > > > > > >
> > > > > > > *** Please cast your vote within the next 72 hours ***
> > > > > > >
> > > > > > > The list of fixed issues:
> > > > > > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
> > > > > > >
> > > > > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > > > > > > for the source and binary artifacts can be found at:
> > > > > > > http://people.apache.org/~brock/flume-1.3.0-rc3/
> > > > > > >
> > > > > > > (Note: attempting to deploy the artifacts to Nexus appears to have
> > > > > > > locked me out of Apache LDAP so you'll have to use the artifacts from
> > > > > > > the above link or via the source tag below.)
> > > > > > >
> > > > > > > The tag to be voted on:
> > > > > > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3
> > > > > > >
> > > > > > > The KEYS file can be found here:
> > > > > > > https://dist.apache.org/repos/dist/release/flume/KEYS
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Thanks Hari, I have created FLUME-1722 for this purpose.

https://issues.apache.org/jira/browse/FLUME-1722

Brock

On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
<[EMAIL PROTECTED]> wrote:
> +1.
>
> Here is what I checked:
> 1. Checksums and signatures look good.
> 2. Verified license file, readme, change log and notice file (more on this below).
> 3. Built, ran unit tests, ran an agent with the sample config - looks good.
>
>
> Additional notes:
> The LICENSE file seems to list three libraries which we do not pull in:
>
> commons logging
> http-client
> http-core
>
>
> We probably should remove these from the license file too.
>
>
>
> Thanks,
> Hari
> --
> Hari Shreedharan
>
>
> On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz wrote:
>
>> +1
>>
>> - Alex
>>
>> On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>>
>> > +1 on the release
>> >
>> > On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>> >
>> > > Thanks Jarek, I don't think it's a blocker but we should definitely fix it.
>> > >
>> > > FWIW, hadoop's LICENSE.txt doesn't even list the licenses of binaries
>> > > and Crunch was just released with many defects to this file.
>> > >
>> > > On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>> > > > I've noticed that LICENSE file contains entry protobuf-<version>.jar whereas our binary artifacts seems to be pulling protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a blocker to me, but it would be great if someone else with more deeper licensing knowledge would confirm that. As long as this is fine, I'm +1 on the release.
>> > > >
>> > > > Checked:
>> > > > * Checksums, signatures seems fine
>> > > > * "mvn clean compile test verify package" passes for source artifact
>> > > > * "mvn verify" passes for binary artifact
>> > > > * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
>> > > >
>> > > > Notes:
>> > > > * Filled FLUME-1719: Example export command in README do not properly close the string
>> > > > * Filled FLUME-1720: LICENSE file contain entry for protobuf-<version>.jar, however proper artifact name is protobuf-java-<version>.jar
>> > > >
>> > > > Jarcec
>> > > >
>> > > > Links:
>> > > > 1: https://issues.apache.org/jira/browse/FLUME-1720
>> > > >
>> > > > On Fri, Nov 16, 2012 at 07:49:13AM +0100, Alexander Alten-Lorenz wrote:
>> > > > > looks good to me, thanks.
>> > > > >
>> > > > > +1
>> > > > >
>> > > > > cheers,
>> > > > > Alex
>> > > > >
>> > > > > On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>> > > > >
>> > > > > > +1 verified sigs, hashes, built docs, and verified smoke test
>> > > > > >
>> > > > > > On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>> > > > > > > This is the second release for Apache Flume as a top-level project,
>> > > > > > > version 1.3.0. We are voting on release candidate rc3.
>> > > > > > >
>> > > > > > > *** Please cast your vote within the next 72 hours ***
>> > > > > > >
>> > > > > > > The list of fixed issues:
>> > > > > > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
>> > > > > > >
>> > > > > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> > > > > > > for the source and binary artifacts can be found at:
>> > > > > > > http://people.apache.org/~brock/flume-1.3.0-rc3/
>> > > > > > >
>> > > > > > > (Note: attempting to deploy the artifacts to Nexus appears to have
>> > > > > > > locked me out of Apache LDAP so you'll have to use the artifacts from
>> > > > > > > the above link or via the source tag below.)
>> > > > > > >
>> > > > > > > The tag to be voted on:
>> > > > > > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=656e049981df62316e0a817382087297209bf2f3

Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

When I was reviewing the libs I noticed that netty is in there twice with 2
different versions. I don't think we should ship like that.

So, -1 from me on this RC.

Details and a patch are here:
https://issues.apache.org/jira/browse/FLUME-1723

Regards,
Mike

On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <[EMAIL PROTECTED]> wrote:

> Thanks Hari, I have created FLUME-1722 for this purpose.
>
> https://issues.apache.org/jira/browse/FLUME-1722
>
> Brock
>
> On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> <[EMAIL PROTECTED]> wrote:
> > +1.
> >
> > Here is what I checked:
> > 1. Checksums and signatures look good.
> > 2. Verified license file, readme, change log and notice file (more on
> this below).
> > 3. Built, ran unit tests, ran an agent with the sample config - looks
> good.
> >
> >
> > Additional notes:
> > The LICENSE file seems to list three libraries which we do not pull in:
> >
> > commons logging
> > http-client
> > http-core
> >
> >
> > We probably should remove these from the license file too.
> >
> >
> >
> > Thanks,
> > Hari
> > --
> > Hari Shreedharan
> >
> >
> > On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz wrote:
> >
> >> +1
> >>
> >> - Alex
> >>
> >> On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED] (mailto:
> [EMAIL PROTECTED])> wrote:
> >>
> >> > +1 on the release
> >> >
> >> > On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED](mailto:
> [EMAIL PROTECTED])> wrote:
> >> >
> >> > > Thanks Jarek, I don't think it's a blocker but we should definitely
> fix it.
> >> > >
> >> > > FWIW, hadoop's LICENSE.txt doesn't even list the licenses of
> binaries
> >> > > and Crunch was just released with many defects to this file.
> >> > >
> >> > > On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <
> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> >> > > > I've noticed that LICENSE file contains entry
> protobuf-<version>.jar whereas our binary artifacts seems to be pulling
> protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a
> blocker to me, but it would be great if someone else with more deeper
> licensing knowledge would confirm that. As long as this is fine, I'm +1 on
> the release.
> >> > > >
> >> > > > Checked:
> >> > > > * Checksums, signatures seems fine
> >> > > > * "mvn clean compile test verify package" passes for source
> artifact
> >> > > > * "mvn verify" passes for binary artifact
> >> > > > * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
> >> > > >
> >> > > > Notes:
> >> > > > * Filled FLUME-1719: Example export command in README do not
> properly close the string
> >> > > > * Filled FLUME-1720: LICENSE file contain entry for
> protobuf-<version>.jar, however proper artifact name is
> protobuf-java-<version>.jar
> >> > > >
> >> > > > Jarcec
> >> > > >
> >> > > > Links:
> >> > > > 1: https://issues.apache.org/jira/browse/FLUME-1720
> >> > > >
> >> > > > On Fri, Nov 16, 2012 at 07:49:13AM +0100, Alexander Alten-Lorenz
> wrote:
> >> > > > > looks good to me, thanks.
> >> > > > >
> >> > > > > +1
> >> > > > >
> >> > > > > cheers,
> >> > > > > Alex
> >> > > > >
> >> > > > > On Nov 16, 2012, at 12:21 AM, Brock Noland <[EMAIL PROTECTED](mailto:
> [EMAIL PROTECTED])> wrote:
> >> > > > >
> >> > > > > > +1 verified sigs, hashes, built docs, and verified smoke test
> >> > > > > >
> >> > > > > > On Thu, Nov 15, 2012 at 5:16 PM, Brock Noland <
> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> >> > > > > > > This is the second release for Apache Flume as a top-level
> project,
> >> > > > > > > version 1.3.0. We are voting on release candidate rc3.
> >> > > > > > >
> >> > > > > > > *** Please cast your vote within the next 72 hours ***
> >> > > > > > >
> >> > > > > > > The list of fixed issues:
> >> > > > > > >
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=656e049981df62316e0a817382087297209bf2f3
> >> > > > > > >
> >> > > > > > > The tarball (*.tar.gz), signature (*.asc), and checksums

Mike,

I committed your patch for flume-1.4, and trunk.
Brock: As I posted on the jira, if you want it committed to flume-1.3. the RM should decide if another RC is required (looks like there are 3 PMC +1 already, unless someone withdraws the +1). If required, please cherry-pick the patch to flume-1.3.0 and roll another RC.
Thanks,
Hari

--
Hari Shreedharan
On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:

> When I was reviewing the libs I noticed that netty is in there twice with 2
> different versions. I don't think we should ship like that.
>
> So, -1 from me on this RC.
>
> Details and a patch are here:
> https://issues.apache.org/jira/browse/FLUME-1723
>
> Regards,
> Mike
>
> On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>
> > Thanks Hari, I have created FLUME-1722 for this purpose.
> >
> > https://issues.apache.org/jira/browse/FLUME-1722
> >
> > Brock
> >
> > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > +1.
> > >
> > > Here is what I checked:
> > > 1. Checksums and signatures look good.
> > > 2. Verified license file, readme, change log and notice file (more on
> > >
> >
> > this below).
> > > 3. Built, ran unit tests, ran an agent with the sample config - looks
> >
> > good.
> > >
> > >
> > > Additional notes:
> > > The LICENSE file seems to list three libraries which we do not pull in:
> > >
> > > commons logging
> > > http-client
> > > http-core
> > >
> > >
> > > We probably should remove these from the license file too.
> > >
> > >
> > >
> > > Thanks,
> > > Hari
> > > --
> > > Hari Shreedharan
> > >
> > >
> > > On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz wrote:
> > >
> > > > +1
> > > >
> > > > - Alex
> > > >
> > > > On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) (mailto:
> > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > >
> > > > > +1 on the release
> > > > >
> > > > > On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > >
> > > > > > Thanks Jarek, I don't think it's a blocker but we should definitely
> > fix it.
> > > > > >
> > > > > > FWIW, hadoop's LICENSE.txt doesn't even list the licenses of
> > binaries
> > > > > > and Crunch was just released with many defects to this file.
> > > > > >
> > > > > > On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <
> > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > > > > I've noticed that LICENSE file contains entry
> > > > > >
> > > > >
> > > >
> > >
> >
> > protobuf-<version>.jar whereas our binary artifacts seems to be pulling
> > protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems as a
> > blocker to me, but it would be great if someone else with more deeper
> > licensing knowledge would confirm that. As long as this is fine, I'm +1 on
> > the release.
> > > > > > >
> > > > > > > Checked:
> > > > > > > * Checksums, signatures seems fine
> > > > > > > * "mvn clean compile test verify package" passes for source
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > artifact
> > > > > > > * "mvn verify" passes for binary artifact
> > > > > > > * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
> > > > > > >
> > > > > > > Notes:
> > > > > > > * Filled FLUME-1719: Example export command in README do not
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > properly close the string
> > > > > > > * Filled FLUME-1720: LICENSE file contain entry for
> > > > > >
> > > > >
> > > >
> > >
> >
> > protobuf-<version>.jar, however proper artifact name is
> > protobuf-java-<version>.jar
> > > > > > >
> > > > > > > Jarcec
> > > > > > >
> > > > > > > Links:
> > > > > > > 1: https://issues.apache.org/jira/browse/FLUME-1720
> > > > > > >
>

Hari,
You're correct that a -1 vote does not veto a release. A savvy user could
delete one of the jars before deploying to production, but why make them do
that.

Thanks for the commit.

Regards,
Mike

On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <[EMAIL PROTECTED]
> wrote:

> Mike,
>
> I committed your patch for flume-1.4, and trunk.
>
>
> Brock: As I posted on the jira, if you want it committed to flume-1.3. the
> RM should decide if another RC is required (looks like there are 3 PMC +1
> already, unless someone withdraws the +1). If required, please cherry-pick
> the patch to flume-1.3.0 and roll another RC.
>
>
> Thanks,
> Hari
>
> --
> Hari Shreedharan
>
>
> On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
>
> > When I was reviewing the libs I noticed that netty is in there twice
> with 2
> > different versions. I don't think we should ship like that.
> >
> > So, -1 from me on this RC.
> >
> > Details and a patch are here:
> > https://issues.apache.org/jira/browse/FLUME-1723
> >
> > Regards,
> > Mike
> >
> > On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <[EMAIL PROTECTED](mailto:
> [EMAIL PROTECTED])> wrote:
> >
> > > Thanks Hari, I have created FLUME-1722 for this purpose.
> > >
> > > https://issues.apache.org/jira/browse/FLUME-1722
> > >
> > > Brock
> > >
> > > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > +1.
> > > >
> > > > Here is what I checked:
> > > > 1. Checksums and signatures look good.
> > > > 2. Verified license file, readme, change log and notice file (more on
> > > >
> > >
> > > this below).
> > > > 3. Built, ran unit tests, ran an agent with the sample config - looks
> > >
> > > good.
> > > >
> > > >
> > > > Additional notes:
> > > > The LICENSE file seems to list three libraries which we do not pull
> in:
> > > >
> > > > commons logging
> > > > http-client
> > > > http-core
> > > >
> > > >
> > > > We probably should remove these from the license file too.
> > > >
> > > >
> > > >
> > > > Thanks,
> > > > Hari
> > > > --
> > > > Hari Shreedharan
> > > >
> > > >
> > > > On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz
> wrote:
> > > >
> > > > > +1
> > > > >
> > > > > - Alex
> > > > >
> > > > > On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED](mailto:
> [EMAIL PROTECTED]) (mailto:
> > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > >
> > > > > > +1 on the release
> > > > > >
> > > > > > On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED](mailto:
> [EMAIL PROTECTED])(mailto:
> > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > > >
> > > > > > > Thanks Jarek, I don't think it's a blocker but we should
> definitely
> > > fix it.
> > > > > > >
> > > > > > > FWIW, hadoop's LICENSE.txt doesn't even list the licenses of
> > > binaries
> > > > > > > and Crunch was just released with many defects to this file.
> > > > > > >
> > > > > > > On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <
> > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > > > > > I've noticed that LICENSE file contains entry
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > protobuf-<version>.jar whereas our binary artifacts seems to be pulling
> > > protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems
> as a
> > > blocker to me, but it would be great if someone else with more deeper
> > > licensing knowledge would confirm that. As long as this is fine, I'm
> +1 on
> > > the release.
> > > > > > > >
> > > > > > > > Checked:
> > > > > > > > * Checksums, signatures seems fine
> > > > > > > > * "mvn clean compile test verify package" passes for source
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > artifact
> > > > > > > > * "mvn verify" passes for binary artifact
> > > > > > > > * CHANGELOG, NOTICE, README, DEVNOTES files seems fine to me
> > > > > > > >
> > > > > > > > Notes:
> > > > > > > > * Filled FLUME-1719: Example export command in README do not

Ok, let's do another rc since the same lobs with different versions is probably bad.  

Also I think it's fine to commit to 1.3 without another rc since we are voting on a tag, not the branch.  

--
Brock Noland
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:

> Hari,
> You're correct that a -1 vote does not veto a release. A savvy user could
> delete one of the jars before deploying to production, but why make them do
> that.
>
> Thanks for the commit.
>
> Regards,
> Mike
>
> On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <[EMAIL PROTECTED]
> > wrote:
>
>
> > Mike,
> >
> > I committed your patch for flume-1.4, and trunk.
> >
> >
> > Brock: As I posted on the jira, if you want it committed to flume-1.3. the
> > RM should decide if another RC is required (looks like there are 3 PMC +1
> > already, unless someone withdraws the +1). If required, please cherry-pick
> > the patch to flume-1.3.0 and roll another RC.
> >
> >
> > Thanks,
> > Hari
> >
> > --
> > Hari Shreedharan
> >
> >
> > On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
> >
> > > When I was reviewing the libs I noticed that netty is in there twice
> > with 2
> > > different versions. I don't think we should ship like that.
> > >
> > > So, -1 from me on this RC.
> > >
> > > Details and a patch are here:
> > > https://issues.apache.org/jira/browse/FLUME-1723
> > >
> > > Regards,
> > > Mike
> > >
> > > On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <[EMAIL PROTECTED](mailto:
> > [EMAIL PROTECTED])> wrote:
> > >
> > > > Thanks Hari, I have created FLUME-1722 for this purpose.
> > > >
> > > > https://issues.apache.org/jira/browse/FLUME-1722
> > > >
> > > > Brock
> > > >
> > > > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > > > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > > +1.
> > > > >
> > > > > Here is what I checked:
> > > > > 1. Checksums and signatures look good.
> > > > > 2. Verified license file, readme, change log and notice file (more on
> > > > >
> > > >
> > > >
> > > > this below).
> > > > > 3. Built, ran unit tests, ran an agent with the sample config - looks
> > > >
> > > >
> > > > good.
> > > > >
> > > > >
> > > > > Additional notes:
> > > > > The LICENSE file seems to list three libraries which we do not pull
> > > > >
> > > >
> > > >
> > >
> > >
> >
> > in:
> > > > >
> > > > > commons logging
> > > > > http-client
> > > > > http-core
> > > > >
> > > > >
> > > > > We probably should remove these from the license file too.
> > > > >
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Hari
> > > > > --
> > > > > Hari Shreedharan
> > > > >
> > > > >
> > > > > On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz
> > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > - Alex
> > > > > >
> > > > > > On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED](mailto:
> > [EMAIL PROTECTED]) (mailto:
> > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > > >
> > > > > > > +1 on the release
> > > > > > >
> > > > > > > On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED](mailto:
> > [EMAIL PROTECTED])(mailto:
> > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > > > >
> > > > > > > > Thanks Jarek, I don't think it's a blocker but we should
> > definitely
> > > > fix it.
> > > > > > > >
> > > > > > > > FWIW, hadoop's LICENSE.txt doesn't even list the licenses of
> > > > binaries
> > > > > > > > and Crunch was just released with many defects to this file.
> > > > > > > >
> > > > > > > > On Fri, Nov 16, 2012 at 8:42 PM, Jarek Jarcec Cecho <
> > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > > > > > > I've noticed that LICENSE file contains entry
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > protobuf-<version>.jar whereas our binary artifacts seems to be pulling
> > > > protobuf-java-<version>.jar (filled FLUME-1720 [1]). It do need seems

Done! Thanks Mike, Brock!
Hari

--
Hari Shreedharan
On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:

> Ok, let's do another rc since the same lobs with different versions is probably bad.
>
> Also I think it's fine to commit to 1.3 without another rc since we are voting on a tag, not the branch.
>
> --
> Brock Noland
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>
>
> On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
>
> > Hari,
> > You're correct that a -1 vote does not veto a release. A savvy user could
> > delete one of the jars before deploying to production, but why make them do
> > that.
> >
> > Thanks for the commit.
> >
> > Regards,
> > Mike
> >
> > On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
> > > wrote:
> >
> >
> >
> > > Mike,
> > >
> > > I committed your patch for flume-1.4, and trunk.
> > >
> > >
> > > Brock: As I posted on the jira, if you want it committed to flume-1.3. the
> > > RM should decide if another RC is required (looks like there are 3 PMC +1
> > > already, unless someone withdraws the +1). If required, please cherry-pick
> > > the patch to flume-1.3.0 and roll another RC.
> > >
> > >
> > > Thanks,
> > > Hari
> > >
> > > --
> > > Hari Shreedharan
> > >
> > >
> > > On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
> > >
> > > > When I was reviewing the libs I noticed that netty is in there twice
> > > with 2
> > > > different versions. I don't think we should ship like that.
> > > >
> > > > So, -1 from me on this RC.
> > > >
> > > > Details and a patch are here:
> > > > https://issues.apache.org/jira/browse/FLUME-1723
> > > >
> > > > Regards,
> > > > Mike
> > > >
> > > > On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > >
> > > > > Thanks Hari, I have created FLUME-1722 for this purpose.
> > > > >
> > > > > https://issues.apache.org/jira/browse/FLUME-1722
> > > > >
> > > > > Brock
> > > > >
> > > > > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > > > > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > > > +1.
> > > > > >
> > > > > > Here is what I checked:
> > > > > > 1. Checksums and signatures look good.
> > > > > > 2. Verified license file, readme, change log and notice file (more on
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > this below).
> > > > > > 3. Built, ran unit tests, ran an agent with the sample config - looks
> > > > >
> > > > >
> > > > >
> > > > > good.
> > > > > >
> > > > > >
> > > > > > Additional notes:
> > > > > > The LICENSE file seems to list three libraries which we do not pull
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > in:
> > > > > >
> > > > > > commons logging
> > > > > > http-client
> > > > > > http-core
> > > > > >
> > > > > >
> > > > > > We probably should remove these from the license file too.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > > Hari
> > > > > > --
> > > > > > Hari Shreedharan
> > > > > >
> > > > > >
> > > > > > On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz
> > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > - Alex
> > > > > > >
> > > > > > > On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])) (mailto:
> > > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > > > >
> > > > > > > > +1 on the release
> > > > > > > >
> > > > > > > > On Nov 16, 2012, at 6:56 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))(mailto:
> > > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > > > > >
> > > > > > > > > Thanks Jarek, I don't think it's a blocker but we should

I think that's the right way to go. Sorry for causing trouble guys! :)

Regards,
Mike
On Sat, Nov 17, 2012 at 7:13 PM, Hari Shreedharan <[EMAIL PROTECTED]
> wrote:

> Done! Thanks Mike, Brock!
>
>
> Hari
>
> --
> Hari Shreedharan
>
>
> On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:
>
> > Ok, let's do another rc since the same lobs with different versions is
> probably bad.
> >
> > Also I think it's fine to commit to 1.3 without another rc since we are
> voting on a tag, not the branch.
> >
> > --
> > Brock Noland
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> >
> >
> > On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
> >
> > > Hari,
> > > You're correct that a -1 vote does not veto a release. A savvy user
> could
> > > delete one of the jars before deploying to production, but why make
> them do
> > > that.
> > >
> > > Thanks for the commit.
> > >
> > > Regards,
> > > Mike
> > >
> > > On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <
> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
> > > > wrote:
> > >
> > >
> > >
> > > > Mike,
> > > >
> > > > I committed your patch for flume-1.4, and trunk.
> > > >
> > > >
> > > > Brock: As I posted on the jira, if you want it committed to
> flume-1.3. the
> > > > RM should decide if another RC is required (looks like there are 3
> PMC +1
> > > > already, unless someone withdraws the +1). If required, please
> cherry-pick
> > > > the patch to flume-1.3.0 and roll another RC.
> > > >
> > > >
> > > > Thanks,
> > > > Hari
> > > >
> > > > --
> > > > Hari Shreedharan
> > > >
> > > >
> > > > On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
> > > >
> > > > > When I was reviewing the libs I noticed that netty is in there
> twice
> > > > with 2
> > > > > different versions. I don't think we should ship like that.
> > > > >
> > > > > So, -1 from me on this RC.
> > > > >
> > > > > Details and a patch are here:
> > > > > https://issues.apache.org/jira/browse/FLUME-1723
> > > > >
> > > > > Regards,
> > > > > Mike
> > > > >
> > > > > On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <[EMAIL PROTECTED](mailto:
> [EMAIL PROTECTED])(mailto:
> > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > >
> > > > > > Thanks Hari, I have created FLUME-1722 for this purpose.
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/FLUME-1722
> > > > > >
> > > > > > Brock
> > > > > >
> > > > > > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > > > > > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])>
> wrote:
> > > > > > > +1.
> > > > > > >
> > > > > > > Here is what I checked:
> > > > > > > 1. Checksums and signatures look good.
> > > > > > > 2. Verified license file, readme, change log and notice file
> (more on
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > this below).
> > > > > > > 3. Built, ran unit tests, ran an agent with the sample config
> - looks
> > > > > >
> > > > > >
> > > > > >
> > > > > > good.
> > > > > > >
> > > > > > >
> > > > > > > Additional notes:
> > > > > > > The LICENSE file seems to list three libraries which we do not
> pull
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > in:
> > > > > > >
> > > > > > > commons logging
> > > > > > > http-client
> > > > > > > http-core
> > > > > > >
> > > > > > >
> > > > > > > We probably should remove these from the license file too.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Hari
> > > > > > > --
> > > > > > > Hari Shreedharan
> > > > > > >
> > > > > > >
> > > > > > > On Saturday, November 17, 2012 at 12:57 AM, Alexander
> Alten-Lorenz
> > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > - Alex
> > > > > > > >
> > > > > > > > On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED](mailto:
> [EMAIL PROTECTED])(mailto:
> > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])) (mailto:
> > > > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:

Might I humbly ask for review & commit FLUME-1719 for next RC?

Jarcec

On Sat, Nov 17, 2012 at 07:13:26PM -0800, Hari Shreedharan wrote:
> Done! Thanks Mike, Brock!
>
>
> Hari
>
> --
> Hari Shreedharan
>
>
> On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:
>
> > Ok, let's do another rc since the same lobs with different versions is probably bad.
> >
> > Also I think it's fine to commit to 1.3 without another rc since we are voting on a tag, not the branch.
> >
> > --
> > Brock Noland
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> >
> >
> > On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
> >
> > > Hari,
> > > You're correct that a -1 vote does not veto a release. A savvy user could
> > > delete one of the jars before deploying to production, but why make them do
> > > that.
> > >
> > > Thanks for the commit.
> > >
> > > Regards,
> > > Mike
> > >
> > > On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
> > > > wrote:
> > >
> > >
> > >
> > > > Mike,
> > > >
> > > > I committed your patch for flume-1.4, and trunk.
> > > >
> > > >
> > > > Brock: As I posted on the jira, if you want it committed to flume-1.3. the
> > > > RM should decide if another RC is required (looks like there are 3 PMC +1
> > > > already, unless someone withdraws the +1). If required, please cherry-pick
> > > > the patch to flume-1.3.0 and roll another RC.
> > > >
> > > >
> > > > Thanks,
> > > > Hari
> > > >
> > > > --
> > > > Hari Shreedharan
> > > >
> > > >
> > > > On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
> > > >
> > > > > When I was reviewing the libs I noticed that netty is in there twice
> > > > with 2
> > > > > different versions. I don't think we should ship like that.
> > > > >
> > > > > So, -1 from me on this RC.
> > > > >
> > > > > Details and a patch are here:
> > > > > https://issues.apache.org/jira/browse/FLUME-1723
> > > > >
> > > > > Regards,
> > > > > Mike
> > > > >
> > > > > On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > >
> > > > > > Thanks Hari, I have created FLUME-1722 for this purpose.
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/FLUME-1722
> > > > > >
> > > > > > Brock
> > > > > >
> > > > > > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > > > > > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > > > > > > +1.
> > > > > > >
> > > > > > > Here is what I checked:
> > > > > > > 1. Checksums and signatures look good.
> > > > > > > 2. Verified license file, readme, change log and notice file (more on
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > this below).
> > > > > > > 3. Built, ran unit tests, ran an agent with the sample config - looks
> > > > > >
> > > > > >
> > > > > >
> > > > > > good.
> > > > > > >
> > > > > > >
> > > > > > > Additional notes:
> > > > > > > The LICENSE file seems to list three libraries which we do not pull
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > in:
> > > > > > >
> > > > > > > commons logging
> > > > > > > http-client
> > > > > > > http-core
> > > > > > >
> > > > > > >
> > > > > > > We probably should remove these from the license file too.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Hari
> > > > > > > --
> > > > > > > Hari Shreedharan
> > > > > > >
> > > > > > >
> > > > > > > On Saturday, November 17, 2012 at 12:57 AM, Alexander Alten-Lorenz
> > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > - Alex
> > > > > > > >
> > > > > > > > On Nov 17, 2012, at 4:10 AM, Will McQueen <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])) (mailto:
> > > > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:

Done.

Regards
Mike

On Sat, Nov 17, 2012 at 7:27 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]>wrote:

> Might I humbly ask for review & commit FLUME-1719 for next RC?
>
> Jarcec
>
> On Sat, Nov 17, 2012 at 07:13:26PM -0800, Hari Shreedharan wrote:
> > Done! Thanks Mike, Brock!
> >
> >
> > Hari
> >
> > --
> > Hari Shreedharan
> >
> >
> > On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:
> >
> > > Ok, let's do another rc since the same lobs with different versions is
> probably bad.
> > >
> > > Also I think it's fine to commit to 1.3 without another rc since we
> are voting on a tag, not the branch.
> > >
> > > --
> > > Brock Noland
> > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > >
> > >
> > > On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
> > >
> > > > Hari,
> > > > You're correct that a -1 vote does not veto a release. A savvy user
> could
> > > > delete one of the jars before deploying to production, but why make
> them do
> > > > that.
> > > >
> > > > Thanks for the commit.
> > > >
> > > > Regards,
> > > > Mike
> > > >
> > > > On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <
> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
> > > > > wrote:
> > > >
> > > >
> > > >
> > > > > Mike,
> > > > >
> > > > > I committed your patch for flume-1.4, and trunk.
> > > > >
> > > > >
> > > > > Brock: As I posted on the jira, if you want it committed to
> flume-1.3. the
> > > > > RM should decide if another RC is required (looks like there are 3
> PMC +1
> > > > > already, unless someone withdraws the +1). If required, please
> cherry-pick
> > > > > the patch to flume-1.3.0 and roll another RC.
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Hari
> > > > >
> > > > > --
> > > > > Hari Shreedharan
> > > > >
> > > > >
> > > > > On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
> > > > >
> > > > > > When I was reviewing the libs I noticed that netty is in there
> twice
> > > > > with 2
> > > > > > different versions. I don't think we should ship like that.
> > > > > >
> > > > > > So, -1 from me on this RC.
> > > > > >
> > > > > > Details and a patch are here:
> > > > > > https://issues.apache.org/jira/browse/FLUME-1723
> > > > > >
> > > > > > Regards,
> > > > > > Mike
> > > > > >
> > > > > > On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <
> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > > >
> > > > > > > Thanks Hari, I have created FLUME-1722 for this purpose.
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/FLUME-1722
> > > > > > >
> > > > > > > Brock
> > > > > > >
> > > > > > > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > > > > > > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])>
> wrote:
> > > > > > > > +1.
> > > > > > > >
> > > > > > > > Here is what I checked:
> > > > > > > > 1. Checksums and signatures look good.
> > > > > > > > 2. Verified license file, readme, change log and notice file
> (more on
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > this below).
> > > > > > > > 3. Built, ran unit tests, ran an agent with the sample
> config - looks
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > good.
> > > > > > > >
> > > > > > > >
> > > > > > > > Additional notes:
> > > > > > > > The LICENSE file seems to list three libraries which we do
> not pull
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > in:
> > > > > > > >
> > > > > > > > commons logging
> > > > > > > > http-client
> > > > > > > > http-core
> > > > > > > >
> > > > > > > >
> > > > > > > > We probably should remove these from the license file too.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Hari
> > > > > > > > --
> > > > > > > > Hari Shreedharan
> > > > > > > >
> > > > > > > >
> > > > > > > > On Saturday, November 17, 2012 at 12:57 AM, Alexander
> Alten-Lorenz
> > > > > wrote:

Thank you sir,
greatly appreciated!

Jarcec

On Sat, Nov 17, 2012 at 07:39:57PM -0800, Mike Percy wrote:
> Done.
>
> Regards
> Mike
>
> On Sat, Nov 17, 2012 at 7:27 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]>wrote:
>
> > Might I humbly ask for review & commit FLUME-1719 for next RC?
> >
> > Jarcec
> >
> > On Sat, Nov 17, 2012 at 07:13:26PM -0800, Hari Shreedharan wrote:
> > > Done! Thanks Mike, Brock!
> > >
> > >
> > > Hari
> > >
> > > --
> > > Hari Shreedharan
> > >
> > >
> > > On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:
> > >
> > > > Ok, let's do another rc since the same lobs with different versions is
> > probably bad.
> > > >
> > > > Also I think it's fine to commit to 1.3 without another rc since we
> > are voting on a tag, not the branch.
> > > >
> > > > --
> > > > Brock Noland
> > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > >
> > > >
> > > > On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
> > > >
> > > > > Hari,
> > > > > You're correct that a -1 vote does not veto a release. A savvy user
> > could
> > > > > delete one of the jars before deploying to production, but why make
> > them do
> > > > > that.
> > > > >
> > > > > Thanks for the commit.
> > > > >
> > > > > Regards,
> > > > > Mike
> > > > >
> > > > > On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <
> > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
> > > > > > wrote:
> > > > >
> > > > >
> > > > >
> > > > > > Mike,
> > > > > >
> > > > > > I committed your patch for flume-1.4, and trunk.
> > > > > >
> > > > > >
> > > > > > Brock: As I posted on the jira, if you want it committed to
> > flume-1.3. the
> > > > > > RM should decide if another RC is required (looks like there are 3
> > PMC +1
> > > > > > already, unless someone withdraws the +1). If required, please
> > cherry-pick
> > > > > > the patch to flume-1.3.0 and roll another RC.
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > > Hari
> > > > > >
> > > > > > --
> > > > > > Hari Shreedharan
> > > > > >
> > > > > >
> > > > > > On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
> > > > > >
> > > > > > > When I was reviewing the libs I noticed that netty is in there
> > twice
> > > > > > with 2
> > > > > > > different versions. I don't think we should ship like that.
> > > > > > >
> > > > > > > So, -1 from me on this RC.
> > > > > > >
> > > > > > > Details and a patch are here:
> > > > > > > https://issues.apache.org/jira/browse/FLUME-1723
> > > > > > >
> > > > > > > Regards,
> > > > > > > Mike
> > > > > > >
> > > > > > > On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <
> > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
> > > > > > [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
> > > > > > >
> > > > > > > > Thanks Hari, I have created FLUME-1722 for this purpose.
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/browse/FLUME-1722
> > > > > > > >
> > > > > > > > Brock
> > > > > > > >
> > > > > > > > On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
> > > > > > > > <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])>
> > wrote:
> > > > > > > > > +1.
> > > > > > > > >
> > > > > > > > > Here is what I checked:
> > > > > > > > > 1. Checksums and signatures look good.
> > > > > > > > > 2. Verified license file, readme, change log and notice file
> > (more on
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > this below).
> > > > > > > > > 3. Built, ran unit tests, ran an agent with the sample
> > config - looks
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > good.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Additional notes:
> > > > > > > > > The LICENSE file seems to list three libraries which we do
> > not pull
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > in:
> > > > > > > > >
> > > > > > > > > commons logging
> > > > > > > > > http-client
> > > > > > > > > http-core
>

If we're doing another RC, I'd like it if we could squeeze in FLUME-1660
too as I've seen several users inquiring about closing tmp files, and I
think it provides the best solution for many of them. I believe it was  
bumped out of 1.3 due to time constraints but it looks like that
shouldn't be an issue now?

Personally, +0 on the release, haven't found the time to do a thorough
check.

On 11/19/2012 01:36 AM, Jarek Jarcec Cecho wrote:
> Thank you sir,
> greatly appreciated!
>
> Jarcec
>
> On Sat, Nov 17, 2012 at 07:39:57PM -0800, Mike Percy wrote:
>> Done.
>>
>> Regards
>> Mike
>>
>> On Sat, Nov 17, 2012 at 7:27 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]>wrote:
>>
>>> Might I humbly ask for review & commit FLUME-1719 for next RC?
>>>
>>> Jarcec
>>>
>>> On Sat, Nov 17, 2012 at 07:13:26PM -0800, Hari Shreedharan wrote:
>>>> Done! Thanks Mike, Brock!
>>>>
>>>>
>>>> Hari
>>>>
>>>> --
>>>> Hari Shreedharan
>>>>
>>>>
>>>> On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:
>>>>
>>>>> Ok, let's do another rc since the same lobs with different versions is
>>> probably bad.
>>>>> Also I think it's fine to commit to 1.3 without another rc since we
>>> are voting on a tag, not the branch.
>>>>> --
>>>>> Brock Noland
>>>>> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>>>>>
>>>>>
>>>>> On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
>>>>>
>>>>>> Hari,
>>>>>> You're correct that a -1 vote does not veto a release. A savvy user
>>> could
>>>>>> delete one of the jars before deploying to production, but why make
>>> them do
>>>>>> that.
>>>>>>
>>>>>> Thanks for the commit.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <
>>> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])
>>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Mike,
>>>>>>>
>>>>>>> I committed your patch for flume-1.4, and trunk.
>>>>>>>
>>>>>>>
>>>>>>> Brock: As I posted on the jira, if you want it committed to
>>> flume-1.3. the
>>>>>>> RM should decide if another RC is required (looks like there are 3
>>> PMC +1
>>>>>>> already, unless someone withdraws the +1). If required, please
>>> cherry-pick
>>>>>>> the patch to flume-1.3.0 and roll another RC.
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Hari
>>>>>>>
>>>>>>> --
>>>>>>> Hari Shreedharan
>>>>>>>
>>>>>>>
>>>>>>> On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
>>>>>>>
>>>>>>>> When I was reviewing the libs I noticed that netty is in there
>>> twice
>>>>>>> with 2
>>>>>>>> different versions. I don't think we should ship like that.
>>>>>>>>
>>>>>>>> So, -1 from me on this RC.
>>>>>>>>
>>>>>>>> Details and a patch are here:
>>>>>>>> https://issues.apache.org/jira/browse/FLUME-1723
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>>
>>>>>>>> On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <
>>> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(mailto:
>>>>>>> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
>>>>>>>>> Thanks Hari, I have created FLUME-1722 for this purpose.
>>>>>>>>>
>>>>>>>>> https://issues.apache.org/jira/browse/FLUME-1722
>>>>>>>>>
>>>>>>>>> Brock
>>>>>>>>>
>>>>>>>>> On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
>>>>>>>>> <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])>
>>> wrote:
>>>>>>>>>> +1.
>>>>>>>>>>
>>>>>>>>>> Here is what I checked:
>>>>>>>>>> 1. Checksums and signatures look good.
>>>>>>>>>> 2. Verified license file, readme, change log and notice file
>>> (more on
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> this below).
>>>>>>>>>> 3. Built, ran unit tests, ran an agent with the sample
>>> config - looks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> good.
>>>>>>>>>>
>>>>>>>>>> Additional notes:
>>>>>>>>>> The LICENSE file seems to list three libraries which we do
>>> not pull
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> in:
>>>>>>>>>> commons logging
>>>>>>>>>> http-client
>>>>>>>>>> http-core
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We probably should remove these from the license file too.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,

I just committed FLUME-1660 to trunk and 1.4. If Brock is cool with it then
let's bring it into 1.3.0.

Regards
Mike

On Sun, Nov 18, 2012 at 7:33 PM, Juhani Connolly <
[EMAIL PROTECTED]> wrote:

> If we're doing another RC, I'd like it if we could squeeze in FLUME-1660
> too as I've seen several users inquiring about closing tmp files, and I
> think it provides the best solution for many of them. I believe it was
>  bumped out of 1.3 due to time constraints but it looks like that shouldn't
> be an issue now?
>
> Personally, +0 on the release, haven't found the time to do a thorough
> check.
>
>
> On 11/19/2012 01:36 AM, Jarek Jarcec Cecho wrote:
>
>> Thank you sir,
>> greatly appreciated!
>>
>> Jarcec
>>
>> On Sat, Nov 17, 2012 at 07:39:57PM -0800, Mike Percy wrote:
>>
>>> Done.
>>>
>>> Regards
>>> Mike
>>>
>>> On Sat, Nov 17, 2012 at 7:27 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]
>>> >wrote:
>>>
>>>  Might I humbly ask for review & commit FLUME-1719 for next RC?
>>>>
>>>> Jarcec
>>>>
>>>> On Sat, Nov 17, 2012 at 07:13:26PM -0800, Hari Shreedharan wrote:
>>>>
>>>>> Done! Thanks Mike, Brock!
>>>>>
>>>>>
>>>>> Hari
>>>>>
>>>>> --
>>>>> Hari Shreedharan
>>>>>
>>>>>
>>>>> On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:
>>>>>
>>>>>  Ok, let's do another rc since the same lobs with different versions is
>>>>>>
>>>>> probably bad.
>>>>
>>>>> Also I think it's fine to commit to 1.3 without another rc since we
>>>>>>
>>>>> are voting on a tag, not the branch.
>>>>
>>>>> --
>>>>>> Brock Noland
>>>>>> Sent with Sparrow (http://www.sparrowmailapp.**com/?sig<http://www.sparrowmailapp.com/?sig>
>>>>>> )
>>>>>>
>>>>>>
>>>>>> On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
>>>>>>
>>>>>>  Hari,
>>>>>>> You're correct that a -1 vote does not veto a release. A savvy user
>>>>>>>
>>>>>> could
>>>>
>>>>> delete one of the jars before deploying to production, but why make
>>>>>>>
>>>>>> them do
>>>>
>>>>> that.
>>>>>>>
>>>>>>> Thanks for the commit.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>>
>>>>>>> On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <
>>>>>>>
>>>>>> [EMAIL PROTECTED] (mailto:hshreedharan@cloudera.**com<[EMAIL PROTECTED]>
>>>> )
>>>>
>>>>>  wrote:
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>  Mike,
>>>>>>>>
>>>>>>>> I committed your patch for flume-1.4, and trunk.
>>>>>>>>
>>>>>>>>
>>>>>>>> Brock: As I posted on the jira, if you want it committed to
>>>>>>>>
>>>>>>> flume-1.3. the
>>>>
>>>>>  RM should decide if another RC is required (looks like there are 3
>>>>>>>>
>>>>>>> PMC +1
>>>>
>>>>>  already, unless someone withdraws the +1). If required, please
>>>>>>>>
>>>>>>> cherry-pick
>>>>
>>>>>  the patch to flume-1.3.0 and roll another RC.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Hari
>>>>>>>>
>>>>>>>> --
>>>>>>>> Hari Shreedharan
>>>>>>>>
>>>>>>>>
>>>>>>>> On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
>>>>>>>>
>>>>>>>>  When I was reviewing the libs I noticed that netty is in there
>>>>>>>>>
>>>>>>>> twice
>>>>
>>>>>  with 2
>>>>>>>>
>>>>>>>>> different versions. I don't think we should ship like that.
>>>>>>>>>
>>>>>>>>> So, -1 from me on this RC.
>>>>>>>>>
>>>>>>>>> Details and a patch are here:
>>>>>>>>> https://issues.apache.org/**jira/browse/FLUME-1723<https://issues.apache.org/jira/browse/FLUME-1723>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Mike
>>>>>>>>>
>>>>>>>>> On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <
>>>>>>>>>
>>>>>>>> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(**mailto:
>>>>
>>>>>  [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
>>>>>>>>
>>>>>>>>> Thanks Hari, I have created FLUME-1722 for this purpose.
>>>>>>>>>>
>>>>>>>>>> https://issues.apache.org/**jira/browse/FLUME-1722<https://issues.apache.org/jira/browse/FLUME-1722>
>>>>>>>>>>
>>>>>>>>>> Brock
>>>>>>>>>>
>>>>>>>>>> On Sat, Nov 17, 2012 at 5:29 PM, Hari Shreedharan
>>>>>>>>>> <[EMAIL PROTECTED] (mailto:hshreedharan@cloudera.**com<[EMAIL PROTECTED]>
>>>>>>>>>> )>

BTW I'm +1 on pulling it into 1.3.0

On Mon, Nov 19, 2012 at 12:22 AM, Mike Percy <[EMAIL PROTECTED]> wrote:

> I just committed FLUME-1660 to trunk and 1.4. If Brock is cool with it
> then let's bring it into 1.3.0.
>
> Regards
> Mike
>
>
> On Sun, Nov 18, 2012 at 7:33 PM, Juhani Connolly <
> [EMAIL PROTECTED]> wrote:
>
>> If we're doing another RC, I'd like it if we could squeeze in FLUME-1660
>> too as I've seen several users inquiring about closing tmp files, and I
>> think it provides the best solution for many of them. I believe it was
>>  bumped out of 1.3 due to time constraints but it looks like that shouldn't
>> be an issue now?
>>
>> Personally, +0 on the release, haven't found the time to do a thorough
>> check.
>>
>>
>> On 11/19/2012 01:36 AM, Jarek Jarcec Cecho wrote:
>>
>>> Thank you sir,
>>> greatly appreciated!
>>>
>>> Jarcec
>>>
>>> On Sat, Nov 17, 2012 at 07:39:57PM -0800, Mike Percy wrote:
>>>
>>>> Done.
>>>>
>>>> Regards
>>>> Mike
>>>>
>>>> On Sat, Nov 17, 2012 at 7:27 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]
>>>> >wrote:
>>>>
>>>>  Might I humbly ask for review & commit FLUME-1719 for next RC?
>>>>>
>>>>> Jarcec
>>>>>
>>>>> On Sat, Nov 17, 2012 at 07:13:26PM -0800, Hari Shreedharan wrote:
>>>>>
>>>>>> Done! Thanks Mike, Brock!
>>>>>>
>>>>>>
>>>>>> Hari
>>>>>>
>>>>>> --
>>>>>> Hari Shreedharan
>>>>>>
>>>>>>
>>>>>> On Saturday, November 17, 2012 at 7:05 PM, Brock Noland wrote:
>>>>>>
>>>>>>  Ok, let's do another rc since the same lobs with different versions
>>>>>>> is
>>>>>>>
>>>>>> probably bad.
>>>>>
>>>>>> Also I think it's fine to commit to 1.3 without another rc since we
>>>>>>>
>>>>>> are voting on a tag, not the branch.
>>>>>
>>>>>> --
>>>>>>> Brock Noland
>>>>>>> Sent with Sparrow (http://www.sparrowmailapp.**com/?sig<http://www.sparrowmailapp.com/?sig>
>>>>>>> )
>>>>>>>
>>>>>>>
>>>>>>> On Saturday, November 17, 2012 at 8:45 PM, Mike Percy wrote:
>>>>>>>
>>>>>>>  Hari,
>>>>>>>> You're correct that a -1 vote does not veto a release. A savvy user
>>>>>>>>
>>>>>>> could
>>>>>
>>>>>> delete one of the jars before deploying to production, but why make
>>>>>>>>
>>>>>>> them do
>>>>>
>>>>>> that.
>>>>>>>>
>>>>>>>> Thanks for the commit.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>>
>>>>>>>> On Sat, Nov 17, 2012 at 6:12 PM, Hari Shreedharan <
>>>>>>>>
>>>>>>> [EMAIL PROTECTED] (mailto:hshreedharan@cloudera.**com<[EMAIL PROTECTED]>
>>>>> )
>>>>>
>>>>>>  wrote:
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>  Mike,
>>>>>>>>>
>>>>>>>>> I committed your patch for flume-1.4, and trunk.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Brock: As I posted on the jira, if you want it committed to
>>>>>>>>>
>>>>>>>> flume-1.3. the
>>>>>
>>>>>>  RM should decide if another RC is required (looks like there are 3
>>>>>>>>>
>>>>>>>> PMC +1
>>>>>
>>>>>>  already, unless someone withdraws the +1). If required, please
>>>>>>>>>
>>>>>>>> cherry-pick
>>>>>
>>>>>>  the patch to flume-1.3.0 and roll another RC.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Hari
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Hari Shreedharan
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Saturday, November 17, 2012 at 5:58 PM, Mike Percy wrote:
>>>>>>>>>
>>>>>>>>>  When I was reviewing the libs I noticed that netty is in there
>>>>>>>>>>
>>>>>>>>> twice
>>>>>
>>>>>>  with 2
>>>>>>>>>
>>>>>>>>>> different versions. I don't think we should ship like that.
>>>>>>>>>>
>>>>>>>>>> So, -1 from me on this RC.
>>>>>>>>>>
>>>>>>>>>> Details and a patch are here:
>>>>>>>>>> https://issues.apache.org/**jira/browse/FLUME-1723<https://issues.apache.org/jira/browse/FLUME-1723>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Mike
>>>>>>>>>>
>>>>>>>>>> On Sat, Nov 17, 2012 at 3:33 PM, Brock Noland <
>>>>>>>>>>
>>>>>>>>> [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])(**mailto:
>>>>>
>>>>>>  [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]))> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks Hari, I have created FLUME-1722 for this purpose.
>>>>>>>>>>>
>>>>>>>>>>> https://issues.apache.org/**jira/browse/FLUME-1722<https://issues.apache.org/jira/browse/FLUME-1722>

This is the first release for Apache Flume as a top-level project,
version 1.3.0. We are voting on release candidate rc4.

*** Please cast your vote within the next 72 hours ***

The list of fixed issues:
http://s.apache.org/Q3i

The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
for the source and binary artifacts can be found at:
http://people.apache.org/~brock/flume-1.3.0-rc4/

Nexus Staging Repository:
https://repository.apache.org/content/repositories/orgapacheflume-047/

The tag to be voted on:
http://s.apache.org/80Y

The KEYS file can be found here:
https://svn.apache.org/repos/asf/flume/dist/KEYS

+1 verified hashes, sigs, and ran tests

On Mon, Nov 19, 2012 at 12:49 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> This is the first release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc4.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/Q3i
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc4/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-047/
>
> The tag to be voted on:
> http://s.apache.org/80Y
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Note the statement "This is the first release for Apache Flume as a
top-level project," is obviously note correct. I'll update the release
mail template to make it more obvious this requires changing.

On Mon, Nov 19, 2012 at 12:50 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> +1 verified hashes, sigs, and ran tests
>
> On Mon, Nov 19, 2012 at 12:49 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>> This is the first release for Apache Flume as a top-level project,
>> version 1.3.0. We are voting on release candidate rc4.
>>
>> *** Please cast your vote within the next 72 hours ***
>>
>> The list of fixed issues:
>> http://s.apache.org/Q3i
>>
>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> for the source and binary artifacts can be found at:
>> http://people.apache.org/~brock/flume-1.3.0-rc4/
>>
>> Nexus Staging Repository:
>> https://repository.apache.org/content/repositories/orgapacheflume-047/
>>
>> The tag to be voted on:
>> http://s.apache.org/80Y
>>
>> The KEYS file can be found here:
>> https://svn.apache.org/repos/asf/flume/dist/KEYS
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Test failure ...

 *<testcase time="4.546"
classname="org.apache.flume.sink.hdfs.TestHDFSEventSink"
name="testCloseOnIdle">*
    <failure type="java.lang.AssertionError">java.lang.AssertionError
        at org.junit.Assert.fail(Assert.java:92)
        at org.junit.Assert.assertTrue(Assert.java:43)
        at org.junit.Assert.assertTrue(Assert.java:54)
        at
org.apache.flume.sink.hdfs.TestHDFSEventSink.testCloseOnIdle(TestHDFSEventSink.java:1036)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)

Also see the below errors in  *test-output.txt files

*1) in
surefire-reports/org.apache.flume.sink.hdfs.TestHDFSEventSink-output.txt*

2012-11-19 11:31:25,926 (main) [ERROR -
org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
Failed to register monitored counter group for type: SINK, name: null
javax.management.InstanceAlreadyExistsException:
org.apache.flume.sink:type=null
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
...
2012-11-19 11:31:25,951 (main) [ERROR -
org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
Failed to register monitored counter group for type: SINK, name: null
javax.management.InstanceAlreadyExistsException:
org.apache.flume.sink:type=null
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
...

*3)
in surefire-reports/org.apache.flume.sink.hdfs.TestHDFSEventSinkOnMiniCluster-output.txt
*

2012-11-19 11:31:53,213 (main) [ERROR -
org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
Failed to register monitored counter group for type: CHANNEL, name:
simpleHDFSTest-mem-chan
javax.management.InstanceAlreadyExistsException:
org.apache.flume.channel:type=simpleHDFSTest-mem-chan
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
        at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
        at
org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:87)
        at
org.apache.flume.instrumentation.MonitoredCounterGroup.start(MonitoredCounterGroup.java:67)
        at
org.apache.flume.channel.MemoryChannel.start(MemoryChannel.java:327)
        at
org.apache.flume.sink.hdfs.TestHDFSEventSinkOnMiniCluster.simpleHDFSGZipCompressedTest(TestHDFSEventSinkOnMiniCluster.java:178)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
...

[ERROR -
org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
Failed to register monitored counter group for type: SINK, name:
simpleHDFSTest-hdfs-sink
javax.management.InstanceAlreadyExistsException:
org.apache.flume.sink:type=simpleHDFSTest-hdfs-sink
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(Defaul

Hi,

Did you run "testCloseOnIdle" test multiple times or just once? I ran
it 15 times and it failed once.  To me it looks like a racy test so I
don't think this is a risk to the release but it'd be great if either
Juhani or Mike could confirm that.

Regarding the MBean errors, those are errors which show up during
normal unit tests because mbeans are being registered multiple times.
While I'd like to get rid of the errors (file channel tests add UUID
to component name for this purpose) it's not urgent.

Brock

On Mon, Nov 19, 2012 at 1:55 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
> Test failure ...
>
>  *<testcase time="4.546"
> classname="org.apache.flume.sink.hdfs.TestHDFSEventSink"
> name="testCloseOnIdle">*
>     <failure type="java.lang.AssertionError">java.lang.AssertionError
>         at org.junit.Assert.fail(Assert.java:92)
>         at org.junit.Assert.assertTrue(Assert.java:43)
>         at org.junit.Assert.assertTrue(Assert.java:54)
>         at
> org.apache.flume.sink.hdfs.TestHDFSEventSink.testCloseOnIdle(TestHDFSEventSink.java:1036)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>
>
>
> Also see the below errors in  *test-output.txt files
>
> *1) in
> surefire-reports/org.apache.flume.sink.hdfs.TestHDFSEventSink-output.txt*
>
> 2012-11-19 11:31:25,926 (main) [ERROR -
> org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
> Failed to register monitored counter group for type: SINK, name: null
> javax.management.InstanceAlreadyExistsException:
> org.apache.flume.sink:type=null
>         at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
> ...
>
>
> 2012-11-19 11:31:25,951 (main) [ERROR -
> org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
> Failed to register monitored counter group for type: SINK, name: null
> javax.management.InstanceAlreadyExistsException:
> org.apache.flume.sink:type=null
>         at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
> ...
>
> *3)
> in surefire-reports/org.apache.flume.sink.hdfs.TestHDFSEventSinkOnMiniCluster-output.txt
> *
>
> 2012-11-19 11:31:53,213 (main) [ERROR -
> org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
> Failed to register monitored counter group for type: CHANNEL, name:
> simpleHDFSTest-mem-chan
> javax.management.InstanceAlreadyExistsException:
> org.apache.flume.channel:type=simpleHDFSTest-mem-chan
>         at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
>         at
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)

Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

I have created https://issues.apache.org/jira/browse/FLUME-1730 for
the racy test issue.

On Mon, Nov 19, 2012 at 2:06 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Did you run "testCloseOnIdle" test multiple times or just once? I ran
> it 15 times and it failed once.  To me it looks like a racy test so I
> don't think this is a risk to the release but it'd be great if either
> Juhani or Mike could confirm that.
>
> Regarding the MBean errors, those are errors which show up during
> normal unit tests because mbeans are being registered multiple times.
> While I'd like to get rid of the errors (file channel tests add UUID
> to component name for this purpose) it's not urgent.
>
> Brock
>
> On Mon, Nov 19, 2012 at 1:55 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
>> Test failure ...
>>
>>  *<testcase time="4.546"
>> classname="org.apache.flume.sink.hdfs.TestHDFSEventSink"
>> name="testCloseOnIdle">*
>>     <failure type="java.lang.AssertionError">java.lang.AssertionError
>>         at org.junit.Assert.fail(Assert.java:92)
>>         at org.junit.Assert.assertTrue(Assert.java:43)
>>         at org.junit.Assert.assertTrue(Assert.java:54)
>>         at
>> org.apache.flume.sink.hdfs.TestHDFSEventSink.testCloseOnIdle(TestHDFSEventSink.java:1036)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>         at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>         at java.lang.reflect.Method.invoke(Method.java:597)
>>         at
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>>
>>
>>
>> Also see the below errors in  *test-output.txt files
>>
>> *1) in
>> surefire-reports/org.apache.flume.sink.hdfs.TestHDFSEventSink-output.txt*
>>
>> 2012-11-19 11:31:25,926 (main) [ERROR -
>> org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
>> Failed to register monitored counter group for type: SINK, name: null
>> javax.management.InstanceAlreadyExistsException:
>> org.apache.flume.sink:type=null
>>         at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
>>         at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
>>         at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
>> ...
>>
>>
>> 2012-11-19 11:31:25,951 (main) [ERROR -
>> org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
>> Failed to register monitored counter group for type: SINK, name: null
>> javax.management.InstanceAlreadyExistsException:
>> org.apache.flume.sink:type=null
>>         at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
>>         at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
>>         at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
>> ...
>>
>> *3)
>> in surefire-reports/org.apache.flume.sink.hdfs.TestHDFSEventSinkOnMiniCluster-output.txt
>> *
>>
>> 2012-11-19 11:31:53,213 (main) [ERROR -
>> org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:92)]
>> Failed to register monitored counter group for type: CHANNEL, name:
>> simpleHDFSTest-mem-chan
>> javax.management.InstanceAlreadyExistsException:
>> org.apache.flume.channel:type=simpleHDFSTest-mem-chan
>>         at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
>>         at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
>>         at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
>>         at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)

Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Just once. Following steps..

- git pull --rebase
- mvn clean package

Running it again right now. will keep you posted.

-roshan

passed on second attempt. definitely a fuzzy test.
-roshan
On Mon, Nov 19, 2012 at 12:34 PM, Roshan Naik <[EMAIL PROTECTED]>wrote:

> Just once. Following steps..
>
> - git pull --rebase
> - mvn clean package
>
> Running it again right now. will keep you posted.
>
> -roshan
>
>
>

OK, good to hear. I don't feel this racy test requires another RC,
e.g. the flume-1.2.0 file channel tests are quite racy, but if we have
another RC, I'll make sure we get that 1730 is included.

On Mon, Nov 19, 2012 at 2:48 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
> passed on second attempt. definitely a fuzzy test.
> -roshan
>
>
> On Mon, Nov 19, 2012 at 12:34 PM, Roshan Naik <[EMAIL PROTECTED]>wrote:
>
>> Just once. Following steps..
>>
>> - git pull --rebase
>> - mvn clean package
>>
>> Running it again right now. will keep you posted.
>>
>> -roshan
>>
>>
>>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

+1 (non binding)  for the rc4

-roshan

+1

I tested the Maven artifacts with Log4j 2 and had no problems.

I tried to use the tag link below but have absolutely no idea what to do with it.  I ended up doing a git clone and then a git checkout release-1.3.0.  That failed once with an out of permgen space error (normal behavior). I then commented out the sphinx plugin and got the same unit test failure as Roshan. I ran it a third time and it passed.

The source distribution looks fine.  I still find it confusing and redundant that the binary distribution also contains source.

Ralph

On Nov 19, 2012, at 11:49 AM, Brock Noland wrote:

> This is the first release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc4.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/Q3i
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc4/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-047/
>
> The tag to be voted on:
> http://s.apache.org/80Y
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS

Hi Brock.

I didn't have any problems  with that  test, but it's setup to be very
tight(1ms) to encounter a possible bug that I initially encountered. It
took me 20 runs now to get the issue to recreate. It's somewhat
sensitive to HDFS, looking at the output logs from the time it did fail
however, it looks like HDFS was just lagging behind a bit. It definitely
isn't a problem that should hold back the release, but it looks like
it's going to be awkward to get a test that properly tests the sink
without a lot of sleeps and longer idle timeouts... And running unit
tests take long enough as is. Still, if I can't come up with another
alternative I'll make a patch along those lines.

On 11/20/2012 05:52 AM, Brock Noland wrote:
> OK, good to hear. I don't feel this racy test requires another RC,
> e.g. the flume-1.2.0 file channel tests are quite racy, but if we have
> another RC, I'll make sure we get that 1730 is included.
>
> On Mon, Nov 19, 2012 at 2:48 PM, Roshan Naik <[EMAIL PROTECTED]> wrote:
>> passed on second attempt. definitely a fuzzy test.
>> -roshan
>>
>>
>> On Mon, Nov 19, 2012 at 12:34 PM, Roshan Naik <[EMAIL PROTECTED]>wrote:
>>
>>> Just once. Following steps..
>>>
>>> - git pull --rebase
>>> - mvn clean package
>>>
>>> Running it again right now. will keep you posted.
>>>
>>> -roshan
>>>
>>>
>>>
>
>

Hi,

Thanks Juhani, I agree, this shouldn't hold up the release and FWIW, I
don't have an alternative way to test this at present...

Brock

On Mon, Nov 19, 2012 at 7:40 PM, Juhani Connolly
<[EMAIL PROTECTED]> wrote:
> Hi Brock.
>
> I didn't have any problems  with that  test, but it's setup to be very
> tight(1ms) to encounter a possible bug that I initially encountered. It took
> me 20 runs now to get the issue to recreate. It's somewhat sensitive to
> HDFS, looking at the output logs from the time it did fail however, it looks
> like HDFS was just lagging behind a bit. It definitely isn't a problem that
> should hold back the release, but it looks like it's going to be awkward to
> get a test that properly tests the sink without a lot of sleeps and longer
> idle timeouts... And running unit tests take long enough as is. Still, if I
> can't come up with another alternative I'll make a patch along those lines.
>
>
> On 11/20/2012 05:52 AM, Brock Noland wrote:
>>
>> OK, good to hear. I don't feel this racy test requires another RC,
>> e.g. the flume-1.2.0 file channel tests are quite racy, but if we have
>> another RC, I'll make sure we get that 1730 is included.
>>
>> On Mon, Nov 19, 2012 at 2:48 PM, Roshan Naik <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> passed on second attempt. definitely a fuzzy test.
>>> -roshan
>>>
>>>
>>> On Mon, Nov 19, 2012 at 12:34 PM, Roshan Naik
>>> <[EMAIL PROTECTED]>wrote:
>>>
>>>> Just once. Following steps..
>>>>
>>>> - git pull --rebase
>>>> - mvn clean package
>>>>
>>>> Running it again right now. will keep you posted.
>>>>
>>>> -roshan
>>>>
>>>>
>>>>
>>
>>
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

+1

* Checksums fine
* Signatures fine
* All shipped JARs seems to have appropriate entry in LICENSE file
* Tests seems to be passing
* Files CHANGELOG, LICENSE, NOTICE, README, RELEASE-NOTES seems fine

Jarcec

On Mon, Nov 19, 2012 at 12:49:57PM -0600, Brock Noland wrote:
> This is the first release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc4.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/Q3i
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc4/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-047/
>
> The tag to be voted on:
> http://s.apache.org/80Y
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS

Hi,

It seems like FLUME-1732 is actually a blocker. Delete your .m2/repository directory and run a full build. It fails the first time (though it may work subsequently). This seems to be caused by a maven bug - I am not entirely sure how we can fix it. Seems like adding netty as a dependency wherever sdk is pulled in works - I know it is lame, but I don't think we should release something that fails to build the first time around.  Can we add that to the pom.xml files and then respin an RC? Sorry about the number of RCs here, but I really do think this one is a blocker.
Thanks,
Hari

--
Hari Shreedharan
On Tuesday, November 20, 2012 at 8:22 AM, Jarek Jarcec Cecho wrote:

> +1
>
> * Checksums fine
> * Signatures fine
> * All shipped JARs seems to have appropriate entry in LICENSE file
> * Tests seems to be passing
> * Files CHANGELOG, LICENSE, NOTICE, README, RELEASE-NOTES seems fine
>
> Jarcec
>
> On Mon, Nov 19, 2012 at 12:49:57PM -0600, Brock Noland wrote:
> > This is the first release for Apache Flume as a top-level project,
> > version 1.3.0. We are voting on release candidate rc4.
> >
> > *** Please cast your vote within the next 72 hours ***
> >
> > The list of fixed issues:
> > http://s.apache.org/Q3i
> >
> > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > for the source and binary artifacts can be found at:
> > http://people.apache.org/~brock/flume-1.3.0-rc4/
> >
> > Nexus Staging Repository:
> > https://repository.apache.org/content/repositories/orgapacheflume-047/
> >
> > The tag to be voted on:
> > http://s.apache.org/80Y
> >
> > The KEYS file can be found here:
> > https://svn.apache.org/repos/asf/flume/dist/KEYS
> >
>
>
>

Can you send the exact steps to reproduce? Deleting my m2 repo didn't reproduce the error.  

--
Brock Noland
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, November 20, 2012 at 6:38 PM, Hari Shreedharan wrote:

> Hi,
>
> It seems like FLUME-1732 is actually a blocker. Delete your .m2/repository directory and run a full build. It fails the first time (though it may work subsequently). This seems to be caused by a maven bug - I am not entirely sure how we can fix it. Seems like adding netty as a dependency wherever sdk is pulled in works - I know it is lame, but I don't think we should release something that fails to build the first time around. Can we add that to the pom.xml files and then respin an RC? Sorry about the number of RCs here, but I really do think this one is a blocker.
>
>
> Thanks,
> Hari
>
> --
> Hari Shreedharan
>
>
> On Tuesday, November 20, 2012 at 8:22 AM, Jarek Jarcec Cecho wrote:
>
> > +1
> >
> > * Checksums fine
> > * Signatures fine
> > * All shipped JARs seems to have appropriate entry in LICENSE file
> > * Tests seems to be passing
> > * Files CHANGELOG, LICENSE, NOTICE, README, RELEASE-NOTES seems fine
> >
> > Jarcec
> >
> > On Mon, Nov 19, 2012 at 12:49:57PM -0600, Brock Noland wrote:
> > > This is the first release for Apache Flume as a top-level project,
> > > version 1.3.0. We are voting on release candidate rc4.
> > >
> > > *** Please cast your vote within the next 72 hours ***
> > >
> > > The list of fixed issues:
> > > http://s.apache.org/Q3i
> > >
> > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > > for the source and binary artifacts can be found at:
> > > http://people.apache.org/~brock/flume-1.3.0-rc4/
> > >
> > > Nexus Staging Repository:
> > > https://repository.apache.org/content/repositories/orgapacheflume-047/
> > >
> > > The tag to be voted on:
> > > http://s.apache.org/80Y
> > >
> > > The KEYS file can be found here:
> > > https://svn.apache.org/repos/asf/flume/dist/KEYS
> > >
> >
> >
>
>
>

Brock,

Seems like this is affecting only trunk, I am able to build the flume-1.3.0 branch. The reason seems to be that it is because the final built artifacts from that branch are not SNAPSHOTs and therefore are immutable. Unless someone changes the pom to adjust dependencies on an artifact that already exists in one of the repos, this problem does not seem to happen.

At this point, since the release branch would not have this issue, we are probably ok to release, but we need to fix it asap in our trunk and 1.4 branch. I will verify the rest of the release and vote.
Thanks
Hari

--
Hari Shreedharan
On Tuesday, November 20, 2012 at 4:50 PM, Brock Noland wrote:

> Can you send the exact steps to reproduce? Deleting my m2 repo didn't reproduce the error.
>
> --
> Brock Noland
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>
>
> On Tuesday, November 20, 2012 at 6:38 PM, Hari Shreedharan wrote:
>
> > Hi,
> >
> > It seems like FLUME-1732 is actually a blocker. Delete your .m2/repository directory and run a full build. It fails the first time (though it may work subsequently). This seems to be caused by a maven bug - I am not entirely sure how we can fix it. Seems like adding netty as a dependency wherever sdk is pulled in works - I know it is lame, but I don't think we should release something that fails to build the first time around. Can we add that to the pom.xml files and then respin an RC? Sorry about the number of RCs here, but I really do think this one is a blocker.
> >
> >
> > Thanks,
> > Hari
> >
> > --
> > Hari Shreedharan
> >
> >
> > On Tuesday, November 20, 2012 at 8:22 AM, Jarek Jarcec Cecho wrote:
> >
> > > +1
> > >
> > > * Checksums fine
> > > * Signatures fine
> > > * All shipped JARs seems to have appropriate entry in LICENSE file
> > > * Tests seems to be passing
> > > * Files CHANGELOG, LICENSE, NOTICE, README, RELEASE-NOTES seems fine
> > >
> > > Jarcec
> > >
> > > On Mon, Nov 19, 2012 at 12:49:57PM -0600, Brock Noland wrote:
> > > > This is the first release for Apache Flume as a top-level project,
> > > > version 1.3.0. We are voting on release candidate rc4.
> > > >
> > > > *** Please cast your vote within the next 72 hours ***
> > > >
> > > > The list of fixed issues:
> > > > http://s.apache.org/Q3i
> > > >
> > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > > > for the source and binary artifacts can be found at:
> > > > http://people.apache.org/~brock/flume-1.3.0-rc4/
> > > >
> > > > Nexus Staging Repository:
> > > > https://repository.apache.org/content/repositories/orgapacheflume-047/
> > > >
> > > > The tag to be voted on:
> > > > http://s.apache.org/80Y
> > > >
> > > > The KEYS file can be found here:
> > > > https://svn.apache.org/repos/asf/flume/dist/KEYS
> > > >
> > >
> > >
> >
> >
>
>
>

+1 on rc4

 - Verified hashes and signatures
 - Source build (even with empty .m2 repository) works, unit tests pass
 - Contents of README, RELEASE-NOTES, NOTICE, LICENSE, and CHANGELOG look
good
 - Verified that running example config with binary artifact works, same
with output from source build

Thanks for all your hard work on this release, Brock!

Regards,
Mike

On Mon, Nov 19, 2012 at 10:49 AM, Brock Noland <[EMAIL PROTECTED]> wrote:

> This is the first release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc4.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/Q3i
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc4/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-047/
>
> The tag to be voted on:
> http://s.apache.org/80Y
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS
>

Alright, good to hear!

On Tue, Nov 20, 2012 at 7:17 PM, Hari Shreedharan
<[EMAIL PROTECTED]> wrote:
> Brock,
>
> Seems like this is affecting only trunk, I am able to build the flume-1.3.0 branch. The reason seems to be that it is because the final built artifacts from that branch are not SNAPSHOTs and therefore are immutable. Unless someone changes the pom to adjust dependencies on an artifact that already exists in one of the repos, this problem does not seem to happen.
>
> At this point, since the release branch would not have this issue, we are probably ok to release, but we need to fix it asap in our trunk and 1.4 branch. I will verify the rest of the release and vote.
>
>
> Thanks
> Hari
>
> --
> Hari Shreedharan
>
>
> On Tuesday, November 20, 2012 at 4:50 PM, Brock Noland wrote:
>
>> Can you send the exact steps to reproduce? Deleting my m2 repo didn't reproduce the error.
>>
>> --
>> Brock Noland
>> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>>
>>
>> On Tuesday, November 20, 2012 at 6:38 PM, Hari Shreedharan wrote:
>>
>> > Hi,
>> >
>> > It seems like FLUME-1732 is actually a blocker. Delete your .m2/repository directory and run a full build. It fails the first time (though it may work subsequently). This seems to be caused by a maven bug - I am not entirely sure how we can fix it. Seems like adding netty as a dependency wherever sdk is pulled in works - I know it is lame, but I don't think we should release something that fails to build the first time around. Can we add that to the pom.xml files and then respin an RC? Sorry about the number of RCs here, but I really do think this one is a blocker.
>> >
>> >
>> > Thanks,
>> > Hari
>> >
>> > --
>> > Hari Shreedharan
>> >
>> >
>> > On Tuesday, November 20, 2012 at 8:22 AM, Jarek Jarcec Cecho wrote:
>> >
>> > > +1
>> > >
>> > > * Checksums fine
>> > > * Signatures fine
>> > > * All shipped JARs seems to have appropriate entry in LICENSE file
>> > > * Tests seems to be passing
>> > > * Files CHANGELOG, LICENSE, NOTICE, README, RELEASE-NOTES seems fine
>> > >
>> > > Jarcec
>> > >
>> > > On Mon, Nov 19, 2012 at 12:49:57PM -0600, Brock Noland wrote:
>> > > > This is the first release for Apache Flume as a top-level project,
>> > > > version 1.3.0. We are voting on release candidate rc4.
>> > > >
>> > > > *** Please cast your vote within the next 72 hours ***
>> > > >
>> > > > The list of fixed issues:
>> > > > http://s.apache.org/Q3i
>> > > >
>> > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> > > > for the source and binary artifacts can be found at:
>> > > > http://people.apache.org/~brock/flume-1.3.0-rc4/
>> > > >
>> > > > Nexus Staging Repository:
>> > > > https://repository.apache.org/content/repositories/orgapacheflume-047/
>> > > >
>> > > > The tag to be voted on:
>> > > > http://s.apache.org/80Y
>> > > >
>> > > > The KEYS file can be found here:
>> > > > https://svn.apache.org/repos/asf/flume/dist/KEYS
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>
>>
>
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

+1. Looks like this is the one!

* Verified checksums and signatures.
* Deleted .m2 and built from scratch.
* Verified LICENSE, CHANGELOG, DEVNOTES, NOTICE, README and RELEASE-NOTES.
* Ran an agent with the sample configuration file.
Thanks,
Hari
--
Hari Shreedharan
On Tuesday, November 20, 2012 at 7:43 PM, Brock Noland wrote:

> Alright, good to hear!
>
> On Tue, Nov 20, 2012 at 7:17 PM, Hari Shreedharan
> <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > Brock,
> >
> > Seems like this is affecting only trunk, I am able to build the flume-1.3.0 branch. The reason seems to be that it is because the final built artifacts from that branch are not SNAPSHOTs and therefore are immutable. Unless someone changes the pom to adjust dependencies on an artifact that already exists in one of the repos, this problem does not seem to happen.
> >
> > At this point, since the release branch would not have this issue, we are probably ok to release, but we need to fix it asap in our trunk and 1.4 branch. I will verify the rest of the release and vote.
> >
> >
> > Thanks
> > Hari
> >
> > --
> > Hari Shreedharan
> >
> >
> > On Tuesday, November 20, 2012 at 4:50 PM, Brock Noland wrote:
> >
> > > Can you send the exact steps to reproduce? Deleting my m2 repo didn't reproduce the error.
> > >
> > > --
> > > Brock Noland
> > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > >
> > >
> > > On Tuesday, November 20, 2012 at 6:38 PM, Hari Shreedharan wrote:
> > >
> > > > Hi,
> > > >
> > > > It seems like FLUME-1732 is actually a blocker. Delete your .m2/repository directory and run a full build. It fails the first time (though it may work subsequently). This seems to be caused by a maven bug - I am not entirely sure how we can fix it. Seems like adding netty as a dependency wherever sdk is pulled in works - I know it is lame, but I don't think we should release something that fails to build the first time around. Can we add that to the pom.xml files and then respin an RC? Sorry about the number of RCs here, but I really do think this one is a blocker.
> > > >
> > > >
> > > > Thanks,
> > > > Hari
> > > >
> > > > --
> > > > Hari Shreedharan
> > > >
> > > >
> > > > On Tuesday, November 20, 2012 at 8:22 AM, Jarek Jarcec Cecho wrote:
> > > >
> > > > > +1
> > > > >
> > > > > * Checksums fine
> > > > > * Signatures fine
> > > > > * All shipped JARs seems to have appropriate entry in LICENSE file
> > > > > * Tests seems to be passing
> > > > > * Files CHANGELOG, LICENSE, NOTICE, README, RELEASE-NOTES seems fine
> > > > >
> > > > > Jarcec
> > > > >
> > > > > On Mon, Nov 19, 2012 at 12:49:57PM -0600, Brock Noland wrote:
> > > > > > This is the first release for Apache Flume as a top-level project,
> > > > > > version 1.3.0. We are voting on release candidate rc4.
> > > > > >
> > > > > > *** Please cast your vote within the next 72 hours ***
> > > > > >
> > > > > > The list of fixed issues:
> > > > > > http://s.apache.org/Q3i
> > > > > >
> > > > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > > > > > for the source and binary artifacts can be found at:
> > > > > > http://people.apache.org/~brock/flume-1.3.0-rc4/
> > > > > >
> > > > > > Nexus Staging Repository:
> > > > > > https://repository.apache.org/content/repositories/orgapacheflume-047/
> > > > > >
> > > > > > The tag to be voted on:
> > > > > > http://s.apache.org/80Y
> > > > > >
> > > > > > The KEYS file can be found here:
> > > > > > https://svn.apache.org/repos/asf/flume/dist/KEYS
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>
>
>

+1 on 1.3.0-rc4

I did only the build test, works and unit tests passed too

- Alex

On Nov 21, 2012, at 3:23 AM, Mike Percy <[EMAIL PROTECTED]> wrote:

> +1 on rc4
>
> - Verified hashes and signatures
> - Source build (even with empty .m2 repository) works, unit tests pass
> - Contents of README, RELEASE-NOTES, NOTICE, LICENSE, and CHANGELOG look
> good
> - Verified that running example config with binary artifact works, same
> with output from source build
>
> Thanks for all your hard work on this release, Brock!
>
> Regards,
> Mike
>
> On Mon, Nov 19, 2012 at 10:49 AM, Brock Noland <[EMAIL PROTECTED]> wrote:
>
>> This is the first release for Apache Flume as a top-level project,
>> version 1.3.0. We are voting on release candidate rc4.
>>
>> *** Please cast your vote within the next 72 hours ***
>>
>> The list of fixed issues:
>> http://s.apache.org/Q3i
>>
>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> for the source and binary artifacts can be found at:
>> http://people.apache.org/~brock/flume-1.3.0-rc4/
>>
>> Nexus Staging Repository:
>> https://repository.apache.org/content/repositories/orgapacheflume-047/
>>
>> The tag to be voted on:
>> http://s.apache.org/80Y
>>
>> The KEYS file can be found here:
>> https://svn.apache.org/repos/asf/flume/dist/KEYS
>>

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

Hi all,

Looks like the LICENSE file lists jsr-305 as ASL2 licensed, but the JSR site lists it as BSD licensed: http://code.google.com/p/jsr-305/source/browse/trunk/ri/LICENSE
Even though it is compatible with our own licensing which is ASL2, shouldn't we list the correct license in the LICENSE file, or does this line - "The compiled Apache Flume distribution includes the following sources/binaries.
The use of these sources/binaries is subject to the terms and conditions of their respective licenses." take care of it? If it does not, do we need to fix it before we release?
Thanks
Hari

--
Hari Shreedharan
On Tuesday, November 20, 2012 at 11:07 PM, Alexander Alten-Lorenz wrote:

> +1 on 1.3.0-rc4
>
> I did only the build test, works and unit tests passed too
>
> - Alex
>
> On Nov 21, 2012, at 3:23 AM, Mike Percy <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>
> > +1 on rc4
> >
> > - Verified hashes and signatures
> > - Source build (even with empty .m2 repository) works, unit tests pass
> > - Contents of README, RELEASE-NOTES, NOTICE, LICENSE, and CHANGELOG look
> > good
> > - Verified that running example config with binary artifact works, same
> > with output from source build
> >
> > Thanks for all your hard work on this release, Brock!
> >
> > Regards,
> > Mike
> >
> > On Mon, Nov 19, 2012 at 10:49 AM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> >
> > > This is the first release for Apache Flume as a top-level project,
> > > version 1.3.0. We are voting on release candidate rc4.
> > >
> > > *** Please cast your vote within the next 72 hours ***
> > >
> > > The list of fixed issues:
> > > http://s.apache.org/Q3i
> > >
> > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > > for the source and binary artifacts can be found at:
> > > http://people.apache.org/~brock/flume-1.3.0-rc4/
> > >
> > > Nexus Staging Repository:
> > > https://repository.apache.org/content/repositories/orgapacheflume-047/
> > >
> > > The tag to be voted on:
> > > http://s.apache.org/80Y
> > >
> > > The KEYS file can be found here:
> > > https://svn.apache.org/repos/asf/flume/dist/KEYS
> > >
> >
> >
>
>
> --
> Alexander Alten-Lorenz
> http://mapredit.blogspot.com
> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>
>

According to http://opensource.org/licenses/BSD-2-Clause it should be enough to use "The compiled Apache Flume distribution includes the following sources/binaries."

- Alex

On Nov 21, 2012, at 8:25 AM, Hari Shreedharan <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> Looks like the LICENSE file lists jsr-305 as ASL2 licensed, but the JSR site lists it as BSD licensed: http://code.google.com/p/jsr-305/source/browse/trunk/ri/LICENSE
> Even though it is compatible with our own licensing which is ASL2, shouldn't we list the correct license in the LICENSE file, or does this line - "The compiled Apache Flume distribution includes the following sources/binaries.
> The use of these sources/binaries is subject to the terms and conditions of their respective licenses." take care of it? If it does not, do we need to fix it before we release?
>
>
> Thanks
> Hari
>
> --
> Hari Shreedharan
>
>
> On Tuesday, November 20, 2012 at 11:07 PM, Alexander Alten-Lorenz wrote:
>
>> +1 on 1.3.0-rc4
>>
>> I did only the build test, works and unit tests passed too
>>
>> - Alex
>>
>> On Nov 21, 2012, at 3:23 AM, Mike Percy <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>>
>>> +1 on rc4
>>>
>>> - Verified hashes and signatures
>>> - Source build (even with empty .m2 repository) works, unit tests pass
>>> - Contents of README, RELEASE-NOTES, NOTICE, LICENSE, and CHANGELOG look
>>> good
>>> - Verified that running example config with binary artifact works, same
>>> with output from source build
>>>
>>> Thanks for all your hard work on this release, Brock!
>>>
>>> Regards,
>>> Mike
>>>
>>> On Mon, Nov 19, 2012 at 10:49 AM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>>>
>>>> This is the first release for Apache Flume as a top-level project,
>>>> version 1.3.0. We are voting on release candidate rc4.
>>>>
>>>> *** Please cast your vote within the next 72 hours ***
>>>>
>>>> The list of fixed issues:
>>>> http://s.apache.org/Q3i
>>>>
>>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>>> for the source and binary artifacts can be found at:
>>>> http://people.apache.org/~brock/flume-1.3.0-rc4/
>>>>
>>>> Nexus Staging Repository:
>>>> https://repository.apache.org/content/repositories/orgapacheflume-047/
>>>>
>>>> The tag to be voted on:
>>>> http://s.apache.org/80Y
>>>>
>>>> The KEYS file can be found here:
>>>> https://svn.apache.org/repos/asf/flume/dist/KEYS
>>>>
>>>
>>>
>>
>>
>> --
>> Alexander Alten-Lorenz
>> http://mapredit.blogspot.com
>> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>>
>>
>
>

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

The third party licensing stuff is not required (still proposed)
http://www.apache.org/legal/3party.html but I don't think we following
the spirit of the BSD license by listing it incorrectly, specifically
this statement "Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with
the distribution."

I checked and the jar does not contain a license file. Sorry about
this guys, I'll spin RC5 this morning.

Brock

On Wed, Nov 21, 2012 at 1:42 AM, Alexander Alten-Lorenz
<[EMAIL PROTECTED]> wrote:
> According to http://opensource.org/licenses/BSD-2-Clause it should be enough to use "The compiled Apache Flume distribution includes the following sources/binaries."
>
> - Alex
>
> On Nov 21, 2012, at 8:25 AM, Hari Shreedharan <[EMAIL PROTECTED]> wrote:
>
>> Hi all,
>>
>> Looks like the LICENSE file lists jsr-305 as ASL2 licensed, but the JSR site lists it as BSD licensed: http://code.google.com/p/jsr-305/source/browse/trunk/ri/LICENSE
>> Even though it is compatible with our own licensing which is ASL2, shouldn't we list the correct license in the LICENSE file, or does this line - "The compiled Apache Flume distribution includes the following sources/binaries.
>> The use of these sources/binaries is subject to the terms and conditions of their respective licenses." take care of it? If it does not, do we need to fix it before we release?
>>
>>
>> Thanks
>> Hari
>>
>> --
>> Hari Shreedharan
>>
>>
>> On Tuesday, November 20, 2012 at 11:07 PM, Alexander Alten-Lorenz wrote:
>>
>>> +1 on 1.3.0-rc4
>>>
>>> I did only the build test, works and unit tests passed too
>>>
>>> - Alex
>>>
>>> On Nov 21, 2012, at 3:23 AM, Mike Percy <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>>>
>>>> +1 on rc4
>>>>
>>>> - Verified hashes and signatures
>>>> - Source build (even with empty .m2 repository) works, unit tests pass
>>>> - Contents of README, RELEASE-NOTES, NOTICE, LICENSE, and CHANGELOG look
>>>> good
>>>> - Verified that running example config with binary artifact works, same
>>>> with output from source build
>>>>
>>>> Thanks for all your hard work on this release, Brock!
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> On Mon, Nov 19, 2012 at 10:49 AM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>>>>
>>>>> This is the first release for Apache Flume as a top-level project,
>>>>> version 1.3.0. We are voting on release candidate rc4.
>>>>>
>>>>> *** Please cast your vote within the next 72 hours ***
>>>>>
>>>>> The list of fixed issues:
>>>>> http://s.apache.org/Q3i
>>>>>
>>>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>>>> for the source and binary artifacts can be found at:
>>>>> http://people.apache.org/~brock/flume-1.3.0-rc4/
>>>>>
>>>>> Nexus Staging Repository:
>>>>> https://repository.apache.org/content/repositories/orgapacheflume-047/
>>>>>
>>>>> The tag to be voted on:
>>>>> http://s.apache.org/80Y
>>>>>
>>>>> The KEYS file can be found here:
>>>>> https://svn.apache.org/repos/asf/flume/dist/KEYS
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Alexander Alten-Lorenz
>>> http://mapredit.blogspot.com
>>> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>>>
>>>
>>
>>
>
> --
> Alexander Alten-Lorenz
> http://mapredit.blogspot.com
> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

This is the second release for Apache Flume as a top-level project,
version 1.3.0. We are voting on release candidate rc5.

*** Please cast your vote within the next 72 hours ***

The list of fixed issues:
http://s.apache.org/RoN

The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
for the source and binary artifacts can be found at:
http://people.apache.org/~brock/flume-1.3.0-rc5/

Nexus Staging Repository:
https://repository.apache.org/content/repositories/orgapacheflume-059/

The tag to be voted on:
http://s.apache.org/gC

The KEYS file can be found here:
https://svn.apache.org/repos/asf/flume/dist/KEYS

+1
Looks good. Verified build and tests.

-roshan
On Wed, Nov 21, 2012 at 11:07 AM, Brock Noland <[EMAIL PROTECTED]> wrote:

> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc5.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/RoN
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc5/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-059/
>
> The tag to be voted on:
> http://s.apache.org/gC
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS
>

+1

Verified build, sanity test, sigs, hashes, LICENSE, and lib/.

On Wed, Nov 21, 2012 at 1:07 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc5.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/RoN
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc5/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-059/
>
> The tag to be voted on:
> http://s.apache.org/gC
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

+1.

* Verified checksums and signature.
* Ran full build and agent with sample configuration
* Verified LICENSE, NOTICE, DEVNOTES, CHANGELOG, README, RELEASE-NOTES

Excellent work, Brock! Thanks for being so patient and working hard to push the release out.
Thanks,
Hari

--
Hari Shreedharan
On Wednesday, November 21, 2012 at 3:12 PM, Brock Noland wrote:

> +1
>
> Verified build, sanity test, sigs, hashes, LICENSE, and lib/.
>
> On Wed, Nov 21, 2012 at 1:07 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > This is the second release for Apache Flume as a top-level project,
> > version 1.3.0. We are voting on release candidate rc5.
> >
> > *** Please cast your vote within the next 72 hours ***
> >
> > The list of fixed issues:
> > http://s.apache.org/RoN
> >
> > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > for the source and binary artifacts can be found at:
> > http://people.apache.org/~brock/flume-1.3.0-rc5/
> >
> > Nexus Staging Repository:
> > https://repository.apache.org/content/repositories/orgapacheflume-059/
> >
> > The tag to be voted on:
> > http://s.apache.org/gC
> >
> > The KEYS file can be found here:
> > https://svn.apache.org/repos/asf/flume/dist/KEYS
> >
>
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>
>

+1

checksum, tests and build okay

Thanks Brock!

cheers,
 Alex

On Nov 22, 2012, at 2:06 AM, Hari Shreedharan <[EMAIL PROTECTED]> wrote:

> +1.
>
> * Verified checksums and signature.
> * Ran full build and agent with sample configuration
> * Verified LICENSE, NOTICE, DEVNOTES, CHANGELOG, README, RELEASE-NOTES
>
> Excellent work, Brock! Thanks for being so patient and working hard to push the release out.
>
>
> Thanks,
> Hari
>
> --
> Hari Shreedharan
>
>
> On Wednesday, November 21, 2012 at 3:12 PM, Brock Noland wrote:
>
>> +1
>>
>> Verified build, sanity test, sigs, hashes, LICENSE, and lib/.
>>
>> On Wed, Nov 21, 2012 at 1:07 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>>> This is the second release for Apache Flume as a top-level project,
>>> version 1.3.0. We are voting on release candidate rc5.
>>>
>>> *** Please cast your vote within the next 72 hours ***
>>>
>>> The list of fixed issues:
>>> http://s.apache.org/RoN
>>>
>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>> for the source and binary artifacts can be found at:
>>> http://people.apache.org/~brock/flume-1.3.0-rc5/
>>>
>>> Nexus Staging Repository:
>>> https://repository.apache.org/content/repositories/orgapacheflume-059/
>>>
>>> The tag to be voted on:
>>> http://s.apache.org/gC
>>>
>>> The KEYS file can be found here:
>>> https://svn.apache.org/repos/asf/flume/dist/KEYS
>>>
>>
>>
>>
>>
>> --
>> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>>
>>
>
>

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF

+1

* Checked signatures, checked check sums
* Artifacts are compiling for me
* Tests seems to be passing
* LICENSE file seems to be handled correctly
* Top level files NOTICE, README, RELEASE-NOTES, CHANGELOG seems fine

Jarcec

On Wed, Nov 21, 2012 at 01:07:56PM -0600, Brock Noland wrote:
> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc5.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/RoN
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc5/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-059/
>
> The tag to be voted on:
> http://s.apache.org/gC
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS

HI,

This good news that flume1.3.0 released.

I have the old version . How I can install this new version? should I
remove the old version and then Install the new version. Another thing, is
this version support the directory spooling?

How I can config the agent that continuously monitor the director for new
file and once file added to folder move to hdfs? The directory locate at
/usr/Data/

Many thanks

Best regards

On Wed, Nov 21, 2012 at 7:07 PM, Brock Noland <[EMAIL PROTECTED]> wrote:

> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc5.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/RoN
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc5/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-059/
>
> The tag to be voted on:
> http://s.apache.org/gC
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS
>

The release is not yet complete, since the vote is not complete yet. Once this vote is completed, the release will be available for download at flume.apache.org.
Thanks,
Hari

--
Hari Shreedharan
On Friday, November 23, 2012 at 1:14 PM, kashif khan wrote:

> HI,
>
> This good news that flume1.3.0 released.
>
> I have the old version . How I can install this new version? should I
> remove the old version and then Install the new version. Another thing, is
> this version support the directory spooling?
>
> How I can config the agent that continuously monitor the director for new
> file and once file added to folder move to hdfs? The directory locate at
> /usr/Data/
>
> Many thanks
>
> Best regards
>
>
>
> On Wed, Nov 21, 2012 at 7:07 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>
> > This is the second release for Apache Flume as a top-level project,
> > version 1.3.0. We are voting on release candidate rc5.
> >
> > *** Please cast your vote within the next 72 hours ***
> >
> > The list of fixed issues:
> > http://s.apache.org/RoN
> >
> > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > for the source and binary artifacts can be found at:
> > http://people.apache.org/~brock/flume-1.3.0-rc5/
> >
> > Nexus Staging Repository:
> > https://repository.apache.org/content/repositories/orgapacheflume-059/
> >
> > The tag to be voted on:
> > http://s.apache.org/gC
> >
> > The KEYS file can be found here:
> > https://svn.apache.org/repos/asf/flume/dist/KEYS
> >
>
>
>

Brock,

I'd recommend keeping the vote open till at least Tuesday, so we can have more people look at the RC. Others may notice things which we may not have. That said, it is your call when to close the vote, since you already have 3 PMC +1s.
Thanks,
Hari

--
Hari Shreedharan
On Friday, November 23, 2012 at 1:16 PM, Hari Shreedharan wrote:

> The release is not yet complete, since the vote is not complete yet. Once this vote is completed, the release will be available for download at flume.apache.org (http://flume.apache.org).
>
>
> Thanks,
> Hari
>
> --
> Hari Shreedharan
>
>
> On Friday, November 23, 2012 at 1:14 PM, kashif khan wrote:
>
> > HI,
> >
> > This good news that flume1.3.0 released.
> >
> > I have the old version . How I can install this new version? should I
> > remove the old version and then Install the new version. Another thing, is
> > this version support the directory spooling?
> >
> > How I can config the agent that continuously monitor the director for new
> > file and once file added to folder move to hdfs? The directory locate at
> > /usr/Data/
> >
> > Many thanks
> >
> > Best regards
> >
> >
> >
> > On Wed, Nov 21, 2012 at 7:07 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> >
> > > This is the second release for Apache Flume as a top-level project,
> > > version 1.3.0. We are voting on release candidate rc5.
> > >
> > > *** Please cast your vote within the next 72 hours ***
> > >
> > > The list of fixed issues:
> > > http://s.apache.org/RoN
> > >
> > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > > for the source and binary artifacts can be found at:
> > > http://people.apache.org/~brock/flume-1.3.0-rc5/
> > >
> > > Nexus Staging Repository:
> > > https://repository.apache.org/content/repositories/orgapacheflume-059/
> > >
> > > The tag to be voted on:
> > > http://s.apache.org/gC
> > >
> > > The KEYS file can be found here:
> > > https://svn.apache.org/repos/asf/flume/dist/KEYS
> > >
> >
> >
> >
> >
>
>

Hi,

Yes I agree, the vote should remain open until Tuesday at 1PM CST.

Brock

On Sat, Nov 24, 2012 at 2:03 AM, Hari Shreedharan
<[EMAIL PROTECTED]> wrote:
> Brock,
>
> I'd recommend keeping the vote open till at least Tuesday, so we can have more people look at the RC. Others may notice things which we may not have. That said, it is your call when to close the vote, since you already have 3 PMC +1s.
>
>
> Thanks,
> Hari
>
> --
> Hari Shreedharan
>
>
> On Friday, November 23, 2012 at 1:16 PM, Hari Shreedharan wrote:
>
>> The release is not yet complete, since the vote is not complete yet. Once this vote is completed, the release will be available for download at flume.apache.org (http://flume.apache.org).
>>
>>
>> Thanks,
>> Hari
>>
>> --
>> Hari Shreedharan
>>
>>
>> On Friday, November 23, 2012 at 1:14 PM, kashif khan wrote:
>>
>> > HI,
>> >
>> > This good news that flume1.3.0 released.
>> >
>> > I have the old version . How I can install this new version? should I
>> > remove the old version and then Install the new version. Another thing, is
>> > this version support the directory spooling?
>> >
>> > How I can config the agent that continuously monitor the director for new
>> > file and once file added to folder move to hdfs? The directory locate at
>> > /usr/Data/
>> >
>> > Many thanks
>> >
>> > Best regards
>> >
>> >
>> >
>> > On Wed, Nov 21, 2012 at 7:07 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
>> >
>> > > This is the second release for Apache Flume as a top-level project,
>> > > version 1.3.0. We are voting on release candidate rc5.
>> > >
>> > > *** Please cast your vote within the next 72 hours ***
>> > >
>> > > The list of fixed issues:
>> > > http://s.apache.org/RoN
>> > >
>> > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> > > for the source and binary artifacts can be found at:
>> > > http://people.apache.org/~brock/flume-1.3.0-rc5/
>> > >
>> > > Nexus Staging Repository:
>> > > https://repository.apache.org/content/repositories/orgapacheflume-059/
>> > >
>> > > The tag to be voted on:
>> > > http://s.apache.org/gC
>> > >
>> > > The KEYS file can be found here:
>> > > https://svn.apache.org/repos/asf/flume/dist/KEYS
>> > >
>> >
>> >
>> >
>> >
>>
>>
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

Thanks for the effort in getting this through Brock. Here is my vote:

+1

* Verified all signatures and checksums
* Verified the build and tests
* Did simple configuration testing with staged binaries

Regards,
Arvind Prabhakar

On Wed, Nov 21, 2012 at 11:07 AM, Brock Noland <[EMAIL PROTECTED]> wrote:

> This is the second release for Apache Flume as a top-level project,
> version 1.3.0. We are voting on release candidate rc5.
>
> *** Please cast your vote within the next 72 hours ***
>
> The list of fixed issues:
> http://s.apache.org/RoN
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found at:
> http://people.apache.org/~brock/flume-1.3.0-rc5/
>
> Nexus Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheflume-059/
>
> The tag to be voted on:
> http://s.apache.org/gC
>
> The KEYS file can be found here:
> https://svn.apache.org/repos/asf/flume/dist/KEYS
>

Stil looking for at least one more PMC vote..

On Fri, Nov 30, 2012 at 2:00 AM, Alexander Alten-Lorenz
<[EMAIL PROTECTED]> wrote:
> +1
>
> - Build / Test / Verification succeeded
> - [FLUME-1743] - Multiport syslog tcp source does not load (v1.3 rc5) confirmed as working
>
> Best,
>  Alex
>
>
>
> On Nov 30, 2012, at 8:03 AM, Mike Percy <[EMAIL PROTECTED]> wrote:
>
>> +1 to release rc6
>>
>> * Verified signatures & checksums
>> * Ran unit tests
>> * Quick smoke test on binary artifact
>> * LICENSE, NOTICE, README, DEVNOTES, and RELEASE-NOTES look good
>> * diff -rq of source tarball against pristine tag looks fine
>>
>> Regards,
>> Mike
>>
>> On Thu, Nov 29, 2012 at 1:25 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>>
>>> This is the second release for Apache Flume as a top-level project,
>>> version 1.3.0. We are voting on release candidate rc6.
>>>
>>> *** Please cast your vote within the next 72 hours ***
>>>
>>> The list of fixed issues:
>>> http://s.apache.org/Bdw
>>>
>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>>>
>>> for the source and binary artifacts can be found at:
>>> http://people.apache.org/~brock/flume-1.3.0-rc6/
>>>
>>> Nexus Staging Repository:
>>> https://repository.apache.org/content/repositories/orgapacheflume-097/
>>>
>>> The tag to be voted on:
>>> http://s.apache.org/us
>>>
>>> The KEYS file can be found here:
>>> https://dist.apache.org/repos/dist/release/flume/KEYS
>>>
>
> --
> Alexander Alten-Lorenz
> http://mapredit.blogspot.com
> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

+1. Looks good.

* Ran full build with unit tests
* Verified LICENSE, DEVNOTES, CHANGELOG,README,RELEASE-NOTES, NOTICE
* Verified signatures and checksums.

Thanks for all the work you put into this release, Brock!
Thanks,
Hari

--
Hari Shreedharan
On Sunday, December 2, 2012 at 11:03 AM, Brock Noland wrote:

> Stil looking for at least one more PMC vote..
>
> On Fri, Nov 30, 2012 at 2:00 AM, Alexander Alten-Lorenz
> <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > +1
> >
> > - Build / Test / Verification succeeded
> > - [FLUME-1743] - Multiport syslog tcp source does not load (v1.3 rc5) confirmed as working
> >
> > Best,
> > Alex
> >
> >
> >
> > On Nov 30, 2012, at 8:03 AM, Mike Percy <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> >
> > > +1 to release rc6
> > >
> > > * Verified signatures & checksums
> > > * Ran unit tests
> > > * Quick smoke test on binary artifact
> > > * LICENSE, NOTICE, README, DEVNOTES, and RELEASE-NOTES look good
> > > * diff -rq of source tarball against pristine tag looks fine
> > >
> > > Regards,
> > > Mike
> > >
> > > On Thu, Nov 29, 2012 at 1:25 PM, Brock Noland <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote:
> > >
> > > > This is the second release for Apache Flume as a top-level project,
> > > > version 1.3.0. We are voting on release candidate rc6.
> > > >
> > > > *** Please cast your vote within the next 72 hours ***
> > > >
> > > > The list of fixed issues:
> > > > http://s.apache.org/Bdw
> > > >
> > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> > > >
> > > > for the source and binary artifacts can be found at:
> > > > http://people.apache.org/~brock/flume-1.3.0-rc6/
> > > >
> > > > Nexus Staging Repository:
> > > > https://repository.apache.org/content/repositories/orgapacheflume-097/
> > > >
> > > > The tag to be voted on:
> > > > http://s.apache.org/us
> > > >
> > > > The KEYS file can be found here:
> > > > https://dist.apache.org/repos/dist/release/flume/KEYS
> > > >
> > >
> > >
> >
> >
> > --
> > Alexander Alten-Lorenz
> > http://mapredit.blogspot.com
> > German Hadoop LinkedIn Group: http://goo.gl/N8pCF
> >
>
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
>
>

+1

* Signature and checksums fits
* It seems that LICENSE file covers all shipped jars
* Compiles
* Tests seems to be passing
* Top level files seems to be fine (CHANGELOG, DEVNOTES, ...)

Jarcec

On Sun, Dec 02, 2012 at 01:03:12PM -0600, Brock Noland wrote:
> Stil looking for at least one more PMC vote..
>
> On Fri, Nov 30, 2012 at 2:00 AM, Alexander Alten-Lorenz
> <[EMAIL PROTECTED]> wrote:
> > +1
> >
> > - Build / Test / Verification succeeded
> > - [FLUME-1743] - Multiport syslog tcp source does not load (v1.3 rc5) confirmed as working
> >
> > Best,
> >  Alex
> >
> >
> >
> > On Nov 30, 2012, at 8:03 AM, Mike Percy <[EMAIL PROTECTED]> wrote:
> >
> >> +1 to release rc6
> >>
> >> * Verified signatures & checksums
> >> * Ran unit tests
> >> * Quick smoke test on binary artifact
> >> * LICENSE, NOTICE, README, DEVNOTES, and RELEASE-NOTES look good
> >> * diff -rq of source tarball against pristine tag looks fine
> >>
> >> Regards,
> >> Mike
> >>
> >> On Thu, Nov 29, 2012 at 1:25 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
> >>
> >>> This is the second release for Apache Flume as a top-level project,
> >>> version 1.3.0. We are voting on release candidate rc6.
> >>>
> >>> *** Please cast your vote within the next 72 hours ***
> >>>
> >>> The list of fixed issues:
> >>> http://s.apache.org/Bdw
> >>>
> >>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> >>>
> >>> for the source and binary artifacts can be found at:
> >>> http://people.apache.org/~brock/flume-1.3.0-rc6/
> >>>
> >>> Nexus Staging Repository:
> >>> https://repository.apache.org/content/repositories/orgapacheflume-097/
> >>>
> >>> The tag to be voted on:
> >>> http://s.apache.org/us
> >>>
> >>> The KEYS file can be found here:
> >>> https://dist.apache.org/repos/dist/release/flume/KEYS
> >>>
> >
> > --
> > Alexander Alten-Lorenz
> > http://mapredit.blogspot.com
> > German Hadoop LinkedIn Group: http://goo.gl/N8pCF
> >
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

The vote passes:

+1: 5 - Brock, Mike, Hari, Jarcec, Alex (non-binding)
0:  0
-1: 0

Thank you to everyone who voted on this and all the other RC's!

Brock

On Sun, Dec 2, 2012 at 2:11 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]> wrote:
> +1
>
> * Signature and checksums fits
> * It seems that LICENSE file covers all shipped jars
> * Compiles
> * Tests seems to be passing
> * Top level files seems to be fine (CHANGELOG, DEVNOTES, ...)
>
> Jarcec
>
> On Sun, Dec 02, 2012 at 01:03:12PM -0600, Brock Noland wrote:
>> Stil looking for at least one more PMC vote..
>>
>> On Fri, Nov 30, 2012 at 2:00 AM, Alexander Alten-Lorenz
>> <[EMAIL PROTECTED]> wrote:
>> > +1
>> >
>> > - Build / Test / Verification succeeded
>> > - [FLUME-1743] - Multiport syslog tcp source does not load (v1.3 rc5) confirmed as working
>> >
>> > Best,
>> >  Alex
>> >
>> >
>> >
>> > On Nov 30, 2012, at 8:03 AM, Mike Percy <[EMAIL PROTECTED]> wrote:
>> >
>> >> +1 to release rc6
>> >>
>> >> * Verified signatures & checksums
>> >> * Ran unit tests
>> >> * Quick smoke test on binary artifact
>> >> * LICENSE, NOTICE, README, DEVNOTES, and RELEASE-NOTES look good
>> >> * diff -rq of source tarball against pristine tag looks fine
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >> On Thu, Nov 29, 2012 at 1:25 PM, Brock Noland <[EMAIL PROTECTED]> wrote:
>> >>
>> >>> This is the second release for Apache Flume as a top-level project,
>> >>> version 1.3.0. We are voting on release candidate rc6.
>> >>>
>> >>> *** Please cast your vote within the next 72 hours ***
>> >>>
>> >>> The list of fixed issues:
>> >>> http://s.apache.org/Bdw
>> >>>
>> >>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
>> >>>
>> >>> for the source and binary artifacts can be found at:
>> >>> http://people.apache.org/~brock/flume-1.3.0-rc6/
>> >>>
>> >>> Nexus Staging Repository:
>> >>> https://repository.apache.org/content/repositories/orgapacheflume-097/
>> >>>
>> >>> The tag to be voted on:
>> >>> http://s.apache.org/us
>> >>>
>> >>> The KEYS file can be found here:
>> >>> https://dist.apache.org/repos/dist/release/flume/KEYS
>> >>>
>> >
>> > --
>> > Alexander Alten-Lorenz
>> > http://mapredit.blogspot.com
>> > German Hadoop LinkedIn Group: http://goo.gl/N8pCF
>> >
>>
>>
>>
>> --
>> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/