You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Eric Sammer <es...@cloudera.com> on 2011/12/28 02:51:42 UTC
Flume (NG) 1.0.0 rc1
All:
I've cut an early RC of flume-1.0.0-incubating. This is *not* yet ready for
a vote as there's at least one maven issue left to be worked out and it's
still a SNAPSHOT. That said, I would like feedback so we can knock out any
remaining issues.
tarball:
http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
GPG signature:
http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
md5sum:
http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
affectsVersion = v1.0.0 please).
Thanks.
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Ralph Goers <ra...@dslextreme.com>.
Also, don't get discouraged. Getting the first release out at the ASF is always a challenge. But once you get the release process down subsequent ones will be much easier - especially if you document the exact process for Flume on the wiki.
Ralph
On Dec 28, 2011, at 4:19 PM, Patrick Hunt wrote:
> On Wed, Dec 28, 2011 at 3:45 PM, Eric Sammer <es...@cloudera.com> wrote:
>> On Wed, Dec 28, 2011 at 2:00 PM, Patrick Hunt <ph...@apache.org> wrote:
>>
>
>>>
>>> 2) you're missing the incubation disclaimer file.
>>>
>>
>> It was missing because of a missed copy in the maven assembly. Fixed in
>> next RC. The behemoth (non-normative) guide[2] talks about a STATUS file
>> but never mentions what the contents should be, and the (normative) release
>> FAQ[3] never mentions it at all. Feedback welcome on that one (including
>> striking the behemoth guide from the face of the Earth - that would be fine
>> too).
>
> The status is this afaik:
> http://incubator.apache.org/projects/flume.html
> which I had reviewed and looked ok.
>
>>
>> [2] http://incubator.apache.org/guides/releasemanagement.html#check-list
>> [3] http://www.apache.org/dev/release.html
>>
>>
>>> 3) you're missing the keys file on dist, see this for mrunit example:
>>> http://www.apache.org/dist/incubator/mrunit/KEYS
>>
>>
>> I'm confused. This existed. Arvind just also added his key, but otherwise
>> it's there[4].
>
> Arvind/I responded on a separate thread, I think we'll be good.
>
>
>>> 7) your readme should say
>>> "h1. Welcome to Apache Flume!"
>>>
>>
>> That wasn't listed in any of the release docs I found but if that's a
>> requirement, I'll do it. Also, I hereby state my opinion that it's silly. ;)
>>
>
> Read over the branding guidelines:
> http://www.apache.org/foundation/marks/pmcs.html
> specifically "The primary branding for any project or product name
> must be in the form of "Apache Foo"."
> Something like the README it's important to state that up front.
>
> Looks good, keep up the good work.
>
> Regards,
>
> Patrick
Re: Flume (NG) 1.0.0 rc1
Posted by Patrick Hunt <ph...@apache.org>.
On Wed, Dec 28, 2011 at 3:45 PM, Eric Sammer <es...@cloudera.com> wrote:
> On Wed, Dec 28, 2011 at 2:00 PM, Patrick Hunt <ph...@apache.org> wrote:
>
>>
>> 2) you're missing the incubation disclaimer file.
>>
>
> It was missing because of a missed copy in the maven assembly. Fixed in
> next RC. The behemoth (non-normative) guide[2] talks about a STATUS file
> but never mentions what the contents should be, and the (normative) release
> FAQ[3] never mentions it at all. Feedback welcome on that one (including
> striking the behemoth guide from the face of the Earth - that would be fine
> too).
The status is this afaik:
http://incubator.apache.org/projects/flume.html
which I had reviewed and looked ok.
>
> [2] http://incubator.apache.org/guides/releasemanagement.html#check-list
> [3] http://www.apache.org/dev/release.html
>
>
>> 3) you're missing the keys file on dist, see this for mrunit example:
>> http://www.apache.org/dist/incubator/mrunit/KEYS
>
>
> I'm confused. This existed. Arvind just also added his key, but otherwise
> it's there[4].
Arvind/I responded on a separate thread, I think we'll be good.
>> 7) your readme should say
>> "h1. Welcome to Apache Flume!"
>>
>
> That wasn't listed in any of the release docs I found but if that's a
> requirement, I'll do it. Also, I hereby state my opinion that it's silly. ;)
>
Read over the branding guidelines:
http://www.apache.org/foundation/marks/pmcs.html
specifically "The primary branding for any project or product name
must be in the form of "Apache Foo"."
Something like the README it's important to state that up front.
Looks good, keep up the good work.
Regards,
Patrick
Re: Flume (NG) 1.0.0 rc1
Posted by Eric Sammer <es...@cloudera.com>.
Oh. I could have sworn I did it. Sorry.
On Wed, Dec 28, 2011 at 3:59 PM, Arvind Prabhakar <ar...@apache.org> wrote:
> For the confusion around KEYS file - it was I who copied it over after
> seeing Patrick's feedback. From what I can tell, there is no automated
> system that puts this file in place from the podling's SVN dist
> directory.
>
> Thanks,
> Arvind
>
> On Wed, Dec 28, 2011 at 3:45 PM, Eric Sammer <es...@cloudera.com> wrote:
> > On Wed, Dec 28, 2011 at 2:00 PM, Patrick Hunt <ph...@apache.org> wrote:
> >
> >> -1, coming along but some serious issues still need to be addressed:
> >>
> >> 1) incorrect licensing of files
> >>
> >> many of the files have invalid license headers. See the bin directory,
> >> for example flume-daemon.sh (also conf, etc...)
> >>
> >> What's concerning is that rat isn't picking up on this. You should fix
> >> your RAT setup before addressing this and verify that it's correctly
> >> picking up on license issues (otw you'll need to verify everything by
> >> hand).
> >>
> >
> > RAT is picking them up and reporting on them (as AL). At least it is in
> the
> > builds I have and on Jenkins[1]. FWIW, a bunch of old files were also
> > trimmed (including flume-daemon.sh) so the next RC won't have them.
> >
> > [1] https://builds.apache.org/job/flume-728/ws/target/rat.txt
> >
> >
> >>
> >> 2) you're missing the incubation disclaimer file.
> >>
> >
> > It was missing because of a missed copy in the maven assembly. Fixed in
> > next RC. The behemoth (non-normative) guide[2] talks about a STATUS file
> > but never mentions what the contents should be, and the (normative)
> release
> > FAQ[3] never mentions it at all. Feedback welcome on that one (including
> > striking the behemoth guide from the face of the Earth - that would be
> fine
> > too).
> >
> > [2] http://incubator.apache.org/guides/releasemanagement.html#check-list
> > [3] http://www.apache.org/dev/release.html
> >
> >
> >> 3) you're missing the keys file on dist, see this for mrunit example:
> >> http://www.apache.org/dist/incubator/mrunit/KEYS
> >
> >
> > I'm confused. This existed. Arvind just also added his key, but otherwise
> > it's there[4].
> >
> > [4] http://svn.apache.org/repos/asf/incubator/flume/dist/
> >
> > 4) not a blocker but it's very common to have a CHANGES file that
> >> provides attribution of each change and who made it
> >>
> >>
> http://incubator.apache.org/guides/releasemanagement.html#distribution-release-documentation
> >
> >
> > I'll see if I can sneak it in.
> >
> >
> >> 5) the tests failed (ubuntu ocelot 32 with sun java)
> >> Running org.apache.flume.node.TestAbstractLogicalNodeManager
> >> Process 1325108442142 is killed.
> >> Running org.apache.flume.node.TestFlumeNode
> >> Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.094
> sec
> >>
> >
> > Bruno found / fixed this one. It was a race condition (which is why I
> > didn't see it).
> >
> >
> >> 6) what are the executables in the bin directory? Are you distributing
> >> those as part of the source release for a reason? What license are
> >> they under?
> >>
> >
> > Some were left over from Flume OG (removed for next RC) and some are
> shell
> > scripts required to run flume. They aren't meant to be run. The maven
> > assembly copies them into the binary artifact. The binary executables
> (from
> > the windows build) are now gone as well.
> >
> >
> >> 7) your readme should say
> >> "h1. Welcome to Apache Flume!"
> >>
> >
> > That wasn't listed in any of the release docs I found but if that's a
> > requirement, I'll do it. Also, I hereby state my opinion that it's
> silly. ;)
> >
> >
> >> Also see the release guidelines, and esp this checklist:
> >> http://incubator.apache.org/guides/releasemanagement.html#check-list
> >
> >
> > I was working from this.
> >
> >
> >>
> >>
> >> Patrick
> >>
> >> On Wed, Dec 28, 2011 at 11:08 AM, Arvind Prabhakar <ar...@apache.org>
> >> wrote:
> >> > Also, the KEYS can be found at:
> >> >
> >> > https://svn.apache.org/repos/asf/incubator/flume/dist/KEYS
> >> >
> >> > On Wed, Dec 28, 2011 at 10:55 AM, Arvind Prabhakar <arvind@apache.org
> >
> >> wrote:
> >> >> The link to the GPG signature seems to be corrupted. Here is the link
> >> >> that works:
> >> >>
> >> >>
> >>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
> >> >>
> >> >> Thanks,
> >> >> Arvind
> >> >>
> >> >> On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com>
> >> wrote:
> >> >>> All:
> >> >>>
> >> >>> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet
> >> ready for
> >> >>> a vote as there's at least one maven issue left to be worked out and
> >> it's
> >> >>> still a SNAPSHOT. That said, I would like feedback so we can knock
> out
> >> any
> >> >>> remaining issues.
> >> >>>
> >> >>> tarball:
> >> >>>
> >>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
> >> >>> GPG signature:
> >> >>>
> >>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
> >> >>> md5sum:
> >> >>>
> >>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
> >> >>>
> >> >>> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME(use
> >> >>> affectsVersion = v1.0.0 please).
> >> >>>
> >> >>> Thanks.
> >> >>> --
> >> >>> Eric Sammer
> >> >>> twitter: esammer
> >> >>> data: www.cloudera.com
> >>
> >
> >
> >
> > --
> > Eric Sammer
> > twitter: esammer
> > data: www.cloudera.com
>
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Patrick Hunt <ph...@apache.org>.
Have you published your key on id.apache.org? (it's relatively new)
https://blogs.apache.org/infra/entry/https_id_apache_org_new
that might be what's pushing it over for some people.
also see this, looks relatively up to date/succinct:
http://incubator.apache.org/isis/docbkx/html/guide/apas05.html
Patrick
On Wed, Dec 28, 2011 at 3:59 PM, Arvind Prabhakar <ar...@apache.org> wrote:
> For the confusion around KEYS file - it was I who copied it over after
> seeing Patrick's feedback. From what I can tell, there is no automated
> system that puts this file in place from the podling's SVN dist
> directory.
>
> Thanks,
> Arvind
>
> On Wed, Dec 28, 2011 at 3:45 PM, Eric Sammer <es...@cloudera.com> wrote:
>> On Wed, Dec 28, 2011 at 2:00 PM, Patrick Hunt <ph...@apache.org> wrote:
>>
>>> -1, coming along but some serious issues still need to be addressed:
>>>
>>> 1) incorrect licensing of files
>>>
>>> many of the files have invalid license headers. See the bin directory,
>>> for example flume-daemon.sh (also conf, etc...)
>>>
>>> What's concerning is that rat isn't picking up on this. You should fix
>>> your RAT setup before addressing this and verify that it's correctly
>>> picking up on license issues (otw you'll need to verify everything by
>>> hand).
>>>
>>
>> RAT is picking them up and reporting on them (as AL). At least it is in the
>> builds I have and on Jenkins[1]. FWIW, a bunch of old files were also
>> trimmed (including flume-daemon.sh) so the next RC won't have them.
>>
>> [1] https://builds.apache.org/job/flume-728/ws/target/rat.txt
>>
>>
>>>
>>> 2) you're missing the incubation disclaimer file.
>>>
>>
>> It was missing because of a missed copy in the maven assembly. Fixed in
>> next RC. The behemoth (non-normative) guide[2] talks about a STATUS file
>> but never mentions what the contents should be, and the (normative) release
>> FAQ[3] never mentions it at all. Feedback welcome on that one (including
>> striking the behemoth guide from the face of the Earth - that would be fine
>> too).
>>
>> [2] http://incubator.apache.org/guides/releasemanagement.html#check-list
>> [3] http://www.apache.org/dev/release.html
>>
>>
>>> 3) you're missing the keys file on dist, see this for mrunit example:
>>> http://www.apache.org/dist/incubator/mrunit/KEYS
>>
>>
>> I'm confused. This existed. Arvind just also added his key, but otherwise
>> it's there[4].
>>
>> [4] http://svn.apache.org/repos/asf/incubator/flume/dist/
>>
>> 4) not a blocker but it's very common to have a CHANGES file that
>>> provides attribution of each change and who made it
>>>
>>> http://incubator.apache.org/guides/releasemanagement.html#distribution-release-documentation
>>
>>
>> I'll see if I can sneak it in.
>>
>>
>>> 5) the tests failed (ubuntu ocelot 32 with sun java)
>>> Running org.apache.flume.node.TestAbstractLogicalNodeManager
>>> Process 1325108442142 is killed.
>>> Running org.apache.flume.node.TestFlumeNode
>>> Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.094 sec
>>>
>>
>> Bruno found / fixed this one. It was a race condition (which is why I
>> didn't see it).
>>
>>
>>> 6) what are the executables in the bin directory? Are you distributing
>>> those as part of the source release for a reason? What license are
>>> they under?
>>>
>>
>> Some were left over from Flume OG (removed for next RC) and some are shell
>> scripts required to run flume. They aren't meant to be run. The maven
>> assembly copies them into the binary artifact. The binary executables (from
>> the windows build) are now gone as well.
>>
>>
>>> 7) your readme should say
>>> "h1. Welcome to Apache Flume!"
>>>
>>
>> That wasn't listed in any of the release docs I found but if that's a
>> requirement, I'll do it. Also, I hereby state my opinion that it's silly. ;)
>>
>>
>>> Also see the release guidelines, and esp this checklist:
>>> http://incubator.apache.org/guides/releasemanagement.html#check-list
>>
>>
>> I was working from this.
>>
>>
>>>
>>>
>>> Patrick
>>>
>>> On Wed, Dec 28, 2011 at 11:08 AM, Arvind Prabhakar <ar...@apache.org>
>>> wrote:
>>> > Also, the KEYS can be found at:
>>> >
>>> > https://svn.apache.org/repos/asf/incubator/flume/dist/KEYS
>>> >
>>> > On Wed, Dec 28, 2011 at 10:55 AM, Arvind Prabhakar <ar...@apache.org>
>>> wrote:
>>> >> The link to the GPG signature seems to be corrupted. Here is the link
>>> >> that works:
>>> >>
>>> >>
>>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>>> >>
>>> >> Thanks,
>>> >> Arvind
>>> >>
>>> >> On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com>
>>> wrote:
>>> >>> All:
>>> >>>
>>> >>> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet
>>> ready for
>>> >>> a vote as there's at least one maven issue left to be worked out and
>>> it's
>>> >>> still a SNAPSHOT. That said, I would like feedback so we can knock out
>>> any
>>> >>> remaining issues.
>>> >>>
>>> >>> tarball:
>>> >>>
>>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
>>> >>> GPG signature:
>>> >>>
>>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>>> >>> md5sum:
>>> >>>
>>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
>>> >>>
>>> >>> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
>>> >>> affectsVersion = v1.0.0 please).
>>> >>>
>>> >>> Thanks.
>>> >>> --
>>> >>> Eric Sammer
>>> >>> twitter: esammer
>>> >>> data: www.cloudera.com
>>>
>>
>>
>>
>> --
>> Eric Sammer
>> twitter: esammer
>> data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Arvind Prabhakar <ar...@apache.org>.
For the confusion around KEYS file - it was I who copied it over after
seeing Patrick's feedback. From what I can tell, there is no automated
system that puts this file in place from the podling's SVN dist
directory.
Thanks,
Arvind
On Wed, Dec 28, 2011 at 3:45 PM, Eric Sammer <es...@cloudera.com> wrote:
> On Wed, Dec 28, 2011 at 2:00 PM, Patrick Hunt <ph...@apache.org> wrote:
>
>> -1, coming along but some serious issues still need to be addressed:
>>
>> 1) incorrect licensing of files
>>
>> many of the files have invalid license headers. See the bin directory,
>> for example flume-daemon.sh (also conf, etc...)
>>
>> What's concerning is that rat isn't picking up on this. You should fix
>> your RAT setup before addressing this and verify that it's correctly
>> picking up on license issues (otw you'll need to verify everything by
>> hand).
>>
>
> RAT is picking them up and reporting on them (as AL). At least it is in the
> builds I have and on Jenkins[1]. FWIW, a bunch of old files were also
> trimmed (including flume-daemon.sh) so the next RC won't have them.
>
> [1] https://builds.apache.org/job/flume-728/ws/target/rat.txt
>
>
>>
>> 2) you're missing the incubation disclaimer file.
>>
>
> It was missing because of a missed copy in the maven assembly. Fixed in
> next RC. The behemoth (non-normative) guide[2] talks about a STATUS file
> but never mentions what the contents should be, and the (normative) release
> FAQ[3] never mentions it at all. Feedback welcome on that one (including
> striking the behemoth guide from the face of the Earth - that would be fine
> too).
>
> [2] http://incubator.apache.org/guides/releasemanagement.html#check-list
> [3] http://www.apache.org/dev/release.html
>
>
>> 3) you're missing the keys file on dist, see this for mrunit example:
>> http://www.apache.org/dist/incubator/mrunit/KEYS
>
>
> I'm confused. This existed. Arvind just also added his key, but otherwise
> it's there[4].
>
> [4] http://svn.apache.org/repos/asf/incubator/flume/dist/
>
> 4) not a blocker but it's very common to have a CHANGES file that
>> provides attribution of each change and who made it
>>
>> http://incubator.apache.org/guides/releasemanagement.html#distribution-release-documentation
>
>
> I'll see if I can sneak it in.
>
>
>> 5) the tests failed (ubuntu ocelot 32 with sun java)
>> Running org.apache.flume.node.TestAbstractLogicalNodeManager
>> Process 1325108442142 is killed.
>> Running org.apache.flume.node.TestFlumeNode
>> Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.094 sec
>>
>
> Bruno found / fixed this one. It was a race condition (which is why I
> didn't see it).
>
>
>> 6) what are the executables in the bin directory? Are you distributing
>> those as part of the source release for a reason? What license are
>> they under?
>>
>
> Some were left over from Flume OG (removed for next RC) and some are shell
> scripts required to run flume. They aren't meant to be run. The maven
> assembly copies them into the binary artifact. The binary executables (from
> the windows build) are now gone as well.
>
>
>> 7) your readme should say
>> "h1. Welcome to Apache Flume!"
>>
>
> That wasn't listed in any of the release docs I found but if that's a
> requirement, I'll do it. Also, I hereby state my opinion that it's silly. ;)
>
>
>> Also see the release guidelines, and esp this checklist:
>> http://incubator.apache.org/guides/releasemanagement.html#check-list
>
>
> I was working from this.
>
>
>>
>>
>> Patrick
>>
>> On Wed, Dec 28, 2011 at 11:08 AM, Arvind Prabhakar <ar...@apache.org>
>> wrote:
>> > Also, the KEYS can be found at:
>> >
>> > https://svn.apache.org/repos/asf/incubator/flume/dist/KEYS
>> >
>> > On Wed, Dec 28, 2011 at 10:55 AM, Arvind Prabhakar <ar...@apache.org>
>> wrote:
>> >> The link to the GPG signature seems to be corrupted. Here is the link
>> >> that works:
>> >>
>> >>
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>> >>
>> >> Thanks,
>> >> Arvind
>> >>
>> >> On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com>
>> wrote:
>> >>> All:
>> >>>
>> >>> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet
>> ready for
>> >>> a vote as there's at least one maven issue left to be worked out and
>> it's
>> >>> still a SNAPSHOT. That said, I would like feedback so we can knock out
>> any
>> >>> remaining issues.
>> >>>
>> >>> tarball:
>> >>>
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
>> >>> GPG signature:
>> >>>
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>> >>> md5sum:
>> >>>
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
>> >>>
>> >>> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
>> >>> affectsVersion = v1.0.0 please).
>> >>>
>> >>> Thanks.
>> >>> --
>> >>> Eric Sammer
>> >>> twitter: esammer
>> >>> data: www.cloudera.com
>>
>
>
>
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Eric Sammer <es...@cloudera.com>.
On Wed, Dec 28, 2011 at 2:00 PM, Patrick Hunt <ph...@apache.org> wrote:
> -1, coming along but some serious issues still need to be addressed:
>
> 1) incorrect licensing of files
>
> many of the files have invalid license headers. See the bin directory,
> for example flume-daemon.sh (also conf, etc...)
>
> What's concerning is that rat isn't picking up on this. You should fix
> your RAT setup before addressing this and verify that it's correctly
> picking up on license issues (otw you'll need to verify everything by
> hand).
>
RAT is picking them up and reporting on them (as AL). At least it is in the
builds I have and on Jenkins[1]. FWIW, a bunch of old files were also
trimmed (including flume-daemon.sh) so the next RC won't have them.
[1] https://builds.apache.org/job/flume-728/ws/target/rat.txt
>
> 2) you're missing the incubation disclaimer file.
>
It was missing because of a missed copy in the maven assembly. Fixed in
next RC. The behemoth (non-normative) guide[2] talks about a STATUS file
but never mentions what the contents should be, and the (normative) release
FAQ[3] never mentions it at all. Feedback welcome on that one (including
striking the behemoth guide from the face of the Earth - that would be fine
too).
[2] http://incubator.apache.org/guides/releasemanagement.html#check-list
[3] http://www.apache.org/dev/release.html
> 3) you're missing the keys file on dist, see this for mrunit example:
> http://www.apache.org/dist/incubator/mrunit/KEYS
I'm confused. This existed. Arvind just also added his key, but otherwise
it's there[4].
[4] http://svn.apache.org/repos/asf/incubator/flume/dist/
4) not a blocker but it's very common to have a CHANGES file that
> provides attribution of each change and who made it
>
> http://incubator.apache.org/guides/releasemanagement.html#distribution-release-documentation
I'll see if I can sneak it in.
> 5) the tests failed (ubuntu ocelot 32 with sun java)
> Running org.apache.flume.node.TestAbstractLogicalNodeManager
> Process 1325108442142 is killed.
> Running org.apache.flume.node.TestFlumeNode
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.094 sec
>
Bruno found / fixed this one. It was a race condition (which is why I
didn't see it).
> 6) what are the executables in the bin directory? Are you distributing
> those as part of the source release for a reason? What license are
> they under?
>
Some were left over from Flume OG (removed for next RC) and some are shell
scripts required to run flume. They aren't meant to be run. The maven
assembly copies them into the binary artifact. The binary executables (from
the windows build) are now gone as well.
> 7) your readme should say
> "h1. Welcome to Apache Flume!"
>
That wasn't listed in any of the release docs I found but if that's a
requirement, I'll do it. Also, I hereby state my opinion that it's silly. ;)
> Also see the release guidelines, and esp this checklist:
> http://incubator.apache.org/guides/releasemanagement.html#check-list
I was working from this.
>
>
> Patrick
>
> On Wed, Dec 28, 2011 at 11:08 AM, Arvind Prabhakar <ar...@apache.org>
> wrote:
> > Also, the KEYS can be found at:
> >
> > https://svn.apache.org/repos/asf/incubator/flume/dist/KEYS
> >
> > On Wed, Dec 28, 2011 at 10:55 AM, Arvind Prabhakar <ar...@apache.org>
> wrote:
> >> The link to the GPG signature seems to be corrupted. Here is the link
> >> that works:
> >>
> >>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
> >>
> >> Thanks,
> >> Arvind
> >>
> >> On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com>
> wrote:
> >>> All:
> >>>
> >>> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet
> ready for
> >>> a vote as there's at least one maven issue left to be worked out and
> it's
> >>> still a SNAPSHOT. That said, I would like feedback so we can knock out
> any
> >>> remaining issues.
> >>>
> >>> tarball:
> >>>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
> >>> GPG signature:
> >>>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
> >>> md5sum:
> >>>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
> >>>
> >>> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
> >>> affectsVersion = v1.0.0 please).
> >>>
> >>> Thanks.
> >>> --
> >>> Eric Sammer
> >>> twitter: esammer
> >>> data: www.cloudera.com
>
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Patrick Hunt <ph...@apache.org>.
-1, coming along but some serious issues still need to be addressed:
1) incorrect licensing of files
many of the files have invalid license headers. See the bin directory,
for example flume-daemon.sh (also conf, etc...)
What's concerning is that rat isn't picking up on this. You should fix
your RAT setup before addressing this and verify that it's correctly
picking up on license issues (otw you'll need to verify everything by
hand).
2) you're missing the incubation disclaimer file.
3) you're missing the keys file on dist, see this for mrunit example:
http://www.apache.org/dist/incubator/mrunit/KEYS
4) not a blocker but it's very common to have a CHANGES file that
provides attribution of each change and who made it
http://incubator.apache.org/guides/releasemanagement.html#distribution-release-documentation
5) the tests failed (ubuntu ocelot 32 with sun java)
Running org.apache.flume.node.TestAbstractLogicalNodeManager
Process 1325108442142 is killed.
Running org.apache.flume.node.TestFlumeNode
Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.094 sec
6) what are the executables in the bin directory? Are you distributing
those as part of the source release for a reason? What license are
they under?
7) your readme should say
"h1. Welcome to Apache Flume!"
Also see the release guidelines, and esp this checklist:
http://incubator.apache.org/guides/releasemanagement.html#check-list
Patrick
On Wed, Dec 28, 2011 at 11:08 AM, Arvind Prabhakar <ar...@apache.org> wrote:
> Also, the KEYS can be found at:
>
> https://svn.apache.org/repos/asf/incubator/flume/dist/KEYS
>
> On Wed, Dec 28, 2011 at 10:55 AM, Arvind Prabhakar <ar...@apache.org> wrote:
>> The link to the GPG signature seems to be corrupted. Here is the link
>> that works:
>>
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>>
>> Thanks,
>> Arvind
>>
>> On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com> wrote:
>>> All:
>>>
>>> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet ready for
>>> a vote as there's at least one maven issue left to be worked out and it's
>>> still a SNAPSHOT. That said, I would like feedback so we can knock out any
>>> remaining issues.
>>>
>>> tarball:
>>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
>>> GPG signature:
>>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>>> md5sum:
>>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
>>>
>>> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
>>> affectsVersion = v1.0.0 please).
>>>
>>> Thanks.
>>> --
>>> Eric Sammer
>>> twitter: esammer
>>> data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Arvind Prabhakar <ar...@apache.org>.
Also, the KEYS can be found at:
https://svn.apache.org/repos/asf/incubator/flume/dist/KEYS
On Wed, Dec 28, 2011 at 10:55 AM, Arvind Prabhakar <ar...@apache.org> wrote:
> The link to the GPG signature seems to be corrupted. Here is the link
> that works:
>
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>
> Thanks,
> Arvind
>
> On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com> wrote:
>> All:
>>
>> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet ready for
>> a vote as there's at least one maven issue left to be worked out and it's
>> still a SNAPSHOT. That said, I would like feedback so we can knock out any
>> remaining issues.
>>
>> tarball:
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
>> GPG signature:
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
>> md5sum:
>> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
>>
>> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
>> affectsVersion = v1.0.0 please).
>>
>> Thanks.
>> --
>> Eric Sammer
>> twitter: esammer
>> data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Arvind Prabhakar <ar...@apache.org>.
The link to the GPG signature seems to be corrupted. Here is the link
that works:
http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
Thanks,
Arvind
On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com> wrote:
> All:
>
> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet ready for
> a vote as there's at least one maven issue left to be worked out and it's
> still a SNAPSHOT. That said, I would like feedback so we can knock out any
> remaining issues.
>
> tarball:
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
> GPG signature:
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
> md5sum:
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
>
> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
> affectsVersion = v1.0.0 please).
>
> Thanks.
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
Re: Flume (NG) 1.0.0 rc1
Posted by Eric Sammer <es...@cloudera.com>.
Here's a filter for things required to knock out before the next RC. Please
help test / file / fix!
http://bit.ly/tFBDyW
Thanks.
On Tue, Dec 27, 2011 at 5:51 PM, Eric Sammer <es...@cloudera.com> wrote:
> All:
>
> I've cut an early RC of flume-1.0.0-incubating. This is *not* yet ready
> for a vote as there's at least one maven issue left to be worked out and
> it's still a SNAPSHOT. That said, I would like feedback so we can knock out
> any remaining issues.
>
> tarball:
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz
> GPG signature:
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.asc
> md5sum:
> http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc1.tar.gz.md5sum
>
> Place to file JIRAs: https://issues.apache.org/jira/browse/FLUME (use
> affectsVersion = v1.0.0 please).
>
> Thanks.
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
>
--
Eric Sammer
twitter: esammer
data: www.cloudera.com