Now that all issues are resolved. I'm going ahead with tagging and pushing to dist. Will send vote mail once ready.
Thanks Amareshwari On Thu, Feb 19, 2015 at 10:27 AM, Jaideep Dhok <[email protected]> wrote: > Will put up ML doc patch by EOD. > > Thanks, > Jaideep > > On Thu, Feb 19, 2015 at 10:26 AM, amareshwarisr . <[email protected]> > wrote: > >> Thanks Sharad. >> >> Merged LENS-212, LENS-319 and LENS-326 into current-release-line. >> >> On Thu, Feb 19, 2015 at 9:16 AM, Sharad Agarwal <[email protected]> >> wrote: >> >>> Provided the patch for Lens-326. >>> Can we pull in Lens-212 and Lens-319 into 2.0 release branch too? These >>> are committed into master and are quite standalone changes. >>> >>> On Thu, Feb 19, 2015 at 7:57 AM, Sharad Agarwal <[email protected]> >>> wrote: >>> >>>> I will provide the patch for docker issue shortly. >>>> On Feb 19, 2015 5:08 AM, "amareshwarisr ." <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Now that almost all release issues are done, we have >>>>> >>>>> LENS-202 <https://issues.apache.org/jira/browse/LENS-202> >>>>> >>>>> Create documentation for lens-ml component >>>>> <https://issues.apache.org/jira/browse/LENS-202> >>>>> >>>>> LENS-326 <https://issues.apache.org/jira/browse/LENS-326> >>>>> >>>>> Docker is failing after Lens-220 >>>>> <https://issues.apache.org/jira/browse/LENS-326> >>>>> still open for 2.0. Will wait for the patches for them today. >>>>> >>>>> Updated >>>>> https://builds.apache.org/view/H-L/view/Lens/job/Lens-current-release-line/ >>>>> to run with apache-release profile. So, I request you to try out source >>>>> and >>>>> binary tarballs from workspace of jenkins job and provide feedback, if >>>>> any. >>>>> >>>>> On the verification of issues fixed in release, Arshad Matin has been >>>>> verifying resolved issues and closing. But he could not verify docker >>>>> setup, if someone can verify docker setup on current-release-line and >>>>> close >>>>> LENS-12, LENS-146 and LENS-326, that would be really great. >>>>> >>>>> If all is well, I will start the release vote tomorrow. >>>>> >>>>> Thanks >>>>> Amareshwari >>>>> >>>>> On Mon, Feb 9, 2015 at 10:21 AM, amareshwarisr . < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> We have still 13 issues open which are marked for 2.0 - out of which >>>>>> 6 of them are release tasks related to license, notice and release >>>>>> distributions, one is a blocker and other are documentation >>>>>> bugs/improvements. >>>>>> >>>>>> Seems we are not ready for rolling the candidate today. Will roll as >>>>>> soon as we have the issues fixed. Will mail here once we are ready. >>>>>> >>>>>> Thanks, >>>>>> Amareshwari >>>>>> >>>>>> On Mon, Feb 2, 2015 at 10:54 PM, amareshwarisr . < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hello all, >>>>>>> >>>>>>> I created the branch current-release-line as the release branch. >>>>>>> Created jenkins job >>>>>>> https://builds.apache.org/view/H-L/view/Lens/job/Lens-current-release-line >>>>>>> for tracking tests in release branch and we will use the same build for >>>>>>> verifying issues. Moved the version on master to >>>>>>> 2.1.0-incubating-SNAPSHOT. >>>>>>> >>>>>>> The issues still marked for 2.0 are >>>>>>> >>>>>>> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.0%20AND%20project%20%3D%20LENS%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC >>>>>>> - Mainly release tasks and some documentation bugs. >>>>>>> >>>>>>> Thanks >>>>>>> Amareshwari >>>>>>> >>>>>>> On Mon, Feb 2, 2015 at 2:55 PM, amareshwarisr . < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Will merge master into release branch EOD today - mostly including >>>>>>>> LENS-262. >>>>>>>> >>>>>>>> Thanks >>>>>>>> Amareshwari >>>>>>>> >>>>>>>> On Tue, Jan 27, 2015 at 9:14 AM, amareshwarisr . < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> Would like to get few important issues before we branch - >>>>>>>>> LENS-236, LENS-58 and LENS-24. So, proposing a change in dates : >>>>>>>>> >>>>>>>>> * Pushing to release branch - 2nd Feb >>>>>>>>> * Rolling release candidate - 7th Feb >>>>>>>>> >>>>>>>>> Let me know if change is ok. >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> Amareshwari >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Jan 23, 2015 at 10:54 AM, amareshwarisr . < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Gentle reminder for all contributors. Will merge master into >>>>>>>>>> release branch on 28/01/2015. If we want a feature or >>>>>>>>>> improvement you are working on to go in 2.0, should be committed by >>>>>>>>>> 28/01/05. After 28/01/05 only critical/blocker bug fixes, >>>>>>>>>> documentation fixes can be merged to strengthen the release. >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> Amareshwari >>>>>>>>>> >>>>>>>>>> On Wed, Jan 14, 2015 at 4:44 PM, Jean-Baptiste Onofré < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> +1 >>>>>>>>>>> >>>>>>>>>>> Regards >>>>>>>>>>> JB >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 01/14/2015 11:48 AM, Srikanth Sundarrajan wrote: >>>>>>>>>>> >>>>>>>>>>>> +1 for the release. >>>>>>>>>>>> >>>>>>>>>>>> Date: Wed, 14 Jan 2015 11:00:27 +0530 >>>>>>>>>>>>> Subject: Re: [DISCUSS]2.0 release plan >>>>>>>>>>>>> From: [email protected] >>>>>>>>>>>>> To: [email protected] >>>>>>>>>>>>> >>>>>>>>>>>>> +1 for making the first apache lens release. >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Jan 14, 2015 at 10:47 AM, amareshwarisr . < >>>>>>>>>>>>> [email protected]> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Volunteers are welcome for picking up unassigned issues >>>>>>>>>>>>>> marked for 2.0 >>>>>>>>>>>>>> release - >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20% >>>>>>>>>>>>>> 3D%20LENS%20AND%20resolution%20%3D%20Unresolved%20AND% >>>>>>>>>>>>>> 20fixVersion%20%3D%202.0%20AND%20assignee%20in%20(EMPTY) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Jan 14, 2015 at 10:33 AM, amareshwarisr . < >>>>>>>>>>>>>> [email protected]> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> If issues marked for 2.0 are not resolved by suggested date, >>>>>>>>>>>>>>> they will be >>>>>>>>>>>>>>> moved to next release unless they are blockers. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>> Amareshwari >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Jan 14, 2015 at 10:24 AM, amareshwarisr . < >>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hello Lens contributors, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thinking about the first release after incubating into >>>>>>>>>>>>>>>> apache, I >>>>>>>>>>>>>>>> volunteer for managing release 2.0. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Here are all the issues marked for release - >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=fixVersion% >>>>>>>>>>>>>> 20%3D%202.0%20AND%20project%20%3D%20LENS >>>>>>>>>>>>>> >>>>>>>>>>>>>>> . >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Issues still open - >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20% >>>>>>>>>>>>>> 3D%20LENS%20AND%20resolution%20%3D%20Unresolved%20AND% >>>>>>>>>>>>>> 20fixVersion%20%3D%202.0 >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Issues yet to verify - >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20% >>>>>>>>>>>>>> 3D%20LENS%20AND%20status%20%3D%20Resolved%20AND% >>>>>>>>>>>>>> 20fixVersion%20%3D%202.0 >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> - Once the issue is verified, the issue will be CLOSED >>>>>>>>>>>>>>>> and regression >>>>>>>>>>>>>>>> added to regression suite. We don't have regression >>>>>>>>>>>>>>>> suite available >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> in code >>>>>>>>>>>>>> >>>>>>>>>>>>>>> base yet. Arshad and Raghavendra from Inmobi volunteered >>>>>>>>>>>>>>>> to put this >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> up. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If any of you feel your changes should go into 2.0 and the >>>>>>>>>>>>>>>> jira is not >>>>>>>>>>>>>>>> marked with fix version, please do so. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Putting down the plan for 2.0 release: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> - Will merge master into release branch after two weeks >>>>>>>>>>>>>>>> from now. >>>>>>>>>>>>>>>> (28/01/2015) >>>>>>>>>>>>>>>> - We will spend one week to fix blockers on the release >>>>>>>>>>>>>>>> branch if any >>>>>>>>>>>>>>>> and verify release candidate. And roll release >>>>>>>>>>>>>>>> candidates until a >>>>>>>>>>>>>>>> release vote passes(04/02/2015) >>>>>>>>>>>>>>>> - Will roll release candidate on 05/02/2015 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Let me know your concerns/comments regarding the process or >>>>>>>>>>>>>>>> dates >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>>> Amareshwari >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>> [email protected] >>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>> Talend - http://www.talend.com >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>> >> > > > -- > - > 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.
