From vali@example.com Mon Jan 01 19:02:52 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 465 invoked from network); 1 Jan 2007 19:02:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 19:02:52 -0000 Received: (qmail 94209 invoked by uid 500); 1 Jan 2007 19:02:58 -0000 Delivered-To: vali@example.com Received: (qmail 94181 invoked by uid 500); 1 Jan 2007 19:02:58 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 94171 invoked by uid 99); 1 Jan 2007 19:02:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 11:02:58 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 11:02:49 -0800 Received: by nf-out-0910.google.com with SMTP id x29so1091490nfb for <vali@example.com>; Mon, 01 Jan 2007 11:02:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Er0Vel1mpLDTSIcRCFRSNvOEThSxwaOlcb1ZqF5LbZsWizvefBDOoesKr0S5M8EvARc2tgj4b3UDisfucl9/+D76frfV5Luy18XOcc/AMQyB2eGNnjcPApxf5FezZlSLDuQUTe06olENjqcMOR0yOF6Tf6Ei7mWaJx84S59jyQU= Received: by 83.161.120.155 with SMTP id a5mr5276023huf.1167678148319; Mon, 01 Jan 2007 11:02:28 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 11:02:28 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 14:02:28 -0500 From: "Rahul Akolkar" <vali@example.com> To: vali@example.com Subject: Re: [v104] Ready In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <vali@example.com> <vali@example.com> X-Virus-Checked: Checked by ClamAV on apache.org On 12/31/06, Craig McClanahan <vali@example.com> wrote: > On 12/31/06, Rahul Akolkar <vali@example.com> wrote: > > > > No pending issues against 1.0.4 snap in JIRA ATM (the couple of open > > ones are sufficiently addressed IMO), so pending ~24 hours for any > > feedback on the dry run (let me know if you need more time), I will > > move towards a final set of proposed artifacts (and a vote). > > > > -Rahul > > > > > Picking my way through the release notes (nice job on the updates :-), I > notice we still have the following statement regarding the expected final > vote: > > > ----- snip ----- > > This is the fourth milestone release of Shale, released to encourage > experimentation and gather feedback on usage issues and requested features. > A final vote on quality has yet to take place for this release, but it will > likely be voted to be of "beta" quality due to the following issues: > > - Reliance on a snapshot of the unreleased Standalone Tiles package. > > However, many of the APIs in Shale are reasonably stable -- for details, see > Shale API Target Audiences and Stability > Ratings<http://shale.apache.org/api-stability.html> > . > > ----- snip ----- > > We had talked earlier about the idea of doing quality rankings on the > individual packages separately, so that we'd have a chance to grant a GA > quality vote on some remaining portion other than shale-tiles. If we still > feel this way, I'd suggest modifying this text to something like this: > > This is the fourth milestone release of Shale, released to encourage > experimentation > and gather feedback on usage issues and requested features. A full vote > on quality > has yet to take place for this release, but will take place later. We > plan to vote on the > quality of each module separately (where necessary). For example, the > shale-tiles > module is likely to receive a grade no higher than "Beta" because it > relies on a > snapshot of the as-yet unreleased Standalone Tiles package. > > As a plan B, we could pull shale-tiles from this release entirely, and > release it separately (with its own release grade vote), as I'm pretty > confident that this would be the only exception. I'd be OK with this but > would still prefer that everything was packaged together and we did the vote > rankings specficially, with wording something like the above. > > Thoughts? > <snip/> Agreed (I prefer Plan A), thanks for the feedback. The previous blurb existed in the 104 release notes since this thread didn't get much feedback as to what that blurb should be: http://tinyurl.com/y6dnbe I have now updated the notes based on this feedback. -Rahul > Craig > > From vali@example.com Mon Jan 01 20:15:30 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 10803 invoked from network); 1 Jan 2007 20:15:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 20:15:29 -0000 Received: (qmail 32941 invoked by uid 500); 1 Jan 2007 20:15:35 -0000 Delivered-To: vali@example.com Received: (qmail 32915 invoked by uid 500); 1 Jan 2007 20:15:35 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 32906 invoked by uid 99); 1 Jan 2007 20:15:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 12:15:35 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wx-out-0506.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 12:15:25 -0800 Received: by wx-out-0506.google.com with SMTP id i27so5683565wxd for <vali@example.com>; Mon, 01 Jan 2007 12:15:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=HxQ3cAysnVqelmlcWyhZYMk+L4ucgdxRl1GbOLhZJ0HLM1jTh0oycqgqOzhJh7d8Aise/s/59IH8pw6T3dDWHzeGuo96lKkdfaXy0LuyrW6sdSTt05fK4P4xvqMej6H112jmJU5wsCtEfmwEhsxosp03pLoS2e0BvnnF7egM9oQ= Received: by 83.161.120.155 with SMTP id t12mr4942822aga.1167682505064; Mon, 01 Jan 2007 12:15:05 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 12:15:05 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 12:15:05 -0800 From: "Craig McClanahan" <vali@example.com> Sender: vali@example.com To: vali@example.com Subject: Re: [v104] Ready In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_155754_19438376.1167682505036" References: <vali@example.com> <vali@example.com> <vali@example.com> X-Google-Sender-Auth: baf03b7cce1790fc X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_155754_19438376.1167682505036 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/1/07, Rahul Akolkar <vali@example.com> wrote: > > On 12/31/06, Craig McClanahan <vali@example.com> wrote: > > On 12/31/06, Rahul Akolkar <vali@example.com> wrote: > > > > > > No pending issues against 1.0.4 snap in JIRA ATM (the couple of open > > > ones are sufficiently addressed IMO), so pending ~24 hours for any > > > feedback on the dry run (let me know if you need more time), I will > > > move towards a final set of proposed artifacts (and a vote). > > > > > > -Rahul > > > > > > > > > Picking my way through the release notes (nice job on the updates :-), I > > notice we still have the following statement regarding the expected > final > > vote: > > > > > > ----- snip ----- > > > > This is the fourth milestone release of Shale, released to encourage > > experimentation and gather feedback on usage issues and requested > features. > > A final vote on quality has yet to take place for this release, but it > will > > likely be voted to be of "beta" quality due to the following issues: > > > > - Reliance on a snapshot of the unreleased Standalone Tiles package. > > > > However, many of the APIs in Shale are reasonably stable -- for details, > see > > Shale API Target Audiences and Stability > > Ratings<http://shale.apache.org/api-stability.html> > > . > > > > ----- snip ----- > > > > We had talked earlier about the idea of doing quality rankings on the > > individual packages separately, so that we'd have a chance to grant a GA > > quality vote on some remaining portion other than shale-tiles. If we > still > > feel this way, I'd suggest modifying this text to something like this: > > > > This is the fourth milestone release of Shale, released to encourage > > experimentation > > and gather feedback on usage issues and requested features. A full > vote > > on quality > > has yet to take place for this release, but will take place > later. We > > plan to vote on the > > quality of each module separately (where necessary). For example, > the > > shale-tiles > > module is likely to receive a grade no higher than "Beta" because it > > relies on a > > snapshot of the as-yet unreleased Standalone Tiles package. > > > > As a plan B, we could pull shale-tiles from this release entirely, and > > release it separately (with its own release grade vote), as I'm pretty > > confident that this would be the only exception. I'd be OK with this > but > > would still prefer that everything was packaged together and we did the > vote > > rankings specficially, with wording something like the above. > > > > Thoughts? > > > <snip/> > > Agreed (I prefer Plan A), thanks for the feedback. The previous blurb > existed in the 104 release notes since this thread didn't get much > feedback as to what that blurb should be: > > http://tinyurl.com/y6dnbe > > I have now updated the notes based on this feedback. +1 on your changes ... looks good. -Rahul Criag > Craig > > > > > ------=_Part_155754_19438376.1167682505036-- From vali@example.com Mon Jan 01 20:56:39 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 22213 invoked from network); 1 Jan 2007 20:56:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 20:56:39 -0000 Received: (qmail 65682 invoked by uid 500); 1 Jan 2007 20:56:45 -0000 Delivered-To: vali@example.com Received: (qmail 65648 invoked by uid 500); 1 Jan 2007 20:56:45 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 65639 invoked by uid 99); 1 Jan 2007 20:56:45 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 12:56:45 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 12:56:36 -0800 Received: by nf-out-0910.google.com with SMTP id x29so1119287nfb for <vali@example.com>; Mon, 01 Jan 2007 12:56:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=KinmBptG0j8hU3QCC+aAbRt6pxL5K6Z7k2CNsl/zZgpGWHrhswhZWnH0SLOgXXb4csv/TTQW3KQhH8CZorp6fd5gFvc0L/EIJCpfWic2Ja3E3AOXek8O3RuQfv6NM5QrCeK/iKv55C4C8RrvWSMfIL5QI1RaTe1/ff5/0Ws3YJU= Received: by 83.161.120.155 with SMTP id t11mr3226317hud.1167684974958; Mon, 01 Jan 2007 12:56:14 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 12:56:14 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 15:56:14 -0500 From: "Rahul Akolkar" <vali@example.com> To: vali@example.com Subject: Code freeze 1.0.x branch MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org The SHALE_1_0_X branch [1] has been created. Over the next day, it will be used to prepare the proposed v1.0.4 artifacts and svn tag. My preference would be to have no commits to the branch when releases are being prepared and voted on (relevant commits to trunk that need to be backported can wait a day or two, unless its a showstopper for the release). I will ping this thread when this is done for v1.0.4, and the branch is open for general commits. -Rahul [1] http://svn.apache.org/repos/asf/shale/framework/branches/SHALE_1_0_X/ From vali@example.com Mon Jan 01 21:00:12 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 22516 invoked from network); 1 Jan 2007 21:00:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 21:00:11 -0000 Received: (qmail 66870 invoked by uid 500); 1 Jan 2007 21:00:18 -0000 Delivered-To: vali@example.com Received: (qmail 66828 invoked by uid 500); 1 Jan 2007 21:00:18 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 66819 invoked by uid 99); 1 Jan 2007 21:00:17 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 13:00:17 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wx-out-0506.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 13:00:08 -0800 Received: by wx-out-0506.google.com with SMTP id i27so5693174wxd for <vali@example.com>; Mon, 01 Jan 2007 12:59:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=V0j0ewndX4Gna6Nti61BgR5nmNhxyLbqOVOzn0A/brpAHctAO99L2uyIS1IzWpACJe2UtX0ncJTRyGOL12xS9wZwu07AQdAFltCjUFgMoCwL3OHtZM9//bN2BC664BOLYzMAxOYSF67LdBU8Kr2bqDadFC5ahPa/nYG3DFJ37kw= Received: by 83.161.120.155 with SMTP id z18mr4951116agz.1167685187743; Mon, 01 Jan 2007 12:59:47 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 12:59:47 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 12:59:47 -0800 From: "Craig McClanahan" <vali@example.com> Sender: vali@example.com To: vali@example.com Subject: Re: Code freeze 1.0.x branch In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_156078_14969879.1167685187643" References: <vali@example.com> X-Google-Sender-Auth: 0a9b3ffefbdd93c5 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_156078_14969879.1167685187643 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/1/07, Rahul Akolkar <vali@example.com> wrote: > > The SHALE_1_0_X branch [1] has been created. Over the next day, it > will be used to prepare the proposed v1.0.4 artifacts and svn tag. > > My preference would be to have no commits to the branch when releases > are being prepared and voted on (relevant commits to trunk that need > to be backported can wait a day or two, unless its a showstopper for > the release). I will ping this thread when this is done for v1.0.4, > and the branch is open for general commits. Does this also imply that the trunk is now open for new features? I want to spend a bit of time between plays :-) on things like SHALE-262, and it'd be easier to just work on the trunk now, rather than branching shale-test and then merging later. (And no, I'm *not* going to propose that we add a new feature to 1.0.4 at the last minute :-). Craig -Rahul > > [1] http://svn.apache.org/repos/asf/shale/framework/branches/SHALE_1_0_X/ > ------=_Part_156078_14969879.1167685187643-- From vali@example.com Mon Jan 01 22:41:50 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 36871 invoked from network); 1 Jan 2007 22:41:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 22:41:49 -0000 Received: (qmail 26036 invoked by uid 500); 1 Jan 2007 22:41:56 -0000 Delivered-To: vali@example.com Received: (qmail 25945 invoked by uid 500); 1 Jan 2007 22:41:56 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 25936 invoked by uid 99); 1 Jan 2007 22:41:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 14:41:56 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 14:41:47 -0800 Received: by nf-out-0910.google.com with SMTP id x29so1144446nfb for <vali@example.com>; Mon, 01 Jan 2007 14:41:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JgdEh+KcAPVTncDrF+QfpRnZ/vdQqa8JkgaGid9Q9agcVJCmhh0Q5ig7IgMXwOkcg7SbWAC0LmjBkorzA/lCLXblrhi8o3LUWmE/CgKb1GLzeUcyOgsYNWLubHN0PIGulHW9Ude20J1whctaGEnNuZ+yrKhK358kbFFl3zUy5jk= Received: by 83.161.120.155 with SMTP id m13mr1814127hue.1167691285175; Mon, 01 Jan 2007 14:41:25 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 14:41:25 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 17:41:25 -0500 From: "Rahul Akolkar" <vali@example.com> To: vali@example.com Subject: Re: Code freeze 1.0.x branch In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <vali@example.com> <vali@example.com> X-Virus-Checked: Checked by ClamAV on apache.org On 1/1/07, Craig McClanahan <vali@example.com> wrote: > On 1/1/07, Rahul Akolkar <vali@example.com> wrote: > > > > The SHALE_1_0_X branch [1] has been created. Over the next day, it > > will be used to prepare the proposed v1.0.4 artifacts and svn tag. > > > > My preference would be to have no commits to the branch when releases > > are being prepared and voted on (relevant commits to trunk that need > > to be backported can wait a day or two, unless its a showstopper for > > the release). I will ping this thread when this is done for v1.0.4, > > and the branch is open for general commits. > > > Does this also imply that the trunk is now open for new features? I want to > spend a bit of time between plays :-) on things like SHALE-262, and it'd be > easier to just work on the trunk now, rather than branching shale-test and > then merging later. > <snip/> Indeed, now that we have multiple lines of development, development need not stop just because a release is imminent. The v104 tag will come from the 10x branch, so the trunk is no longer relevant for the release ;-) More generally, I propose we have the following procedure for future releases: (1) At the appropriate time, the RM declares a code freeze on the relevant branch (2) Development continues in all other branches, and developers keep notes of any changes that need to be ported to the "frozen" branch (3) When freeze is over, developers commit pending changes Showstoppers that require a fix to the frozen branch restart the process at (1). -Rahul > (And no, I'm *not* going to propose that we add a new feature to 1.0.4 at > the last minute :-). > > Craig > > > -Rahul > > > > [1] http://svn.apache.org/repos/asf/shale/framework/branches/SHALE_1_0_X/ > > > > From vali@example.com Mon Jan 01 22:54:16 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 38086 invoked from network); 1 Jan 2007 22:54:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 22:54:15 -0000 Received: (qmail 31383 invoked by uid 500); 1 Jan 2007 22:54:22 -0000 Delivered-To: vali@example.com Received: (qmail 31349 invoked by uid 500); 1 Jan 2007 22:54:21 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 31335 invoked by uid 99); 1 Jan 2007 22:54:21 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 14:54:21 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wx-out-0506.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 14:54:12 -0800 Received: by wx-out-0506.google.com with SMTP id h29so5859300wxd for <vali@example.com>; Mon, 01 Jan 2007 14:53:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=KS1dJAVMuj6xYXxxIlNVWAs+3Rs7JzkdkabePbepXxgW/oqtClYGdOwmI+hK3dVVHt4GBcTjWhtU8feKbbgDuLey8+83KLR5yGETG/3KP/84kj4O6OYhNRwLgb62VErqWA3UB0Twrtt9h61ZrGDRF8Psd8hlAtFpfH0EU1XXbS8= Received: by 83.161.120.155 with SMTP id p7mr4990239agb.1167692031731; Mon, 01 Jan 2007 14:53:51 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 14:53:51 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 14:53:51 -0800 From: "Craig McClanahan" <vali@example.com> Sender: vali@example.com To: vali@example.com Subject: Re: Code freeze 1.0.x branch In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_156752_9357937.1167692031706" References: <vali@example.com> <vali@example.com> <vali@example.com> X-Google-Sender-Auth: 65a2ef327f21856e X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_156752_9357937.1167692031706 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/1/07, Rahul Akolkar <vali@example.com> wrote: > > On 1/1/07, Craig McClanahan <vali@example.com> wrote: > > On 1/1/07, Rahul Akolkar <vali@example.com> wrote: > > > > > > The SHALE_1_0_X branch [1] has been created. Over the next day, it > > > will be used to prepare the proposed v1.0.4 artifacts and svn tag. > > > > > > My preference would be to have no commits to the branch when releases > > > are being prepared and voted on (relevant commits to trunk that need > > > to be backported can wait a day or two, unless its a showstopper for > > > the release). I will ping this thread when this is done for v1.0.4, > > > and the branch is open for general commits. > > > > > > Does this also imply that the trunk is now open for new features? I > want to > > spend a bit of time between plays :-) on things like SHALE-262, and it'd > be > > easier to just work on the trunk now, rather than branching shale-test > and > > then merging later. > > > <snip/> > > Indeed, now that we have multiple lines of development, development > need not stop just because a release is imminent. The v104 tag will > come from the 10x branch, so the trunk is no longer relevant for the > release ;-) > > More generally, I propose we have the following procedure for future > releases: > > (1) At the appropriate time, the RM declares a code freeze on the > relevant branch > (2) Development continues in all other branches, and developers keep > notes of any changes that need to be ported to the "frozen" branch > (3) When freeze is over, developers commit pending changes > > Showstoppers that require a fix to the frozen branch restart the process > at (1). Sounds like a good general policy, although I suspect there generally will *not* be pending changes that we did not already discuss and decide on -- it will probably amount to a few patches that were deemed not critical to getting a maintenance release out the door. But time will tell :-). In the mean time, I'll go ahead and update the trunk version numbers to 1.1.0-SNAPSHOT, per our previous discussions. I've also added a JIRA version for this, so we can start tagging issues for new development as they get dealt with there. -Rahul Craig > (And no, I'm *not* going to propose that we add a new feature to 1.0.4 at > > the last minute :-). > > > > Craig > > > > > > -Rahul > > > > > > [1] > http://svn.apache.org/repos/asf/shale/framework/branches/SHALE_1_0_X/ > > > > > > > > ------=_Part_156752_9357937.1167692031706-- From vali@example.com Mon Jan 01 22:58:03 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 38718 invoked from network); 1 Jan 2007 22:57:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 22:57:52 -0000 Received: (qmail 32965 invoked by uid 500); 1 Jan 2007 22:57:57 -0000 Delivered-To: vali@example.com Received: (qmail 32935 invoked by uid 500); 1 Jan 2007 22:57:57 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 32926 invoked by uid 99); 1 Jan 2007 22:57:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 14:57:57 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ug-out-1314.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 14:57:48 -0800 Received: by ug-out-1314.google.com with SMTP id 30so5839036ugs for <vali@example.com>; Mon, 01 Jan 2007 14:57:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YVvND3XnE9Hk7yYcQU6CSn8OGLu6QS6yjeWUC7Q+lkqB6k2Nr1HAtU12FrltF2OuGe6k7fl9MxEd9htkZHvFdNYaVQAcLsAHepbjDlvl7Hy5VKgkyVw1dJwmd1J86NhcnyEIRW33v9sns8TexAJx3R6Ce5moP+/VTFRQ6ZajZf0= Received: by 83.161.120.155 with SMTP id d13mr5099492huf.1167692246806; Mon, 01 Jan 2007 14:57:26 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 14:57:26 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 17:57:26 -0500 From: "Rahul Akolkar" <vali@example.com> To: vali@example.com Subject: Re: Code freeze 1.0.x branch In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <vali@example.com> <vali@example.com> <vali@example.com> <vali@example.com> X-Virus-Checked: Checked by ClamAV on apache.org On 1/1/07, Craig McClanahan <vali@example.com> wrote: > On 1/1/07, Rahul Akolkar <vali@example.com> wrote: <snip/> > > > > More generally, I propose we have the following procedure for future > > releases: > > > > (1) At the appropriate time, the RM declares a code freeze on the > > relevant branch > > (2) Development continues in all other branches, and developers keep > > notes of any changes that need to be ported to the "frozen" branch > > (3) When freeze is over, developers commit pending changes > > > > Showstoppers that require a fix to the frozen branch restart the process > > at (1). > > > Sounds like a good general policy, although I suspect there generally will > *not* be pending changes that we did not already discuss and decide on -- > it will probably amount to a few patches that were deemed not critical to > getting a maintenance release out the door. But time will tell :-). > <snap/> Agreed :-) > In the mean time, I'll go ahead and update the trunk version numbers to > 1.1.0-SNAPSHOT, per our previous discussions. I've also added a JIRA > version for this, so we can start tagging issues for new development as they > get dealt with there. > <snip/> Sounds good, thanks. -Rahul > > Craig > > From vali@example.com Mon Jan 01 23:20:48 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 45348 invoked from network); 1 Jan 2007 23:20:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 23:20:47 -0000 Received: (qmail 42646 invoked by uid 500); 1 Jan 2007 23:20:54 -0000 Delivered-To: vali@example.com Received: (qmail 42615 invoked by uid 500); 1 Jan 2007 23:20:54 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 42601 invoked by uid 99); 1 Jan 2007 23:20:54 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 15:20:54 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 15:20:44 -0800 Received: by nf-out-0910.google.com with SMTP id x29so1154299nfb for <vali@example.com>; Mon, 01 Jan 2007 15:20:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Xw/ZcwClUkbhysPkHUMY5yIli/e5hck4JcE9a+Byt207bzGMCtVY7iQmBfQQcbOQ2FI9G+WIUBWdNRFbLhtFQemXPHA+NSBdhhEPDCzwMuRYOaBrggspo+HDdMSPgiKwzyXWm65APmfw1VzVbrlBbKz9DB4M+vJICPJ+ubtsLXU= Received: by 83.161.120.155 with SMTP id o7mr1820346hue.1167693623443; Mon, 01 Jan 2007 15:20:23 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 15:20:23 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 18:20:23 -0500 From: "Rahul Akolkar" <vali@example.com> To: vali@example.com Subject: Re: svn commit: r491671 - in /shale/framework/trunk: ./ shale-application/ shale-apps/ shale-apps/mailreader-jpa/ shale-apps/shale-blank/ shale-apps/shale-clay-usecases/ shale-apps/shale-mailreader-jpa/ shale-apps/shale-mailreader/ shale-apps/shale-s MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org On 1/1/07, vali@example.com <vali@example.com> wrote: > Author: craigmcc > Date: Mon Jan 1 14:58:04 2007 > New Revision: 491671 > > URL: http://svn.apache.org/viewvc?view=rev&rev=491671 > Log: > Advance trunk version numbers from 1.0.4-SNAPSHOT to 1.1.0-SNAPSHOT now that > 1.0 has been branched. SHALE-383 > > Modified: > shale/framework/trunk/pom.xml <snip/> The shale-master version in shale-parent should be 3-SNAPSHOT, though I'm not sure if continuum will install it locally by itself. -Rahul From vali@example.com Mon Jan 01 23:54:49 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 52867 invoked from network); 1 Jan 2007 23:54:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jan 2007 23:54:48 -0000 Received: (qmail 76123 invoked by uid 500); 1 Jan 2007 23:54:55 -0000 Delivered-To: vali@example.com Received: (qmail 76038 invoked by uid 500); 1 Jan 2007 23:54:54 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 76028 invoked by uid 99); 1 Jan 2007 23:54:54 -0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jan 2007 15:54:50 -0800 Received: by nf-out-0910.google.com with SMTP id x29so1162453nfb for <vali@example.com>; Mon, 01 Jan 2007 15:53:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=BoVNC8xmllex0kXlJKVlx0vfiSG+JMp2iP8ZmdIS/R6Cff2dxXKFj8Za/9MLdSVSgU1ZNy9N1SmWfEGSEKxqFTYtwdhiORDzB8LmLVASWwSZAj9Q0hkVwD5aAfvGvDw0Wy4mRW0iChSAwWVufjmSyH+G4EkTTl6rHTp3tef4jQk= Received: by 83.161.120.155 with SMTP id s14mr1359894buc.1167695602758; Mon, 01 Jan 2007 15:53:22 -0800 (PST) Received: by 83.161.120.155 with HTTP; Mon, 1 Jan 2007 15:53:22 -0800 (PST) Message-ID: <vali@example.com> Date: Mon, 1 Jan 2007 17:53:22 -0600 From: "Greg Reddin" <vali@example.com> Sender: vali@example.com To: vali@example.com Subject: Re: [v104] Ready In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_134905_16501695.1167695602670" References: <vali@example.com> <vali@example.com> X-Google-Sender-Auth: faaa007f53d63101 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_134905_16501695.1167695602670 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 12/31/06, Craig McClanahan <vali@example.com> wrote: > > We had talked earlier about the idea of doing quality rankings on the > individual packages separately, so that we'd have a chance to grant a GA > quality vote on some remaining portion other than shale-tiles. If we > still > feel this way, I'd suggest modifying this text to something like this: > > This is the fourth milestone release of Shale, released to encourage > experimentation > and gather feedback on usage issues and requested features. A full > vote > on quality > has yet to take place for this release, but will take place later. We > plan to vote on the > quality of each module separately (where necessary). For example, the > shale-tiles > module is likely to receive a grade no higher than "Beta" because it > relies on a > snapshot of the as-yet unreleased Standalone Tiles package. +1 to the above. Greg ------=_Part_134905_16501695.1167695602670-- From vali@example.com Tue Jan 02 22:17:22 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 87330 invoked from network); 2 Jan 2007 22:17:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Jan 2007 22:17:22 -0000 Received: (qmail 6848 invoked by uid 500); 2 Jan 2007 22:17:28 -0000 Delivered-To: vali@example.com Received: (qmail 6826 invoked by uid 500); 2 Jan 2007 22:17:28 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 6817 invoked by uid 99); 2 Jan 2007 22:17:28 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2007 14:17:28 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wr-out-0506.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2007 14:17:18 -0800 Received: by wr-out-0506.google.com with SMTP id i7so1877476wra for <vali@example.com>; Tue, 02 Jan 2007 14:16:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JTlQ4nWnhE7lF59AKlnJRoHsQ+v9q6EC4+fgR1bB7e7zkMlupLmx/vBa8dU0fjFTjvgYEyryQD53npPjysqmJK5qoeDB0vx2zZLP5ew348Hu1TNaQEWyoq0aa/yhxVYUVZUqWgrY+xT/E5JkXECUr4PU6aKWLHBGbpxa8CkddZc= Received: by 83.161.120.155 with SMTP id q5mr4746963huf.1167776217716; Tue, 02 Jan 2007 14:16:57 -0800 (PST) Received: by 83.161.120.155 with HTTP; Tue, 2 Jan 2007 14:16:57 -0800 (PST) Message-ID: <vali@example.com> Date: Tue, 2 Jan 2007 15:16:57 -0700 From: "Wendy Smoak" <vali@example.com> To: vali@example.com Subject: Re: [jira] Commented: (SHALE-188) Add a default outcome to the dialog manager In-Reply-To: <7460339.1167775699856.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7460339.1167775699856.JavaMail.jira@brutus> X-Virus-Checked: Checked by ClamAV on apache.org Mail loop! Fixed by changing the users's email address to something invalid. (As advised by jefft on irc.) -- Wendy On 1/2/07, vali@example.com (JIRA) <vali@example.com> wrote: > > [ http://issues.apache.org/struts/browse/SHALE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39639 ] > > vali@example.com commented on SHALE-188: > ------------------------------------------------------- > > Your message > Subject: "[jira] Commented: (SHALE-188) Add a default outcome to the dialog manager" > could not be delivered to some or all of the intended recipients. > > > User<vali@example.com> - (550 5.1.1 User unknown) > > > > Additional Information > ====================== > Original Sender: <vali@example.com> > Sender-MTA: <83.161.120.155> > Remote-MTA: <83.161.120.155> > Reporting-MTA: <WINMX1.123multimedia.com> > MessageName: <B459ad75e0000.000000000001.0001.mml> > Last-Attempt-Date: <23:06:25 Tue, 02 January 2007> From vali@example.com Wed Jan 03 01:10:52 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 42022 invoked from network); 3 Jan 2007 01:10:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Jan 2007 01:10:51 -0000 Received: (qmail 61670 invoked by uid 500); 3 Jan 2007 01:10:58 -0000 Delivered-To: vali@example.com Received: (qmail 61581 invoked by uid 500); 3 Jan 2007 01:10:57 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 61572 invoked by uid 99); 3 Jan 2007 01:10:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2007 17:10:57 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ug-out-1314.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2007 17:10:48 -0800 Received: by ug-out-1314.google.com with SMTP id 30so6082864ugs for <vali@example.com>; Tue, 02 Jan 2007 17:10:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Do8pRgn6/yNJNx230Ksnyyru82tSXTmDGCsyE2LU1GqadV1qm7WEitKbppqrWgFzKOud38PM48cW+QmHXU5qiy9Q32/Faind88v32k7hoW6iE5jvDjjfWv17SjLNLnscE0bq22bXLCIRjSZUrzKmJq0BWpnRZhpOpSUkNDXptmA= Received: by 83.161.120.155 with SMTP id q19mr2091330huc.1167786626380; Tue, 02 Jan 2007 17:10:26 -0800 (PST) Received: by 83.161.120.155 with HTTP; Tue, 2 Jan 2007 17:10:26 -0800 (PST) Message-ID: <vali@example.com> Date: Tue, 2 Jan 2007 20:10:26 -0500 From: "Rahul Akolkar" <vali@example.com> To: vali@example.com Subject: [VOTE] Release Shale version 1.0.4 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org This is a vote to release Apache Shale version 1.0.4 (1) The repository has been tagged (long, possibly fragmented URLs below): http://svn.apache.org/repos/asf/shale/framework/tags/APACHE_SHALE_1_0_4/ (2) The Maven artifacts are staged: http://people.apache.org/~rahul/shale/v104/repos org.apache.shale.extras:mailreader-jpa:1.0.4 org.apache.shale:shale-application:1.0.4 org.apache.shale:shale-apps-parent:1.0.4 org.apache.shale:shale-clay:1.0.4 org.apache.shale:shale-core:1.0.4 org.apache.shale:shale-dialog:1.0.4 org.apache.shale:shale-dialog-basic:1.0.4 org.apache.shale:shale-dialog-scxml:1.0.4 org.apache.shale:shale-dist:1.0.4 org.apache.shale:shale-parent:1.0.4 org.apache.shale:shale-remoting:1.0.4 org.apache.shale:shale-spring:1.0.4 org.apache.shale:shale-test:1.0.4 org.apache.shale:shale-tiger:1.0.4 org.apache.shale:shale-tiles:1.0.4 org.apache.shale:shale-validator:1.0.4 org.apache.shale:shale-view:1.0.4 (3) The release artifacts are available: http://people.apache.org/~rahul/shale/v104/ mailreader-jpa-1.0.4.zip shale-blank-1.0.4.zip shale-clay-usecases-1.0.4.zip shale-framework-1.0.4.zip shale-mailreader-1.0.4.zip shale-mailreader-jpa-1.0.4.zip shale-sql-browser-1.0.4.zip shale-usecases-1.0.4.zip (4) The release notes are here, for ready reference: http://people.apache.org/~rahul/shale/v104/release-notes-1.0.4.html (5) Vote Please review these artifacts, signatures and checksums, and vote whether we should release them as Apache Shale version 1.0.4. --8<-------------------------------------------- [ ] +1 (Binding) for PMC members only [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released ------------------------------------------------ A quality vote (per module, where necessary) will be held later on if this passes. -Rahul From vali@example.com Wed Jan 03 05:01:01 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 93038 invoked from network); 3 Jan 2007 05:01:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Jan 2007 05:01:00 -0000 Received: (qmail 25048 invoked by uid 500); 3 Jan 2007 05:01:07 -0000 Delivered-To: vali@example.com Received: (qmail 24961 invoked by uid 500); 3 Jan 2007 05:01:06 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 24952 invoked by uid 99); 3 Jan 2007 05:01:06 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2007 21:01:06 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wx-out-0506.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2007 21:00:57 -0800 Received: by wx-out-0506.google.com with SMTP id i27so6137336wxd for <vali@example.com>; Tue, 02 Jan 2007 21:00:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=UQqhqWvZNO2AZcZThcN/zYUZDymcmyPJFKebDlqxE1Dp5iO9eJEQzcU8vsMzVsuQ3VFgskxOrFM5RSxKO99nT3zi2wdM+/d/gwKAMh2tzVrANdH3yKgd+FDhc5HxQL7PR+zW/TQnKE1GTTV9jTaEV8kGXsDnTR4fQpv6Ug5pJYM= Received: by 83.161.120.155 with SMTP id x1mr14598859agx.1167800436229; Tue, 02 Jan 2007 21:00:36 -0800 (PST) Received: by 83.161.120.155 with HTTP; Tue, 2 Jan 2007 21:00:36 -0800 (PST) Message-ID: <vali@example.com> Date: Tue, 2 Jan 2007 21:00:36 -0800 From: "Craig McClanahan" <vali@example.com> Sender: vali@example.com To: vali@example.com Subject: Re: [VOTE] Release Shale version 1.0.4 In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_172360_19182784.1167800436212" References: <vali@example.com> X-Google-Sender-Auth: 134c5ff87ff9eef0 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_172360_19182784.1167800436212 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/2/07, Rahul Akolkar <vali@example.com> wrote: > > org.apache.shale:shale-apps-parent:1.0.4 As part of my review of the proposed 1.0.4 release (all the sigs match ... but let's see what happens when I try to *use* this stuff :-), I want to try building our distribution artifacts. I could build the framework with no problems -- but trying to build an app fails because this artifact is (correctly) not available in any repository yet. Thinking about it a bit more, we aren't officially distributing *source* artifacts for this POM, or for "org.apache.shale:shale-master:2" either -- both of which you would need to install if you're trying to build Shale. On the other hand, once the distribution is voted in and released, the artifacts will be available (but only if you know to go get them). One could certainly argue that, since our source build system is Maven based, we could expect this to "just work" for our downstream users after a release. But what about folks who are not "always on" connected to the Internet? Or folks who need to be able to build Shale, from source, in Maven's "offline" mode? Maybe we should publish these two POM artifacts as part of some "source distribution" somewhere, like we do all the other POMs? Craig PS: I'm not done reviewing the proposed 1.0.4 bits, but things look good (outside of the issue raised here) so far. ------=_Part_172360_19182784.1167800436212-- From vali@example.com Wed Jan 03 11:56:39 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 75505 invoked from network); 3 Jan 2007 11:56:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Jan 2007 11:56:36 -0000 Received: (qmail 19543 invoked by uid 500); 3 Jan 2007 11:56:43 -0000 Delivered-To: vali@example.com Received: (qmail 19509 invoked by uid 500); 3 Jan 2007 11:56:42 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 19500 invoked by uid 99); 3 Jan 2007 11:56:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2007 03:56:42 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [83.161.120.155] (HELO smtp02.lnh.mail.rcn.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2007 03:56:31 -0800 Received: from mr02.lnh.mail.rcn.net ([83.161.120.155]) by smtp02.lnh.mail.rcn.net with ESMTP; 03 Jan 2007 06:56:11 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [83.161.120.155]) by mr02.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id MSP77430; Wed, 3 Jan 2007 06:56:02 -0500 (EST) Received: from 216-164-200-77.s1855.apx1.atn.pa.dialup.rcn.com (HELO [83.161.120.155]) ([83.161.120.155]) by smtp01.lnh.mail.rcn.net with ESMTP; 03 Jan 2007 06:56:01 -0500 Message-ID: <vali@example.com> Date: Wed, 03 Jan 2007 06:55:58 -0500 From: Gregg Leichtman <vali@example.com> User-Agent: Thunderbird 83.161.120.155 (X11/20060725) MIME-Version: 1.0 To: vali@example.com Subject: Re: [FWD: [v1.0.4] shale-tiles and release notes (was Re: svn commit: r490857 ...)] References: <vali@example.com> <vali@example.com> <vali@example.com> In-Reply-To: <vali@example.com> X-Enigmail-Version: 83.161.120.155 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5032A9DB07C10D3387066748" X-Junkmail-Status: score=10/50, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090205.459B9830.00AD,ss=1,fgs=0, ip=83.161.120.155, so=2006-05-09 23:27:51, dmn=5.2.125/2006-10-10 X-Virus-Checked: Checked by ClamAV on apache.org --------------enig5032A9DB07C10D3387066748 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Just a suggestion. It would be helpful, to me at least, if you were to include within the release notes one or more snapshot version numbers of standalone Tiles, one or more version numbers of Spring and one or more version numbers of other targeted components that work with Shale with which you the development group believes v1.0.4 appears to work. I realize that items like Tiles in sandboxes are fast moving targets, but it helps us users avoid having to do a lot of trial and error just to find a single combination of components that works. If we have one working set, substituting different components one at a time using trial and error during component upgrades is far less burdensome that not knowing anything about what works together. -=3D> Gregg= <=3D- Rahul Akolkar wrote: > On 12/29/06, Greg Reddin <vali@example.com> wrote: >> > > From: "Rahul Akolkar" <vali@example.com> >> > > Date: Thu, December 28, 2006 4:56 pm >> > > To: vali@example.com >> > > >> > > The above "projected quality" paragraph needs to be updated to >> reflect >> > > the current sentiment. Of the two items in that list, 1.0.4 will >> > > address most of the dialog issues (so I've removed that). >> > > >> > > Someone more familiar with shale-tiles (and changes implied by goi= ng >> > > TLP) should update the above paragraph in the release notes. TIA. >> >> >> >> The TLP hasn't changed the status of Tiles just yet. Tiles will >> still be a >> snapshot for a while because it will take some time to get the TLP >> infrastructure set up. >> > <snip/> > > Thanks, the related bits are in section 1 and 4 of the release notes > -- you're welcome (as is everyone else) to tweak the wording (long, > possibly fragmented URL): > > http://svn.apache.org/repos/asf/shale/framework/trunk/src/site/resource= s/docs/release-notes-1.0.4.html > > > -Rahul > > >> Greg >> >> > --------------enig5032A9DB07C10D3387066748 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFm5nTMcSsEtbyA2cRAo6XAJsHhPpXzPSshs/YHHK3gSUn8dwfiQCfbbUP GqZwOiDoRRfxamVbIIJ1BzI= =lA5m -----END PGP SIGNATURE----- --------------enig5032A9DB07C10D3387066748-- From vali@example.com Wed Jan 03 12:20:57 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 82603 invoked from network); 3 Jan 2007 12:20:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Jan 2007 12:20:56 -0000 Received: (qmail 67622 invoked by uid 500); 3 Jan 2007 12:21:03 -0000 Delivered-To: vali@example.com Received: (qmail 67576 invoked by uid 500); 3 Jan 2007 12:21:02 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 67567 invoked by uid 99); 3 Jan 2007 12:21:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2007 04:21:02 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [83.161.120.155] (HELO MAIL3.DnB.no) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2007 04:20:52 -0800 Received: from cgawe002n.dnbnor.net (int-mail2.dnbnor.no) by MAIL3.DnB.no (Content Technologies SMTPRS 4.3.12) with ESMTP id <vali@example.com> for <vali@example.com>; Wed, 3 Jan 2007 13:20:24 +0100 Received: from CNORCL01E003V.dnbnor.net ([83.161.120.155]) by cgawe002n.dnbnor.net with Microsoft SMTPSVC (6.0.3790.211); Wed, 3 Jan 2007 13:20:21 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [FWD: [v1.0.4] shale-tiles and release notes (was Re: svn commit: r490857 ...)] Date: Wed, 3 Jan 2007 13:20:19 +0100 Message-ID: <vali@example.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [FWD: [v1.0.4] shale-tiles and release notes (was Re: svn commit: r490857 ...) ] Thread-Index: AccvLj3qdTBnoXSGTjGjfUDjkL6hBQAAzXKQ From: <vali@example.com> To: <vali@example.com> X-OriginalArrivalTime: 03 Jan 2007 12:20:21.0313 (UTC) FILETIME=[89ADF310:01C72F31] X-Virus-Checked: Checked by ClamAV on apache.org Hi These are listed in the various profiles in the Maven POM file. Hermod -----Original Message----- From: Gregg Leichtman [mailto:vali@example.com] Sent: Wednesday, January 03, 2007 12:56 PM To: vali@example.com Subject: Re: [FWD: [v1.0.4] shale-tiles and release notes (was Re: svn commit: r490857 ...)] Just a suggestion. It would be helpful, to me at least, if you were to include within the release notes one or more snapshot version numbers of standalone Tiles, one or more version numbers of Spring and one or more version numbers of other targeted components that work with Shale with which you the development group believes v1.0.4 appears to work. I realize that items like Tiles in sandboxes are fast moving targets, but it helps us users avoid having to do a lot of trial and error just to find a single combination of components that works. If we have one working set, substituting different components one at a time using trial and error during component upgrades is far less burdensome that not knowing anything about what works together. -=3D> Gregg <= =3D- Rahul Akolkar wrote: > On 12/29/06, Greg Reddin <vali@example.com> wrote: >> > > From: "Rahul Akolkar" <vali@example.com> >> > > Date: Thu, December 28, 2006 4:56 pm >> > > To: vali@example.com >> > > >> > > The above "projected quality" paragraph needs to be updated to >> reflect >> > > the current sentiment. Of the two items in that list, 1.0.4 will >> > > address most of the dialog issues (so I've removed that). >> > > >> > > Someone more familiar with shale-tiles (and changes implied by going >> > > TLP) should update the above paragraph in the release notes. TIA. >> >> >> >> The TLP hasn't changed the status of Tiles just yet. Tiles will >> still be a >> snapshot for a while because it will take some time to get the TLP >> infrastructure set up. >> > <snip/> > > Thanks, the related bits are in section 1 and 4 of the release notes > -- you're welcome (as is everyone else) to tweak the wording (long, > possibly fragmented URL): > > http://svn.apache.org/repos/asf/shale/framework/trunk/src/site/resources/= docs/release-notes-1.0.4.html > > > -Rahul > > >> Greg >> >> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that the DnB NOR Group cannot accept any payment orders or other legally binding correspondence wi= th customers as a part of an email.=20 This email message has been virus checked by the anti virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * From vali@example.com Wed Jan 03 16:45:10 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 71542 invoked from network); 3 Jan 2007 16:45:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Jan 2007 16:45:09 -0000 Received: (qmail 4113 invoked by uid 500); 3 Jan 2007 16:45:16 -0000 Delivered-To: vali@example.com Received: (qmail 4091 invoked by uid 500); 3 Jan 2007 16:45:15 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 4082 invoked by uid 99); 3 Jan 2007 16:45:15 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2007 08:45:15 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO an-out-0708.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2007 08:45:06 -0800 Received: by an-out-0708.google.com with SMTP id c25so1535775ana for <vali@example.com>; Wed, 03 Jan 2007 08:44:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OgkHXa3axeD74dSuIlCZ/QmU2rfsJPFF8Nyu/Dv4neHoM1udqzwn0y0NHVda+nsHAnCPrDQZB8h+c59wMyjrNCqqMHYhlR/w9lncqYOenO0yscBM8Jhc3yuafPQvr7leTddEwh9wElMADVGpZBkAe2cOJ/495I66RJ/YOsfOO1U= Received: by 83.161.120.155 with SMTP id i15mr4223074huf.1167842684684; Wed, 03 Jan 2007 08:44:44 -0800 (PST) Received: by 83.161.120.155 with HTTP; Wed, 3 Jan 2007 08:44:43 -0800 (PST) Message-ID: <vali@example.com> Date: Wed, 3 Jan 2007 11:44:43 -0500 From: "Rahul Akolkar" <vali@example.com> To: vali@example.com Subject: Re: [VOTE] Release Shale version 1.0.4 In-Reply-To: <vali@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <vali@example.com> <vali@example.com> X-Virus-Checked: Checked by ClamAV on apache.org On 1/3/07, Craig McClanahan <vali@example.com> wrote: > On 1/2/07, Rahul Akolkar <vali@example.com> wrote: > > > > org.apache.shale:shale-apps-parent:1.0.4 > > > As part of my review of the proposed 1.0.4 release (all the sigs match ... > but let's see what happens when I try to *use* this stuff :-), I want to try > building our distribution artifacts. I could build the framework with no > problems -- but trying to build an app fails because this artifact is > (correctly) not available in any repository yet. Thinking about it a bit > more, we aren't officially distributing *source* artifacts for this POM, or > for "org.apache.shale:shale-master:2" either -- both of which you would need > to install if you're trying to build Shale. On the other hand, once the > distribution is voted in and released, the artifacts will be available (but > only if you know to go get them). > > One could certainly argue that, since our source build system is Maven > based, we could expect this to "just work" for our downstream users after a > release. But what about folks who are not "always on" connected to the > Internet? Or folks who need to be able to build Shale, from source, in > Maven's "offline" mode? Maybe we should publish these two POM artifacts as > part of some "source distribution" somewhere, like we do all the other POMs? > <snip/> A m2 bootstrap distro having shale-{master,parent,apps-parent}.pom is a possibility (the mechanics would need fleshing out since they're not in the same source subtree), but that is also no guarantee that a build will just work when there is no connectivity (or for an offline build). For example, the build may not have: * A dependency version we need (workaround: install it manually from shale-framework.zip/lib -- assumes that was downloaded, not just the sample app zip) * A plugin we need (such as gpg with -Prelease, and while its debatable whether using the release profile is a reasonable thing to do, there are probably better examples elsewhere) In my experience, for any sizeable m2 build, I've had to be connected the first time. Ofcourse, thereafter, it may be possible to work offline. Using build tooling that has a notion of central management of artifact metadata (for dependencies and tooling components themselves) implies, IMO, waiving some of our expectations about things working when that (remote) metadata is no longer accessible. > Craig > > PS: I'm not done reviewing the proposed 1.0.4 bits, but things look good > (outside of the issue raised here) so far. > <snap/> No rush, please take your time. -Rahul From vali@example.com Thu Jan 04 03:01:14 2007 Return-Path: <vali@example.com> Delivered-To: vali@example.com Received: (qmail 41452 invoked from network); 4 Jan 2007 03:01:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Jan 2007 03:01:13 -0000 Received: (qmail 59863 invoked by uid 500); 4 Jan 2007 03:01:19 -0000 Delivered-To: vali@example.com Received: (qmail 59773 invoked by uid 500); 4 Jan 2007 03:01:19 -0000 Mailing-List: contact vali@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:vali@example.com> List-Unsubscribe: <mailto:vali@example.com> List-Post: <mailto:vali@example.com> List-Id: <dev.shale.apache.org> Reply-To: vali@example.com Delivered-To: mailing list vali@example.com Received: (qmail 59764 invoked by uid 99); 4 Jan 2007 03:01:19 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2007 19:01:19 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of vali@example.com designates
{'source': 'Apache Software Foundation Public Mail Archives'}