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. > > >> > > > > > > > > >
