+1 for Mike as Release Manager +1 for 1.2.0 +1 for timeline. I agree that we must wither fix the Hadoop dependencies or make sure we end up in a known state and not where the agent just hangs.
Thanks Hari -- Hari Shreedharan On Thursday, June 14, 2012 at 12:32 AM, Ralph Goers wrote: > What I would like to see included: > > 1. Be able to build Flume. (Unfortunately, I'll have to vote -1 if tI can't > do this as it is a pre-requisite for a release). I've reopened FLUME-1256 and > attached my build output and machine information. > > Am I the only one with a Mac running Lion? > > Ralph > > On Jun 13, 2012, at 12:57 AM, Mike Percy wrote: > > > Developers, > > It has been nearly 3 months since we released Flume 1.1.0. Since the 1.1.0 > > release, we have had 117 commits to the trunk, and 114 JIRAs have been > > marked "Resolved Fixed" with a target of v1.2.0. This flurry of activity > > represents a whole slew of new features and a bunch of bug fixes. > > > > Because of the above, I think we should release a Flume 1.2.0 to the world > > within 2-3 weeks. I propose that I be the release manager for this release. > > To that end, I would like to cut an SVN branch pretty soon to stabilize and > > test the code in advance of the release. > > > > In addition, I'd like to gather input on what other devs would like to see > > included in a 1.2.0 release. > > > > Aside from a few JIRAs already marked as Patch Available, the one thing I'd > > really like to make happen is a once-over on the user guide to cover the > > latest features. I'm willing to help. > > > > Regards, > > Mike > > > > >
