Sanjiva Weerawarana wrote:
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 :) !!
I will help as u need it!
Thanks,
Sanjiva.
On Sat, 2005-08-27 at 22:34 +0200, Rony G. Flatscher wrote:
Regards !!
Sanka
Hi there,
looking through the Apache-BSF site via the given links gives the
impression, as if the technology has not been changed since three years,
which is not true at all. E.g. there is no "current build", nor an
update on the HTML files pointing to new languages which support BSF
(like ooRexx, JLog etc.).
Also, officially BSF is in "beta" and not yet in production. Before we
can officially tackle a JSR-223 compliant implementation of BSF, we
would need to create a BSF 2.0 production version.
Short of having any working knowledge about the necessary Apache-style
steps, I would like to ask anyone in the know what the next steps would
be (administrative wise).
Regards,
---rony
P.S.: W.r.t. then next version, one thing I could offer (if there is
interest at all) is to "seal off" all of the Java code I created to
support the scripting engines REXX As that scripting language only deals
with strings as datatype, all the interfaces into Java are string based
(even those interacting with single-/multidimensional arrays of any
type). This means that probably any programming language that is able to
deal with strings, will be able to take advantage of that infrastructure.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
