A couple things came up on my side, let's get in the last commits soon and do the RC in the next 1-2 days.
Thanks, Mike On Jun 13, 2013, at 11:49 AM, Mike Percy <[email protected]> wrote: > Hi Roshan, sure, I'll commit it. > > Thanks! > Mike > > > > On Thu, Jun 13, 2013 at 11:13 AM, Roshan Naik <[email protected]> wrote: >> FYI... i am thinking of adding a blocker jira for removal of the deprecated >> 'Recoverable Memory Channel'. >> >> >> On Tue, Jun 11, 2013 at 5:33 PM, Mike Percy <[email protected]> wrote: >> >> > Hi everyone, >> > I'd like to cut an RC and start a Flume 1.4 vote on June 20th (9 days from >> > now). >> > >> > These are the currently resolved issues in Flume 1.4: >> > >> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20Status%20%3D%20Resolved%20ORDER%20BY%20created%20ASC >> > >> > These are the current JIRAs marked Patch Available with a fixVersion of >> > v1.4.0, plus anything marked as a Bug Blocker against v1.4.0: >> > >> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLUME%20AND%20fixVersion%20%3D%20%22v1.4.0%22%20AND%20((Status%20%3D%20%22Patch%20Available%22)%20OR%20(Resolution%20%3D%20Unresolved%20and%20Type%20%3D%20Bug%20AND%20Priority%20%3D%20Blocker))%20ORDER%20BY%20priority%20DESC%2C%20created%20ASC >> > >> > If you would like a JIRA to be considered for inclusion into Flume 1.4, >> > please mark it as fixVersion = v1.4.0 and mark it as Patch Available, or >> > set it to Type = Bug and Priority = Blocker if you really think it is a >> > critical bug that we cannot release without fixing. >> > >> > Let's crunch through these patches and come up with an RC next week. >> > >> > Thanks! >> > Mike >> > >
