+1 On Fri, Sep 23, 2016 at 10:17 PM, Sergio Pena <sergio.p...@cloudera.com> wrote:
> Cool. > > I will start investigating these failures. > > On Fri, Sep 23, 2016 at 10:40 AM, Jesus Camacho Rodriguez < > jcamachorodrig...@hortonworks.com> wrote: > > > Thanks Sergio. > > > > Since only bug fixes were going in, I would expect that most failures > > are just a matter of regenerating q files. But certainly, we should > > make sure all tests are passing. > > > > -- > > Jesús > > > > > > > > On 9/23/16, 4:23 PM, "Sergio Pena" <sergio.p...@cloudera.com> wrote: > > > > >Thanks Jesus. > > >+1 > > > > > >I will take a look at some jiras useful for it. > > > > > >Btw, many tests are failing on branch-2.1. > > >Are we going to fix them before the release? > > > > > >On Thu, Sep 22, 2016 at 12:56 PM, Prasanth Jayachandran < > > >pjayachand...@hortonworks.com> wrote: > > > > > >> +1 > > >> > > >> Thanks > > >> Prasanth > > >> > > >> > On Sep 22, 2016, at 5:57 AM, Jesus Camacho Rodriguez > > <jcamachorodriguez@ > > >> hortonworks.com> wrote: > > >> > > > >> > Hi team, > > >> > > > >> > Since the release of 2.1.0, there have been more than 170 fixes > > >> > that went into branch-2.1 (awesome!). Thus, I think it is a good > > >> > time to release 2.1.1. > > >> > > > >> > If you would like some other fixes to be included, please tag > > >> > their target version as 2.1.1 so we do not miss them. > > >> > > > >> > If there are no objections, I propose to create an RC next week. > > >> > > > >> > Thanks, > > >> > Jesús > > >> > > > >> > > >> > > > -- Rajat Khandelwal Software Engineer -- _____________________________________________________________ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
