Branching is done for Lens 2.6.0
Thanks, Puneet Gupta On Mon, Jul 25, 2016 at 3:48 PM, Rajat Khandelwal <[email protected]> wrote: > Let's also get https://issues.apache.org/jira/browse/LENS-1178 in the > release. > > On Fri, Jul 22, 2016 at 5:58 PM Puneet Gupta <[email protected]> > wrote: > > > Will start the merge once LENS-128, LENS-1168, LENS-996, LENS-1202, > > LENS-1217 are in . > > > > Thanks, > > Puneet Gupta > > On Wed, Jul 20, 2016 at 11:00 AM, Puneet Gupta <[email protected]> > > wrote: > > > > > Hi > > > > > > Waiting for a few important fixes to go in . Will merge master into > > > release branch post that ( targeting 22 July) > > > > > > Thanks, > > > Puneet Gupta > > > On Thu, Jul 7, 2016 at 5:56 PM, amareshwarisr . <[email protected] > > > > > wrote: > > > > > >> +1 > > >> > > >> Release plan looks great! > > >> > > >> On Sat, Jul 2, 2016 at 9:35 AM, Puneet Gupta < > [email protected]> > > >> wrote: > > >> > > >> > We have some significant improvements and features added after 2.5 > > >> > release, mainly : > > >> > > > >> > - Hive 2 support and move Hive dependency to Apache Hive > > >> > - Lens Regression module added > > >> > - Work on Lens Scheduler is 70% complete. > > >> > - Limit number of open sessions per user on session service > > >> > - Enable streaming results for queries > > >> > - cube-segmentation specification added > > >> > - Python client support > > >> > - Exponential back off for hive queries > > >> > - Client result set iterable api added > > >> > - Lens UI enhancements > > >> > - Query Priority persisted in Lens DB > > >> > - Option to kill queries that exceed timeout added > > >> > - Convert dimension filter to fact filters for performance > improvement > > >> > - Return same handle for repeated query from same user > > >> > - Post select option added to DriverQueryHook > > >> > - Skip partition registration for very old and future dates for a > fact > > >> > tables > > >> > - Weighted Driver selector added. > > >> > - Cube keyword made optional in queries > > >> > - Session close will not result in queued query failures > > >> > > > >> > and bug fixes. > > >> > > > >> > I'm volunteering to manage the release. Calling out for a release > > >> > preparation for 2.6 here. > > >> > *Unassigned open items on 2.6 are ( A total of 13 issues)* > > >> > > > >> > > > >> > > > >> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20fixVersion%20%3D%202.6%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20is%20EMPTY > > >> > > > >> > Contributors are welcome to provide fix for those issues. > > >> > > > >> > *All the open issues (A total of 30 issues including above mentioned > > >> > 13 unassigned issues)* > > >> > > > >> > > > >> > > > >> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.6 > > >> > > > >> > *Issues yet to verify (A total of 107 issues)* > > >> > > > >> > > > >> > > > >> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20fixVersion%20%3D%202.6%20AND%20status%20%3D%20Resolved > > >> > > > >> > If any of you feel your changes should go into 2.6 and the jira is > not > > >> > marked with fix version, please do so. > > >> > > > >> > Putting down the plan for 2.6 release: > > >> > - Will merge master into release branch after two weeks from now. > > >> > We can resolve the open issues until then. > > >> > (18/July/2016) > > >> > - We will spend one-two weeks to fix blockers on the release > branch > > >> > if any and verify release candidate and roll release candidates > until > > >> > a release vote passes(29/July/2016) > > >> > - Will roll release candidate on 3/Aug/2016 > > >> > > > >> > Let me know your concerns/comments. > > >> > > > >> > > > > > > > > > -- _____________________________________________________________ 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.
