Can we close all the issue by 19th(fri) if possible instead of 22nd? On Tue, Jun 16, 2015 at 11:19 AM, Jean-Baptiste Onofré <[email protected]> wrote:
> Hi, > > thanks for the update. > > Regards > JB > > > On 06/16/2015 07:43 AM, amareshwarisr . wrote: > >> Hi all, >> >> I moved some of the issues which are not actively worked upon from 2.2. >> >> Here are all the open issues on 2.2 (13 issues) - >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20fixVersion%20%3D%202.2%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC >> >> >> Thanks >> Amareshwari >> >> >> On Mon, Jun 8, 2015 at 7:22 PM, Raghavendra Singh < >> [email protected]> wrote: >> >> Hi All, >>> I would like to pick up following issues if no one is planning to work on >>> them. >>> >>> https://issues.apache.org/jira/browse/LENS-540 >>> https://issues.apache.org/jira/browse/LENS-536 >>> >>> They are minor pom fixes, and I will soon update the tickets with my >>> approach. >>> >>> Thanks, >>> Raghavendra Singh >>> >>> On Mon, Jun 8, 2015 at 7:07 PM, Yash Sharma <[email protected]> wrote: >>> >>> Hi All, >>>> I would like to pick the tracker issue [1] if no one is working on it. I >>>> have updated the issue with my thoughts. >>>> Let me know what everyone thinks and I can start working on the points. >>>> >>>> Best Regards >>>> >>>> 1. https://issues.apache.org/jira/browse/LENS-539 >>>> >>>> On Mon, Jun 8, 2015 at 3:21 PM, amareshwarisr . <[email protected]> >>>> wrote: >>>> >>>> +1 looks fine to me. >>>>> >>>>> Regarding issues mentioned by Justin in last release - the tracking >>>>> >>>> jiras >>> >>>> are opened and marked for 2.2, but none of them are fixed though. We >>>>> >>>> should >>>> >>>>> fix them for the release. >>>>> >>>>> Pranav Kumar Agarwal, I think Zeppelin interpreter for Lens requires >>>>> >>>> Lens >>> >>>> release. Please mark all jiras required (if any) for 2.2. >>>>> >>>>> Thanks >>>>> Amareshwari >>>>> >>>>> On Mon, Jun 8, 2015 at 3:11 PM, Yash Sharma <[email protected]> wrote: >>>>> >>>>> Also we can check if we are good on the points mentioned by Justin in >>>>>> >>>>> last >>>>> >>>>>> release vote - http://goo.gl/RqwgIj >>>>>> >>>>>> Best regards >>>>>> >>>>>> On Mon, Jun 8, 2015 at 3:11 PM, Yash Sharma <[email protected]> >>>>>> >>>>> wrote: >>> >>>> >>>>>> +1. >>>>>>> >>>>>>> Best Regards >>>>>>> >>>>>>> >>>>>>> On Mon, Jun 8, 2015 at 2:49 PM, Jaideep Dhok < >>>>>>> >>>>>> [email protected]> >>>> >>>>> wrote: >>>>>>> >>>>>>> Hi Lens-dev, >>>>>>>> >>>>>>>> I will be volunteering for our next release. Tentative release >>>>>>>> >>>>>>> dates >>> >>>> are >>>>> >>>>>> as >>>>>>>> follows - >>>>>>>> >>>>>>>> 22 June 15 - Feature freeze and making release branch. >>>>>>>> 29 June 15 or July 6 - Release verification complete >>>>>>>> July 6 or July 13 - roll out release candidates >>>>>>>> >>>>>>>> Please get back if you have any concerns with the date. I will >>>>>>>> >>>>>>> send >>> >>>> out >>>>> >>>>>> a >>>>>> >>>>>>> follow up email about the various JIRA lists. >>>>>>>> >>>>>>>> Meanwhile, if you wish your patch to go in 2.2 release, please >>>>>>>> >>>>>>> mark >>> >>>> it >>>> >>>>> with >>>>>>>> 2.2 version. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Jaideep Dhok >>>>>>>> >>>>>>>> -- >>>>>>>> _____________________________________________________________ >>>>>>>> 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. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> -- >>> _____________________________________________________________ >>> 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. >>> >>> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- _____________________________________________________________ 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.
