Mike, instead of asking what needs to be fixed I would suggest that Jira issues should be marked as blockers. Then those are dealt with in one of two ways; fix the issue or get agreement to move it to he next release.
In general, asking what needs to be done before a release on an active project will simply delay you into never getting a release out. Ralph On 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 > >
