Return-Path: 
 <commons-dev-return-82046-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 37325 invoked from network); 20 Dec 2005 22:27:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 20 Dec 2005 22:27:15 -0000
Received: (qmail 57090 invoked by uid 500); 20 Dec 2005 22:27:13 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 57033 invoked by uid 500); 20 Dec 2005 22:27:12 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 57022 invoked by uid 99); 20 Dec 2005 22:27:12 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2005 14:27:12 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of rahul.akolkar@gmail.com
 designates 64.233.162.207 as permitted sender)
Received: from [64.233.162.207] (HELO zproxy.gmail.com) (64.233.162.207)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2005 14:27:11 -0800
Received: by zproxy.gmail.com with SMTP id 9so3069nzo
        for <commons-dev@jakarta.apache.org>;
 Tue, 20 Dec 2005 14:26:51 -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=CeERuVaf86x9wsuuadu85WgCU+cTjP45b3KFUXcbOlPSr1kQp1VxdTB8KI/pnQfr4tXMcx4CrC6p3bg3hwOvNFLeRiDzPURaeWDOxSmRVM5moJ4iGZtXx2fTuoutQEb4e6WGGJHo14Oh/G2baUIL16VDZVmDicSVL1zvds2QxQM=
Received: by 10.37.21.25 with SMTP id y25mr37219nzi;
        Tue, 20 Dec 2005 14:26:50 -0800 (PST)
Received: by 10.36.252.67 with HTTP; Tue, 20 Dec 2005 14:26:50 -0800 (PST)
Message-ID: <ce1f2ea80512201426u2e43d4c1j890c5cebc0fce828@mail.gmail.com>
Date: Tue, 20 Dec 2005 17:26:50 -0500
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [scxml] Release schedule?
In-Reply-To: 
 <8E6E1270FFE02641987EC98FDA5535A0CDC07C@LDNPCMEU303VEUA.INTRANET.BARCAPINT.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: 
 <8E6E1270FFE02641987EC98FDA5535A0CDC07C@LDNPCMEU303VEUA.INTRANET.BARCAPINT.COM>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 12/20/05, Joe.Toller@barclayscapital.com
<Joe.Toller@barclayscapital.com> wrote:
> Hi,
>
> Is there a proposed release date for v1.0 for the scxml stuff?
>
<snip/>

Thanks for the nudge :-) An hour or so ago, I added a brief roadmap to
a Commons SCXML 1.0.0 release on the Apache wiki. That is here:

http://wiki.apache.org/jakarta-commons/SCXML/1.0.0ReleasePlan

The actual issues reported in the "Bug Review and Fixes" section
shouldn't take more than a week to resolve (usual holiday season
tolerances apply).

The steps to be executed here on are as follows:
1) Get feedback from Commons developers before calling a sandbox
graduation vote (I'll begin this thread later this evening or
tomorrow)
2) Call a vote to graduate out of sandbox
3) If (2) passes, we will have an unknown number of release
candidates, until no issues are reported against those
4) When (3) is done, we will proceed by calling a 1.0.0 release vote,
which again needs to pass

While it is not possible to give any firm date (you'll find this the
common theme in most Apache projects -- it is hard to predict the
timing on most releases), my best case estimates put the actual
release towards the end of Q1 '06 (which matches up with Jim's
estimates as well).


> And does the current build / will v1.0 implement the whole scxml
> specification, or are there some bits missing.
>
<snap/>

See release plan for known issues (these will be resolved). 1.0.0 will
not implement any functionality dealing with external namespaces. For
example, CCXML constructs as shown in some of the examples in the
specification will have to be made by suitable EventDispatcher
implementations (EventDispatcher is a Commons SCXML interface), these
will not be provided out of the box.


> Apologies if I'm asking questions that have been asked before - can't
> find this info on the web tho.
>
<snip/>

Quite the contrary, thanks again for nudging me into motion.

-Rahul


> Many Thanks!
> Joe
>
<snap/>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org