Martin -- First off, I apologize since the title of the announcement was inappropriate and I'll amend it. In hindsight, I agree that the word "release" has a very specific connotation.
<quote>Once a new project submission is included in the sandbox, it is the responsibility of the submitter to promote its availability to various mailing lists such as taglibs-user. The goal is to use this evaluation period to "kick the tires" and rally support for the eventual inclusion of the project within Jakarta Taglibs.</quote> [ http://jakarta.apache.org/taglibs/newprojectsubmission.html ] I interpret that as: a) Having mailing list discussions that drive changes/enhancements to the taglib b) Periodically communicating changes in the taglib, new features, tags etc. to the dev/user community The announcement is clearly part of (b), although it should have simply read "[ANN] Recent changes to the RDC sandbox taglib" (same change in the first paragraph of the body of the email). Unless you or others have more feedback, I will assume these are the only changes and send a clarification note to the users list in 12 hours. -Rahul On 4/25/05, Martin Cooper <[EMAIL PROTECTED]> wrote: > I couldn't find any written rules on releases from Taglibs, but I've > always assumed that the rules for Taglibs Sandbox were the same as, or > similar to, those for Commons Sandbox. If that's the case, then a taglib > cannot be released from the sandbox, and must be promoted out first, by a > vote of Jakarta PMC members. > > Further, regardless of the Taglibs Sandbox rules, no taglib, or other ASF > component, can be released without a vote of the relevant PMC. As far as I > can determine, there has been no vote for a beta release of RDC. > > -- > Martin Cooper > > > On Sun, 24 Apr 2005, Rahul P Akolkar wrote: > > > The RDC sandbox taglib [ > > http://jakarta.apache.org/taglibs/sandbox/doc/rdc-doc/intro.html ] has a > > new features beta 1.0 release. > > > > Major Changes: > > 1) Defining Custom Event tuples - It is possible to leverage VoiceXML > > support for user defined event (name, grammar, handler) tuples. These > > tuples can be conveniently added to the RDC configuration files. > > 2) Dialog Context Switching - A recipe for switching dialog contexts using > > the RDC framework i.e. having the ability to leave a task (dialog) > > unfinished, initiate and complete another task and then come back to the > > earlier task, has been demonstrated. > > 3) Multi-channel amazon application - This sample application uses the > > Amazon Web Services to provide users with a Small Device GUI -or- Voice > > User Interface for browsing and buying music albums [ sample applications > > are available in rdc-examples.war ] > > 4) More documentation in rdc-doc.war [also available online at: > > http://jakarta.apache.org/taglibs/sandbox/doc/rdc-doc/index.html ] > > > > New RDC Tag: > > 1) <rdc:pause> - Pauses until the user resumes the application. > > > > Modified RDC Tag: > > 1) <rdc:struts-submit> - Added the ability to selectively clear some or > > all of the RDC session state. > > > > Sandbox source is here [ > > http://cvs.apache.org/builds/jakarta-taglibs-sandbox/nightly/src/ ] > > RDC binaries are here [ > > http://cvs.apache.org/builds/jakarta-taglibs-sandbox/nightly/projects/rdc/ > > ] > > RDC revision history is available here [ > > http://jakarta.apache.org/taglibs/sandbox/doc/rdc-doc/changes.html ] > > > > -Rahul Akolkar > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
