Thanks for taking this up Mike. I agree it is about time we cut the next release.
+1 on Mike being the RM for 1.2.0. My wish list: * Fix File Channel Issues * Get configuration changes in to support external tooling * Finalize and fix the hot-reconfiguration mechanism being discussed on the other thread One suggestion and a personal preference - it would be good to set a timeline for the release so that we don't get carried away trying to incorporate changes and fixes. Regards, Arvind Prabhakar On Wed, Jun 13, 2012 at 12:57 AM, Mike Percy <[email protected]> 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 > > >
