Return-Path: 
 <dev-return-1272-apmail-shale-dev-archive=shale.apache.org@shale.apache.org>
Delivered-To: apmail-shale-dev-archive@locus.apache.org
Received: (qmail 55896 invoked from network); 23 Jan 2007 18:56:16 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 Jan 2007 18:56:16 -0000
Received: (qmail 58095 invoked by uid 500); 23 Jan 2007 18:56:22 -0000
Delivered-To: apmail-shale-dev-archive@shale.apache.org
Received: (qmail 58059 invoked by uid 500); 23 Jan 2007 18:56:22 -0000
Mailing-List: contact dev-help@shale.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@shale.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@shale.apache.org>
List-Post: <mailto:dev@shale.apache.org>
List-Id: <dev.shale.apache.org>
Reply-To: dev@shale.apache.org
Delivered-To: mailing list dev@shale.apache.org
Received: (qmail 58050 invoked by uid 99); 23 Jan 2007 18:56:22 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2007 10:56:22 -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 rahul.akolkar@gmail.com
 designates 209.85.132.240 as permitted sender)
Received: from [209.85.132.240] (HELO an-out-0708.google.com) (209.85.132.240)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2007 10:56:13 -0800
Received: by an-out-0708.google.com with SMTP id c25so703464ana
        for <dev@shale.apache.org>; Tue, 23 Jan 2007 10:55:52 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=F1iAc+53MbBhUpVchGR8G6tRFDsaFOo392zrjy2IvLliXyJg6U5dQ8KDV5vO60RbNsMG9fdhjw2z04Zu8VNh09lPctAdetEAKFmrG+euwN8fVuF5kuBQdODvDlqEK4YNZj5aokpK1rUa31d9OxCauvzNDzGijFqCQkTMROd8/nQ=
Received: by 10.114.13.1 with SMTP id 1mr59454wam.1169578551971;
        Tue, 23 Jan 2007 10:55:51 -0800 (PST)
Received: by 10.114.208.15 with HTTP; Tue, 23 Jan 2007 10:55:51 -0800 (PST)
Message-ID: <ce1f2ea80701231055y69936c8bg4ebae8325b16c89e@mail.gmail.com>
Date: Tue, 23 Jan 2007 13:55:51 -0500
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: dev@shale.apache.org
Subject: Re: [ANNOUNCEMENT] Apache Shale 1.0.4 released
In-Reply-To: <71235db40701231049x5126ecb1q68b6048cab99fbcb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ce1f2ea80701231022q1ad90c98of27b1873375f1da8@mail.gmail.com>
	 <71235db40701231049x5126ecb1q68b6048cab99fbcb@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

On 1/23/07, Matthias Wessendorf <matzew@apache.org> wrote:
> that contains the bug I fixed,
> are we providing a 104_1 ?
>
<snip/>

Nope, those are the bits we voted on for 1.0.4. I think you are asking
about SHALE-394, that will be available in subsequent releases (next
in 1_0_X line is  1.0.5 ATM).

We should discuss whether having bugfix releases for individual
modules makes sense (so having a shale-view 1.0.4.1, rather than a
framework 1.0.5 in this case).

-Rahul


> .M
>