From dev-return-29716-archive-asf-public=cust-asf.ponee.io@geode.apache.org Thu Sep 13 20:39:23 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1487D180649 for ; Thu, 13 Sep 2018 20:39:21 +0200 (CEST) Received: (qmail 2230 invoked by uid 500); 13 Sep 2018 18:39:21 -0000 Mailing-List: contact dev-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list dev@geode.apache.org Received: (qmail 2219 invoked by uid 99); 13 Sep 2018 18:39:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2018 18:39:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id DFE5C1A1445 for ; Thu, 13 Sep 2018 18:39:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id zJAWUCJTOGcb for ; Thu, 13 Sep 2018 18:39:14 +0000 (UTC) Received: from mx0a-00296801.pphosted.com (mx0a-00296801.pphosted.com [148.163.150.38]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id F2C115F3EE for ; Thu, 13 Sep 2018 18:39:13 +0000 (UTC) Received: from pps.filterd (m0114583.ppops.net [127.0.0.1]) by mx0a-00296801.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w8DIXASj018032 for ; Thu, 13 Sep 2018 18:39:12 GMT Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) by mx0a-00296801.pphosted.com with ESMTP id 2mc56k4mmr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 13 Sep 2018 18:39:11 +0000 Received: by mail-lf1-f71.google.com with SMTP id n79-v6so1992169lfi.20 for ; Thu, 13 Sep 2018 11:39:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=oeihYUj5FQllLuk0Ckl+RK7U71QIJvmVVHhi+yvTjt0=; b=p/f1/6zfEc/uBtqzDwbRtVtbNaszk2nd5p9cNyOPFjSTvN5vcwLR9YzmPJWuoyy4lF usLkous714qTSMip5n02WGUUqepi14NypKW5y8kQ+5blrZLUJ7Nk5eV/VgpTan/cvUYB eaVi4J7AekbmJ+60DH06Wz3CnaFQOAy/hwx3tWfUKwijv3eo0A+h/Ra0zxHs2MYQrUEE bXjXX1jHqbK69jwxzDwoO7tyr1AyVx/uqlq13lZ23Oq1p1Owb7n4Oh1IN8n6f2ZxII+U sAkwwSm0uOPC1mzv9Pf3+qmKhekXdyJqCzuTqLHI/GjPI3dx+Tm7VzcFvCtBIr827yVy 9fZw== X-Gm-Message-State: APzg51B04+Z0ESPZJTovO3jfdx2I2TL+/PyA+pCm0uWbM74m1mVdLJFx 311ZnICXmAnoSBnrtKPTSDB5XfxsPI++LtyqBBJEG1e1icvtimOT3jKiJNeEdiatzF+FkhjARbE 786coYBBCMSJMQqq7LOt+DfnkYe3ty+zNJR99ja3Wu0rCtVpqaaJnIV4= X-Received: by 2002:a19:18c:: with SMTP id 134-v6mr5699672lfb.16.1536863948547; Thu, 13 Sep 2018 11:39:08 -0700 (PDT) X-Google-Smtp-Source: ANB0VdY4CXFLlV0vlw6KxTGZtxlAkp2NyNgdWJQxk+8CTFLqgXQrQWb1j/HXJgH0w3wJ9b7lz2iZ8klCUMhkczsURAI= X-Received: by 2002:a19:18c:: with SMTP id 134-v6mr5699644lfb.16.1536863947964; Thu, 13 Sep 2018 11:39:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:6b06:0:0:0:0:0 with HTTP; Thu, 13 Sep 2018 11:39:07 -0700 (PDT) In-Reply-To: References: <62206EE0-064B-4AFC-B553-72E2F5F747D1@pivotal.io> <47A9B9B0-BCD7-4648-B6C8-DFD3D54F5801@pivotal.io> <3703F976-156D-4142-A3EF-830E8061C14C@pivotal.io> From: Patrick Rhomberg Date: Thu, 13 Sep 2018 11:39:07 -0700 Message-ID: Subject: Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created To: dev@geode.apache.org Content-Type: multipart/alternative; boundary="000000000000afdafd0575c50587" X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-09-13_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=3 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809130187 --000000000000afdafd0575c50587 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Revert of 5600 commits pushed to release/1.7.0. Built clean locally and `$> gfsh version --full` is behaving as expected. On Thu, Sep 13, 2018 at 9:49 AM, Nabarun Nag wrote: > GEODE-5727 is closed and merged to release/1.7.0 > Thank you Jinmei > > On Thu, Sep 13, 2018 at 9:47 AM Nabarun Nag wrote: > > > Thank you Patrick. Please do send a notification email once this is > > reverted in the release/1.7.0 branch. > > Thank you Jinmei for putting the fix for GEODE-5727 into release/1.7.0. > > However the GEODE ticket is still in open state. Can it be closed? > > > > Regards > > Nabarun Nag > > > > > > On Thu, Sep 13, 2018 at 9:21 AM Patrick Rhomberg > > wrote: > > > >> Sounds like we have a plan! I'll take it upon myself to do the revert= . > >> > >> On Thu, Sep 13, 2018 at 7:24 AM, Sai Boorlagadda < > >> sai.boorlagadda@gmail.com> > >> wrote: > >> > >> > +1 to revert and fix on develop > >> > > >> > On Wed, Sep 12, 2018, 4:43 PM Nabarun Nag wrote: > >> > > >> > > Reverting them on release/1.7.0 will bring it to the previous stat= us > >> quo, > >> > > how all previous releases were done. I don't think anyone will bui= ld > >> > > release/1.7.0 repeatedly, hence there is no advantage of making > build > >> > > process faster for that branch. > >> > > Whereas on develop a more appropriate solution can be incorporated > >> after > >> > > discussions. > >> > > > >> > > Is it acceptable? > >> > > > >> > > Regards > >> > > Nabarun Nag > >> > > > >> > > On Wed, Sep 12, 2018 at 4:37 PM Patrick Rhomberg < > >> prhomberg@pivotal.io> > >> > > wrote: > >> > > > >> > > > Okay. So that information is definitely coming from the > >> > > > GemFireVersion.properties file, which explains this issue. Eith= er > >> > > > reverting the previous GEODE-5600 changes or resolving merge > >> conflicts > >> > > from > >> > > > PR 2457 would address this issue. > >> > > > > >> > > > My concern remains about the .buildinfo file, however. Is the > >> > > .buildinfo > >> > > > redundant at this point and should be? Should it always contain > the > >> > > > necessary information, with the GemFireVersion.properties file > >> > acquiring > >> > > > the source information from .buildinfo rather than fetching it > again > >> > > > itself? Is .buildinfo a convention in distributions with which = I > am > >> > just > >> > > > myself unfamiliar? > >> > > > > >> > > > The path we take here is fundamentally linked to how we want to > >> > approach > >> > > > GEODE-5600, and with PR 2457 currently open, we could choose any > of > >> > these > >> > > > routes to go. > >> > > > > >> > > > On Wed, Sep 12, 2018 at 4:13 PM, Nabarun Nag > >> wrote: > >> > > > > >> > > > > @patrick > >> > > > > if you build geode release branch 1.7.0 "./gradlew clean build > >> > > > > -Dskip.tests=3Dtrue -xdocs -xjavadoc" and start gfsh from > >> > > > > geode-assembly/build/install/apache-geode/bin/gfsh > >> > > > > And then type `version --full` you get this > >> > > > > > >> > > > > gfsh>version --full > >> > > > > Build-Date: 2018-09-12 16:07:03 -0700 > >> > > > > Build-Id: nnag 0 > >> > > > > Build-Java-Version: 1.8.0_181 > >> > > > > Build-Platform: Mac OS X 10.13.6 x86_64 > >> > > > > Product-Name: Apache Geode > >> > > > > Product-Version: 1.7.0 > >> > > > > Source-Date: 2018-09-12 16:07:03 -0700 > >> > > > > *Source-Repository: unknown* > >> > > > > *Source-Revision: unknown* > >> > > > > Native version: native code unavailable > >> > > > > Running on: /10.118.19.23, 8 cpu(s), x86_64 Mac OS X 10.13.6 > >> > > > > > >> > > > > As you can notice that Source-Repository and Source-Revision i= s > >> > > missing. > >> > > > It > >> > > > > should contain the info from the buildinfo file present in > >> > > > > geode-assemble/.buildinfo file. It contains the following > >> > > > > > >> > > > > # > >> > > > > #Wed Sep 12 16:07:56 PDT 2018 > >> > > > > Source-Date=3D2018-09-11 15\:56\:48 -0700 > >> > > > > Source-Revision=3Dc637193aa61abdfd236ae36b6d9a228fc1e84bcd > >> > > > > Source-Repository=3Drelease/1.7.0 > >> > > > > > >> > > > > Hope this helps > >> > > > > > >> > > > > Regards > >> > > > > Nabarun Nag > >> > > > > > >> > > > > On Wed, Sep 12, 2018 at 3:51 PM Patrick Rhomberg < > >> > prhomberg@pivotal.io > >> > > > > >> > > > > wrote: > >> > > > > > >> > > > > > I'm happy to work on those reverts, although if Anthony coul= d > >> > > elaborate > >> > > > > on > >> > > > > > where exactly the version information was missing, that > assuage > >> > some > >> > > of > >> > > > > my > >> > > > > > own worries as to whether it's the right approach. It's sti= ll > >> not > >> > > > clear > >> > > > > to > >> > > > > > me where .buildinfo is intended to be consumed. > >> > > > > > > >> > > > > > On Wed, Sep 12, 2018 at 3:08 PM, Nabarun Nag > > >> > > wrote: > >> > > > > > > >> > > > > > > Yes Alexander, we are still waiting on the build info > reverts > >> > from > >> > > > > > Patrick, > >> > > > > > > so, I think that this can be put into release/1.7.0. > >> > > > > > > > >> > > > > > > Sure Jinmei, you can go ahead and merge the change into > >> > > release/1.7.0 > >> > > > > > > branch too when you merge the PR. Please do close the fixe= d > >> > version > >> > > > in > >> > > > > > the > >> > > > > > > JIRA as 1.7.0 > >> > > > > > > > >> > > > > > > Regards > >> > > > > > > Nabarun Nag > >> > > > > > > > >> > > > > > > > >> > > > > > > On Wed, Sep 12, 2018 at 2:50 PM Alexander Murmann < > >> > > > amurmann@pivotal.io > >> > > > > > > >> > > > > > > wrote: > >> > > > > > > > >> > > > > > > > While there is a workaround this looks like a highly > visible > >> > bug > >> > > > > with a > >> > > > > > > > fairly safe fix. I am in favor of merging, since the > branch > >> is > >> > > > still > >> > > > > > > > distressed anyways. > >> > > > > > > > > >> > > > > > > > Other opinions? > >> > > > > > > > > >> > > > > > > > On Wed, Sep 12, 2018 at 2:29 PM, Jinmei Liao < > >> > jiliao@pivotal.io> > >> > > > > > wrote: > >> > > > > > > > > >> > > > > > > > > Should we include the fix for GEODE-5727 in the 1.7 > >> release > >> > as > >> > > > > well? > >> > > > > > > > > > >> > > > > > > > > Without the fix, the command "export cluster-config > >> > > > > > > > --zip-file-name=3Dx.zip" > >> > > > > > > > > would fail with NPE, user has to use "export > >> cluster-config > >> > > > > > > > > --zip-file-name=3D./x.zip" in order for export to work= . > >> > > > > > > > > > >> > > > > > > > > PR for this fix is ready and could be merged soon. > >> > > > > > > > > > >> > > > > > > > > Jinmei > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > On Wed, Sep 12, 2018 at 11:12 AM Patrick Rhomberg < > >> > > > > > > prhomberg@apache.org> > >> > > > > > > > > wrote: > >> > > > > > > > > > >> > > > > > > > > > I'm not sure PR 2457 will help with an ignored > >> .buildinfo, > >> > > but > >> > > > > I'm > >> > > > > > > not > >> > > > > > > > > sure > >> > > > > > > > > > as to why .buildinfo would be getting ignored by > >> anything, > >> > > > > either. > >> > > > > > > > > > > >> > > > > > > > > > PR 2457 deals with the still-needs-to-be-renamed > >> > > > > > > > > GemFireVersion.properties > >> > > > > > > > > > file and when it is generated. Previously, it was > >> whenever > >> > > the > >> > > > > git > >> > > > > > > > index > >> > > > > > > > > > changed, which was too frequent. Not it is whenever > the > >> > > source > >> > > > > > > > > parameters > >> > > > > > > > > > are passed on the command-line with the build, which > has > >> > > > > presented > >> > > > > > > > issues > >> > > > > > > > > > outside the Concourse pipeline. PR 2457 splits the > >> > > difference, > >> > > > > > > > > > regenerating the file anytime the SHA changes. > >> > > > > > > > > > > >> > > > > > > > > > The only interaction with .buildinfo that I can see = is > >> that > >> > > if > >> > > > > the > >> > > > > > > > build > >> > > > > > > > > > was run on a machine that was missing git, it would > >> attempt > >> > > to > >> > > > > read > >> > > > > > > > > values > >> > > > > > > > > > instead from .buildinfo when creating the > >> > > > > GemFireVersion.properties > >> > > > > > > > file. > >> > > > > > > > > > > >> > > > > > > > > > I guess I don't fully understand the problem Anthony > has > >> > > called > >> > > > > > out. > >> > > > > > > > > Where > >> > > > > > > > > > is it exactly that information previously gathered > from > >> > > > > .buildinfo > >> > > > > > is > >> > > > > > > > now > >> > > > > > > > > > missing? And are we certain that it was indeed > pulling > >> > from > >> > > > > > > .buildinfo > >> > > > > > > > > and > >> > > > > > > > > > not the aforementioned GemFireVersion.properties? > >> > > > > > > > > > > >> > > > > > > > > > On Wed, Sep 12, 2018 at 10:11 AM, Alexander Murmann = < > >> > > > > > > > amurmann@pivotal.io > >> > > > > > > > > > > >> > > > > > > > > > wrote: > >> > > > > > > > > > > >> > > > > > > > > > > Hi everyone, > >> > > > > > > > > > > > >> > > > > > > > > > > It seems like that PR doesn't address the missing > SHA > >> > issue > >> > > > > > either > >> > > > > > > > and > >> > > > > > > > > I > >> > > > > > > > > > am > >> > > > > > > > > > > not aware of any proposals to properly fix this. H= ow > >> > viable > >> > > > is > >> > > > > it > >> > > > > > > to > >> > > > > > > > > > revert > >> > > > > > > > > > > the relevant Gradle build changes on support/1.7? > >> > > > > > > > > > > We could continue make the new Gradle approach wor= k > >> with > >> > > our > >> > > > > > > release > >> > > > > > > > > > > process on develop and hopefully release 1.8 with > >> these > >> > > > > changes. > >> > > > > > > > > > > > >> > > > > > > > > > > Are there any other proposals to unblock this? > >> > > > > > > > > > > > >> > > > > > > > > > > On Tue, Sep 11, 2018 at 5:41 PM, Anthony Baker < > >> > > > > > abaker@pivotal.io> > >> > > > > > > > > > wrote: > >> > > > > > > > > > > > >> > > > > > > > > > > > Slight clarification=E2=80=94the issue I mention= ed is > when a > >> > user > >> > > > > > builds > >> > > > > > > > > Geode > >> > > > > > > > > > > > from the source distribution. The source > >> distribution > >> > > that > >> > > > > the > >> > > > > > > > > release > >> > > > > > > > > > > > manager creates has the correct .buildinfo file, > >> it=E2=80=99s > >> > > just > >> > > > > > > ignored > >> > > > > > > > by > >> > > > > > > > > > the > >> > > > > > > > > > > > build. In short, the release manager can=E2=80= =99t work > >> around > >> > > the > >> > > > > > > > problem. > >> > > > > > > > > > > > > >> > > > > > > > > > > > Does [1] help with this? > >> > > > > > > > > > > > > >> > > > > > > > > > > > Anthony > >> > > > > > > > > > > > > >> > > > > > > > > > > > [1] https://github.com/apache/geode/pull/2457 < > >> > > > > > > > > > > https://github.com/apache/ > >> > > > > > > > > > > > geode/pull/2457> > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > On Sep 11, 2018, at 3:16 PM, Alexander Murmann= < > >> > > > > > > > > amurmann@pivotal.io> > >> > > > > > > > > > > > wrote: > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > What's the consensus on the version info issue > >> > Anthony > >> > > is > >> > > > > > > calling > >> > > > > > > > > > out? > >> > > > > > > > > > > > Does > >> > > > > > > > > > > > > anyone have a proposal for fixing this for thi= s > >> > > release? > >> > > > > > Should > >> > > > > > > > > > Nabarun > >> > > > > > > > > > > > as > >> > > > > > > > > > > > > the release manager manually correct this for > the > >> > > release > >> > > > > and > >> > > > > > > we > >> > > > > > > > > > find a > >> > > > > > > > > > > > > permanent solution for 1.8? > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > On Mon, Sep 10, 2018 at 12:33 PM, Anthony Bake= r > < > >> > > > > > > > abaker@pivotal.io > >> > > > > > > > > > > >> > > > > > > > > > > > wrote: > >> > > > > > > > > > > > > > >> > > > > > > > > > > > >> Unfortunately it would require a fix to the > >> > build=E2=80=94it=E2=80=99s > >> > > > not > >> > > > > > > about > >> > > > > > > > > > > > producing > >> > > > > > > > > > > > >> the release candidate. It=E2=80=99s when a us= er builds > >> from > >> > > the > >> > > > > > source > >> > > > > > > > > > release > >> > > > > > > > > > > > that > >> > > > > > > > > > > > >> the version info is ignored. > >> > > > > > > > > > > > >> > >> > > > > > > > > > > > >> Anthony > >> > > > > > > > > > > > >> > >> > > > > > > > > > > > >>> On Sep 10, 2018, at 10:02 AM, Nabarun Nag < > >> > > > > nnag@apache.org > >> > > > > > > > >> > > > > > > > > wrote: > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> Hello Anthony, > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> I plan to do that while creating the release > >> > > candidate. > >> > > > > If > >> > > > > > > > there > >> > > > > > > > > > are > >> > > > > > > > > > > no > >> > > > > > > > > > > > >>> concerns raised on the release branch, I wil= l > >> start > >> > > > with > >> > > > > > the > >> > > > > > > > > > process > >> > > > > > > > > > > > >> soon. > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> Regards > >> > > > > > > > > > > > >>> Nabarun Nag > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>>> On Mon, Sep 10, 2018 at 8:51 AM Anthony > Baker < > >> > > > > > > > > abaker@pivotal.io> > >> > > > > > > > > > > > >> wrote: > >> > > > > > > > > > > > >>>> > >> > > > > > > > > > > > >>>> Looks good Naba! Only thing I see right no= w > is > >> > that > >> > > > > > > building > >> > > > > > > > > from > >> > > > > > > > > > > the > >> > > > > > > > > > > > >>>> source distribution does not use the > .buildinfo > >> > > file, > >> > > > > > > leaving > >> > > > > > > > > the > >> > > > > > > > > > > > >> version > >> > > > > > > > > > > > >>>> string empty. > >> > > > > > > > > > > > >>>> > >> > > > > > > > > > > > >>>> Anthony > >> > > > > > > > > > > > >>>> > >> > > > > > > > > > > > >>>> > >> > > > > > > > > > > > >>>>> On Sep 7, 2018, at 9:15 AM, Nabarun Nag < > >> > > > > nnag@apache.org > >> > > > > > > > >> > > > > > > > > wrote: > >> > > > > > > > > > > > >>>>> > >> > > > > > > > > > > > >>>>> CORRECTION: if '*no*' concerns are raised, > we > >> > will > >> > > > > start > >> > > > > > > with > >> > > > > > > > > the > >> > > > > > > > > > > > >> voting > >> > > > > > > > > > > > >>>>> for the release candidate soon. > >> > > > > > > > > > > > >>>>> > >> > > > > > > > > > > > >>>>> Regrads > >> > > > > > > > > > > > >>>>> Nabarun Nag > >> > > > > > > > > > > > >>>>> > >> > > > > > > > > > > > >>>>>> On Fri, Sep 7, 2018 at 9:08 AM Nabarun Na= g > < > >> > > > > > > nnag@pivotal.io > >> > > > > > > > > > >> > > > > > > > > > > wrote: > >> > > > > > > > > > > > >>>>>> > >> > > > > > > > > > > > >>>>>> Hello Geode Dev Community, > >> > > > > > > > > > > > >>>>>> > >> > > > > > > > > > > > >>>>>> We have created a new release branch for > >> Apache > >> > > > Geode > >> > > > > > > 1.7.0 > >> > > > > > > > - > >> > > > > > > > > > > > >>>>>> "release/1.7.0" > >> > > > > > > > > > > > >>>>>> > >> > > > > > > > > > > > >>>>>> Previous branch was deleted and has been > >> > replaced > >> > > > > with a > >> > > > > > > > fresh > >> > > > > > > > > > > one. > >> > > > > > > > > > > > >>>>>> > >> > > > > > > > > > > > >>>>>> Please do review and raise any concern wi= th > >> the > >> > > > > release > >> > > > > > > > > branch. > >> > > > > > > > > > > > >>>>>> > >> > > > > > > > > > > > >>>>>> If concerns are raised, we will start wit= h > >> the > >> > > > voting > >> > > > > > for > >> > > > > > > > the > >> > > > > > > > > > > > release > >> > > > > > > > > > > > >>>>>> candidate soon. > >> > > > > > > > > > > > >>>>>> > >> > > > > > > > > > > > >>>>>> Regards > >> > > > > > > > > > > > >>>>>> Nabarun Nag > >> > > > > > > > > > > > >>>>>> > >> > > > > > > > > > > > >>>> > >> > > > > > > > > > > > >>>> -- > >> > > > > > > > > > > > >>> Regards > >> > > > > > > > > > > > >>> Nabarun Nag > >> > > > > > > > > > > > >> > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > -- > >> > > > > > > > > Cheers > >> > > > > > > > > > >> > > > > > > > > Jinmei > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > -- > >> > > > > > > Regards > >> > > > > > > Nabarun Nag > >> > > > > > > > >> > > > > > > >> > > > > -- > >> > > > > Regards > >> > > > > Nabarun Nag > >> > > > > > >> > > > > >> > > -- > >> > > Regards > >> > > Nabarun Nag > >> > > > >> > > >> > > > --000000000000afdafd0575c50587--