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 flamefew@gmail.com designates
 66.249.92.170 as permitted sender)
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=JT9HxhHnY+tj110xYCXFjkRE7tsUI9fZFTG5aZIBgw0KKGAAK3At+zepSmIFsPElwufH6mJFPzIFTOvACA2h4kZvrvdOdAZ3UvCAN5ifN2/i1Cl4wBPYiPFowdzMnd/SANJSR2/36VfruYRn2ufCrou9j/4HcrqWd2i76tmstPc=
Message-ID: <31cc37360607222349y4fce800fk7ea0660b4e95fc12@mail.gmail.com>
Date: Sat, 22 Jul 2006 23:49:37 -0700
From: "Henri Yandell" <flamefew@gmail.com>
To: "Bean Scripting Framework developers" <bsf-dev@jakarta.apache.org>
Subject: Re: Release Plans?
In-Reply-To: <44B6BFCC.2070003@wu-wien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5ea470920602271033p27d0cfe9v921d5c1bc40153f9@mail.gmail.com>
	 <44035FFC.1020307@wu-wien.ac.at>
	 <5ea470920607130741h6740eb78i28db32bd02cde0cb@mail.gmail.com>
	 <44B67574.8080701@wu-wien.ac.at> <44B679A8.7000006@gmail.com>
	 <44B69022.7060602@gmail.com> <44B6BFCC.2070003@wu-wien.ac.at>

On 7/13/06, Rony G. Flatscher <Rony.Flatscher@wu-wien.ac.at> wrote:
> Hi Sanka,
>
> >>>> The BSF sources are up-to-date, but the binary distribution (and the web-site itself) is not. :-(
> >>>>
> >> Rony, can you state what is needed to be done so that we can get this going? (fixing the website first may be)
> >>
> >
> > I mean a list of items that need to do so that we can cut the release ..
> >
> Hmm, good question. I would suggest to consider:
>
>     * automatic builds, if the source got changed (or even an automatic
>       daily build) to create a binary distribution off the latest
>       code-base for users,
>
>     * update the supported languages; it seems that there is a directory
>       tree with updated information that is not used for the Jakarta BSF
>       WWW site at the moment (like the JLog or ooRexx infos),
>     * maybe there are Apache Jakarta policies in place which would
>       influence the setup to use for both, which should be taken into
>       account?
>
> Hope that helps a little bit, and thanks a lot for your stepping
> forward, Sanka!

Jakarta Commons components all link to documentation on how to do
releases. It's commons-centric, but I bet it's 95% relevant to BSF.
Let me know if I can help - give me a private email to flag the thread
in my inbox as I don't check the BSF list very often.

http://jakarta.apache.org/commons/releases/index.html

There's a Commons nightly build script that could conceivably be
extended to handle BSF.

Hen

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