Mailing-List: contact bsf-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Bean Scripting Framework developers" <bsf-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of ssanka@gmail.com designates
 64.233.184.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=jGHlMCoje3gzu7jSYUs86r6WFB9OQRrk2p+NmtFuR6lhSgVBQy7h1/y9iDSCDuPan2cF9xyeA1QpJOAJ7iZeKpfvIk4zAE86HnAeMsqrc69/ieFFIKCXBF0S9+S+Dn6OT7NdjOg6KYoOFMOXFe1KfbFMAK1/Emk0p5AnhTZgL5o=
Message-ID: <431755BA.1040008@gmail.com>
Date: Fri, 02 Sep 2005 01:25:46 +0600
From: Sanka Samaranayake <ssanka@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Bean Scripting Framework developers <bsf-dev@jakarta.apache.org>
Subject: Re: Keeping the Apache-BSF site (and downloads) really up-to-date
 ?
References: <4310CE43.3000302@wu-wien.ac.at>
 <1125389503.9058.24.camel@localhost.localdomain> <43152459.9080107@gmail.com>
 <4315D899.60902@wu-wien.ac.at>
In-Reply-To: <4315D899.60902@wu-wien.ac.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Rony G. Flatscher wrote:

> Hi Sanka,
>
>>> Basically .. let's get a beta ready of the BSF 2.3 family and then 
>>> put it out.
>>
>>
>> +1!
>>
>>> There's a process - need to get approval from the PMC but they
>>> don't usually second guess the committers and go thru the release
>>> process.
>>> Someone needs to become release manager and write a release plan
>>> (basically an email listing what we intend to release and when etc.
>>> etc.). We vote on it and then we do the approval stuff.
>>>
>>> Are you able to run the process?
>>
>>
>> +1! -- lets appoint Rony as the release manager for this project  :) !!
>
>
> :)
>
> Will be off for a few weeks (see other post), 

B-) !!

> but maybe, if everyone helps together we can plan to get BSF GA in 
> October out the door, then look at JSR-223, if it has stabiized and 
> make BSF 3.0 as an opensource implementation of JSR-223 available as a 
> beta, trying to get the BSF 2 engines pluggable into it one way or the 
> other.

+1! sounds good to me !!

>
> Regards,
>
> ---rony
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
>
>
Sanka


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