From dev-return-3857-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Tue Aug 7 20:30:01 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 C418D180657 for ; Tue, 7 Aug 2018 20:30:00 +0200 (CEST) Received: (qmail 65486 invoked by uid 500); 7 Aug 2018 18:29:59 -0000 Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mxnet.incubator.apache.org Delivered-To: mailing list dev@mxnet.incubator.apache.org Received: (qmail 65468 invoked by uid 99); 7 Aug 2018 18:29:59 -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; Tue, 07 Aug 2018 18:29:59 +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 A8BDD1A2C59 for ; Tue, 7 Aug 2018 18:29:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.389 X-Spam-Level: ** X-Spam-Status: No, score=2.389 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ujjYMNv3H63f for ; Tue, 7 Aug 2018 18:29:55 +0000 (UTC) Received: from mail-pg1-f180.google.com (mail-pg1-f180.google.com [209.85.215.180]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id AE1AA5F24A for ; Tue, 7 Aug 2018 18:29:54 +0000 (UTC) Received: by mail-pg1-f180.google.com with SMTP id x5-v6so8231489pgp.7 for ; Tue, 07 Aug 2018 11:29:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=r3zpKJ/Lmr/YGFW7lHVOdkQDqN+U1LVySg9/NyI0sFk=; b=Y/auc82liDd10unAEQJ/8Ewuo2H11eiWwexP2FwX3fHgSohPK4w4E/wxtjc7+lc5Im k0owM2huf9ToBgBsJHVr/0kxKI2vKHPwON6k0bURds6eDF55QxMyqRDu5LAf8nDutVZ3 K+1ykKRLh0JsaroZa6/eHFV3qi6U1G9TnPcsIzSVhkrCO68sA481al36XYsqNajAtW1S Z/u5VAx7+8bJqUxztgNWNXNVpHZp788s1YMfHXNFPDFv+jck3RVFOMX8sYf0cW2CvdlI WO6WLDtmoSMD1dIkSQU5AEdL4Vb3CpRShnkn3AGXkMQfTUHciFB6/dbqM9g+EdjbYOJM dq0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=r3zpKJ/Lmr/YGFW7lHVOdkQDqN+U1LVySg9/NyI0sFk=; b=YF5z+mEM76mxEMtt1+8jAUBZmuadKG7+NgigHyGEucNyghO//GTHO8XN93BDUXm+et 93Grr5OSxdSgQdSG3829Ku/C8c8GcwkyYUe6lCcxrfw3GLP4XEDdmT4uNBMu2nvq3471 93OOVF5jFI7rZzQfibvS5lzfAsaaWLfWqrZHEXFg2MS9bKNEEfO4ji4BDI+SxDGuPUsl l4QZ5G+gZxJepnDYRRPI/8TmqVwd/jgoIswSRwcHuWwDQP73OZBbxB8folEu05dWrU2q +bktzCBYAu0HazXXU+pP6hDYUr3xIZ8pUEeIicdLysmIj5mi2IpzGNGpPxefn7hPz/++ SPig== X-Gm-Message-State: AOUpUlFOi1zvRyVxMILZnrTUgDQWrtq6zrccAjnPKD2N+UbCDY6GZfHA wYM0uo0+Mg4d4G1ympCvCgM/kpWO X-Google-Smtp-Source: AAOMgpe2zf2q0izCFomWuqoYnkESvMIgXf+AipylJC/ud+DsmRDNPQR/rfrHhLm+cttrSY49BEmt7g== X-Received: by 2002:a63:ad07:: with SMTP id g7-v6mr19517094pgf.19.1533666593251; Tue, 07 Aug 2018 11:29:53 -0700 (PDT) Received: from 88e9fe562b5f.sjc18.amazon.com (54-240-198-33.amazon.com. [54.240.198.33]) by smtp.gmail.com with ESMTPSA id p26-v6sm3490722pfi.183.2018.08.07.11.29.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Aug 2018 11:29:52 -0700 (PDT) From: "Joshua Z. Zhang" Content-Type: multipart/alternative; boundary="Apple-Mail=_ABC364F6-B1B3-46DE-A432-AA7E0FD339A1" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Release plan - MXNET 1.3 Date: Tue, 7 Aug 2018 11:29:46 -0700 References: To: dev@mxnet.incubator.apache.org In-Reply-To: Message-Id: <9AB660F0-E5CE-42C3-8408-59F7B4DF5ECE@gmail.com> X-Mailer: Apple Mail (2.3273) --Apple-Mail=_ABC364F6-B1B3-46DE-A432-AA7E0FD339A1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I strongly suggest to track this PR = https://github.com/apache/incubator-mxnet/pull/11908 = in 1.3 release = which fixed the usability issue for lower end machines that don=E2=80=99t = have as large shared memory space as ec2 instances.=20 Best, - Zhi > On Aug 7, 2018, at 9:05 AM, Roshani Nagmote = wrote: >=20 > Hi all, >=20 > Right now, we are delaying MXNet 1.3 release for pending TensorRT PR ( > https://github.com/apache/incubator-mxnet/pull/11325 ). >=20 > I wanted to ask everyone for their opinions if we should delay the = release > to get tensorRT integration in or we should go ahead with the release = and > include tensorRT in next release. Please provide suggestions. >=20 > Thanks, > Roshani >=20 > On Mon, Aug 6, 2018 at 12:45 AM Hagay Lupesko = wrote: >=20 >> Some thoughts: why not keep it out of 1.3, and merge it into master = so it >> can go out with 1.4 instead? >> Pros: >> - Reduce quality risks for 1.3 >> - More time to test and get feedback before release >> - Avoid further delays in 1.3 release (lots of good stuff there = already for >> users) >> Cons: >> - People will need to get master to experiment with TRT (not a major = issue >> IMO) >>=20 >> Besides, TRT requires a build flag anyway, so MXNet users consuming = built >> packages (PyPi, Scala) will anyway not be able to try it out unless >> building from source... >>=20 >> Thoughts? >>=20 >> On Sun, Aug 5, 2018 at 10:38 PM Steffen Rochel = >> wrote: >>=20 >>> Marek, Kellen, Jun, Da, Eric, myself and a few other people = discussed >>> offline about TensorRT integration PR ( >>> https://github.com/apache/incubator-mxnet/pull/11325 ). We do agree = that >>> it >>> would be good to include the PR into upcoming 1.3 release, but are = all >>> concerned about the risk involved and the breaking API change. The >>> discussion converged to following proposal. (1) change to contrib PR = and >>> (2) define a different top level API to indicate that the package is = part >>> of contrib and experimental (details of API TBD between Marek, = Kellen and >>> Eric). This change would allow to include TRT integration with v1.3 = to >>> enable users to try TRT with MXNet, minimize the risk and avoid = breaking >>> API change. >>> To accommodate the change the request is to delay RC for a few days. >>>=20 >>> Regards, >>> Steffen >>>=20 >>> On Tue, Jul 31, 2018 at 5:08 PM Roshani Nagmote < >> roshaninagmote2@gmail.com >>>>=20 >>> wrote: >>>=20 >>>> Hi, >>>>=20 >>>> I have created a wiki for tracking MXNet 1.3 release with the = timeline. >>>> Please take a look here: >>>>=20 >>>>=20 >>>=20 >> = https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubati= ng%29+1.3.0+Release+Status >>>>=20 >>>> I am still waiting for following 2 PRs to get merged: >>>> TRT integration: = https://github.com/apache/incubator-mxnet/pull/11325 >>>> Gluon RNN: https://github.com/apache/incubator-mxnet/pull/11482 >>>>=20 >>>> *Code freeze date is 08/02(Thursday).* Kindly try to complete = ongoing >>> work >>>> and get these PRs merged. >>>>=20 >>>> Thanks, >>>> Roshani >>>>=20 >>>>=20 >>>>=20 >>>> On Mon, Jul 30, 2018 at 1:02 PM Roshani Nagmote < >>> roshaninagmote2@gmail.com >>>>>=20 >>>> wrote: >>>>=20 >>>>> Hi all, >>>>>=20 >>>>> Here is an update on MXNet 1.3 release: >>>>> I am still waiting for following PRs to get merged: >>>>>=20 >>>>> TRT integration: >> https://github.com/apache/incubator-mxnet/pull/11325 >>>>> Gluon RNN: https://github.com/apache/incubator-mxnet/pull/11482 >>>>> Scala examples: >>>>>=20 >>>>> https://github.com/apache/incubator-mxnet/pull/11753 >>>>>=20 >>>>> https://github.com/apache/incubator-mxnet/pull/11621 >>>>>=20 >>>>> *New code freeze date is: 08/03* Please try to get your ongoing = PRs >>>>> merged by then. >>>>>=20 >>>>> @Pedro, I didn't include your PRs in tracking list as you said = those >>> are >>>>> not critical for now. Please let me know if those needs to be >> included. >>>>> https://github.com/apache/incubator-mxnet/pull/11636 >>>>> https://github.com/apache/incubator-mxnet/pull/11562 >>>>>=20 >>>>> I also have updated project proposal cwiki page to update the = status >> of >>>>> PRs. >>>>> < >>>>=20 >>>=20 >> = https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+ne= xt+MXNet+Release >>>>>=20 >>>>>=20 >>>>> Please let me know if I am missing something. >>>>>=20 >>>>> Thanks, >>>>> Roshani >>>>>=20 >>>>>=20 >>>>> On Thu, Jul 26, 2018 at 1:34 PM Pedro Larroy < >>>> pedro.larroy.lists@gmail.com> >>>>> wrote: >>>>>=20 >>>>>> I would like to get these PR merged: >>>>>>=20 >>>>>> https://github.com/apache/incubator-mxnet/pull/11636 >>>>>> https://github.com/apache/incubator-mxnet/pull/11562 >>>>>>=20 >>>>>> How much longer until the code freeze? >>>>>>=20 >>>>>> On Thu, Jul 26, 2018 at 1:44 AM Roshani Nagmote < >>>>>> roshaninagmote2@gmail.com> >>>>>> wrote: >>>>>>=20 >>>>>>> Hi all, >>>>>>>=20 >>>>>>> PRs waiting to be merged for 1.3 release: >>>>>>> https://github.com/apache/incubator-mxnet/pull/11325 >>>>>>>=20 >>>>>>> Are there any other PRs waiting to get merged? Please let me = know. >>>>>>>=20 >>>>>>> Release blocker issue: >>>>>>> https://github.com/apache/incubator-mxnet/issues/11853 >>>>>>>=20 >>>>>>> @Marco, @Kellen, Thanks for bringing up the important topic. I >> agree >>>>>> with >>>>>>> you and we(internal Amazon team) will be working on fixing the >>>> disabled >>>>>>> tests. >>>>>>> Currently, my colleague, Hao Jin is working on compiling the = list >> of >>>>>>> disabled tests and leading the effort to fix them in the next = few >>>> days. >>>>>>>=20 >>>>>>> Thanks, >>>>>>> Roshani >>>>>>>=20 >>>>>>> On Mon, Jul 23, 2018 at 6:39 PM kellen sunderland < >>>>>>> kellen.sunderland@gmail.com> wrote: >>>>>>>=20 >>>>>>>> Thanks again for organizing Roshani. I believe the TensorRT >> work >>> is >>>>>>> ready >>>>>>>> for a merge. Thanks to Marek and all the NVIDIA people for >>>> iterating >>>>>> on >>>>>>>> it. If possible could a committer review, make sure it meets >>> their >>>>>>>> expectations and then merge? PR is here: >>>>>>>> https://github.com/apache/incubator-mxnet/pull/11325 >>>>>>>>=20 >>>>>>>> To Marco's point. I'd recommend we review some of those >> disabled >>>>>> tests >>>>>>> and >>>>>>>> see how likely they are to affect users before we cut a = release. >>>>>> Many of >>>>>>>> them are obviously not too important from a user's point of = view >>>> (e.g. >>>>>>>> downloading a sometimes-offline image in a test). One idea >> would >>> be >>>>>> to >>>>>>> try >>>>>>>> and address as many of the customer impacting issues as = possible >>>>>> between >>>>>>>> code freeze and the RC0 vote. >>>>>>>>=20 >>>>>>>> On Mon, Jul 23, 2018 at 1:23 PM Marco de Abreu >>>>>>>> wrote: >>>>>>>>=20 >>>>>>>>> Hello Roshani, >>>>>>>>>=20 >>>>>>>>> frequent releases are good and I'm supportive for this in >>> general >>>> in >>>>>>>> order >>>>>>>>> to provide our users with the latest features and >> improvements. >>>> But >>>>>> at >>>>>>>> the >>>>>>>>> moment, I'm slightly concerned about the test coverage due to >>>> [1]. I >>>>>>> want >>>>>>>>> us to be conscious about cutting a release even though not all >>>> tests >>>>>>> are >>>>>>>>> enabled (29 disabled tests [2] as of today). However, I >>>> acknowledge >>>>>>> that >>>>>>>> we >>>>>>>>> have improved by a lot lately thanks to everybody >> participating >>>> and >>>>>>>> leading >>>>>>>>> the efforts around improving flaky tests. =46rom a = retrospective >>>>>> point of >>>>>>>>> view, we could say that these efforts have actually revealed >>> some >>>>>> quite >>>>>>>>> interesting bugs and thus the time was well spent and yielded >>> good >>>>>>>> results. >>>>>>>>>=20 >>>>>>>>> What does the community think about making another sprint of >>>>>>> improvements >>>>>>>>> around tests followed up by a period of 1-2 weeks during which >>> we >>>>>>> observe >>>>>>>>> the failures closely to ensure that no critical paths are >>>> impacted? >>>>>> If >>>>>>> we >>>>>>>>> are in a good shape by then, we could continue the release >>> process >>>>>> and >>>>>>> at >>>>>>>>> the same time have the advantage of giving contributors more >>> lead >>>>>> time >>>>>>> to >>>>>>>>> finish their work to ensure it gets into the release in the >>>> desired >>>>>>>>> quality. >>>>>>>>>=20 >>>>>>>>> Again, thanks to everybody for their efforts during the last >>> weeks >>>>>> to >>>>>>>>> improve the usability and stability of MXNet. This is great >>>>>> community >>>>>>>>> effort and a good example of a community working together >>> towards >>>> a >>>>>>>> unified >>>>>>>>> goal! >>>>>>>>>=20 >>>>>>>>> Best regards, >>>>>>>>> Marco >>>>>>>>>=20 >>>>>>>>> [1]: >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>=20 >>>=20 >> = https://lists.apache.org/thread.html/d6d81401de796a96677a112d6cd0b074b01f4= 6564194ea89b86c6a3e@%3Cdev.mxnet.apache.org%3E >>>>>>>>> [2]: >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>=20 >>>=20 >> = https://github.com/apache/incubator-mxnet/issues?q=3Dis%3Aopen+is%3Aissue+= label%3A%22Disabled+test%22 >>>>>>>>>=20 >>>>>>>>> On Mon, Jul 23, 2018 at 8:34 PM Roshani Nagmote < >>>>>>>> roshaninagmote2@gmail.com >>>>>>>>>>=20 >>>>>>>>> wrote: >>>>>>>>>=20 >>>>>>>>>> Hi all, >>>>>>>>>>=20 >>>>>>>>>> As mentioned before, code freeze date is today July 23rd. >>> Please >>>>>> try >>>>>>> to >>>>>>>>> get >>>>>>>>>> your ongoing PRs merged by today. >>>>>>>>>> Please let me know if there are any concerns or need more >>> time. >>>>>>>>>>=20 >>>>>>>>>> Thanks, >>>>>>>>>> Roshani >>>>>>>>>>=20 >>>>>>>>>> On Thu, Jul 19, 2018 at 1:16 PM Anirudh Acharya < >>>>>>> anirudhkrec@gmail.com >>>>>>>>>=20 >>>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>>> @sandeep krishnamurthy the >>> bug >>>>>> fixes >>>>>>>> in >>>>>>>>>> the >>>>>>>>>>> R-package is something we have just begun, there will not >> be >>>>>>> anything >>>>>>>>>>> significant to announce before the v1.3 code freeze. >>>>>>>>>>>=20 >>>>>>>>>>> On Wed, Jul 18, 2018 at 10:08 PM Steffen Rochel < >>>>>>>>> steffenrochel@gmail.com >>>>>>>>>>>=20 >>>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>>> To make it easier to find the discussions related to >>> project >>>>>>>>> proposals >>>>>>>>>> I >>>>>>>>>>>> added a column with a link to the thread on dev@ for >> most >>>>>>>> projects. >>>>>>>>>>>> Appreciate for the project owners to fill in the blanks >>> and >>>> to >>>>>>>> check >>>>>>>>>>> that I >>>>>>>>>>>> got the right threads. >>>>>>>>>>>>=20 >>>>>>>>>>>> Regards, >>>>>>>>>>>> Steffen >>>>>>>>>>>>=20 >>>>>>>>>>>> On Wed, Jul 18, 2018 at 7:11 PM Roshani Nagmote < >>>>>>>>>>> roshaninagmote2@gmail.com >>>>>>>>>>>>>=20 >>>>>>>>>>>> wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>>> Hi Kellen, >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Sure. I will update the notes with the information. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> Roshani >>>>>>>>>>>>>=20 >>>>>>>>>>>>> On Wed, Jul 18, 2018 at 3:01 PM kellen sunderland < >>>>>>>>>>>>> kellen.sunderland@gmail.com> wrote: >>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Hey Roshani, >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Would you be able to add 'TensorRT Runtime >>> Integration' >>>> to >>>>>>> the >>>>>>>>> list >>>>>>>>>>> of >>>>>>>>>>>>>> upcoming features? We'll target getting the release >>> in >>>>>> and >>>>>>>>>> polished >>>>>>>>>>> by >>>>>>>>>>>>> the >>>>>>>>>>>>>> 23rd. Design proposal is here: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>=20 >>>=20 >> = https://cwiki.apache.org/confluence/display/MXNET/Runtime+Integration+with= +TensorRT >>>>>>>>>>>>>> and the lead contributor is Marek Kolodziej. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> -Kellen >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On Wed, Jul 18, 2018 at 8:32 PM Roshani Nagmote < >>>>>>>>>>>>> roshaninagmote2@gmail.com >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> I am starting the process to prepare for Apache >>> MXNet >>>>>>>>>> (incubating) >>>>>>>>>>>> 1.3 >>>>>>>>>>>>>>> Release. Please find project proposal draft for >> this >>>>>>> release >>>>>>>>>> here: >>>>>>>>>>>>>>> <* >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>=20 >>>=20 >> = https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+ne= xt+MXNet+Release >>>>>>>>>>>>>>> < >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>=20 >>>=20 >> = https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+ne= xt+MXNet+Release >>>>>>>>>>>>>>>> * >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Target feature freeze date is July 23rd. A release >>>>>>> candidate >>>>>>>>> will >>>>>>>>>>> be >>>>>>>>>>>>> cut >>>>>>>>>>>>>>> around Monday, August 6th and voting will commence >>>> from >>>>>>> then >>>>>>>>>> until >>>>>>>>>>>>>>> Thursday, August 9th. If you have any additional >>>>>> features >>>>>>> in >>>>>>>>>>> progress >>>>>>>>>>>>> and >>>>>>>>>>>>>>> would like to include it in this release, please >>> make >>>>>> sure >>>>>>> to >>>>>>>>>>> comment >>>>>>>>>>>>> so >>>>>>>>>>>>>> I >>>>>>>>>>>>>>> can update the release notes. >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Feel free to add any other comments/suggestions. >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> Roshani >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>=20 >>>>=20 >>>=20 >>=20 --Apple-Mail=_ABC364F6-B1B3-46DE-A432-AA7E0FD339A1--