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