+1, great work! -- Claude
----- Original Message ----- From: "Malcolm Edgar" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <[email protected]> Sent: Friday, October 21, 2005 1:30 AM Subject: Re: [vote] VelocityTools 1.2 release plan +1 On 10/21/05, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Ah, sorry. +1. WILL ----- Original Message ----- From: "Nathan Bubna" <[EMAIL PROTECTED]> To: "Velocity Developers List" <[email protected]> Sent: Thursday, October 20, 2005 1:10 PM Subject: Re: [vote] VelocityTools 1.2 release plan On 10/20/05, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > sounds fabulous. that's a +1, right? :) > Were you planning on including veltag in the Velocity Tools distribution? no, not yet. after 1.2 is out, i'll look into pulling it over and sprucing it up for a 1.3 or 2.0 tools release (whichever turns out to be next). > WILL > > ----- Original Message ----- > From: "Nathan Bubna" <[EMAIL PROTECTED]> > To: "Velocity Developer's List" <[email protected]> > Sent: Thursday, October 20, 2005 12:24 PM > Subject: [vote] VelocityTools 1.2 release plan > > > hey folks, > > it's been a long time since VelocityTools 1.1 final was released. in > the meantime, we've made many improvements and fixes, and so has the > Struts project. since both Struts and Velocity are gearing up for big > evolutionary releases (Struts 1.3 and Velocity 1.5) with growing > rumors of revolution (Struts Ti? Clarity? Velocity 2?) on the horizon, > i think it is high time we got VelocityTools 1.2 out the door. The > bug list is clear, and i'm eager to get this released. > > Major changes in this release are: > - Support for Struts 1.2.7 > - Added support for tool configuration parameters in toolbox.xml > - VelocityView (and VelocityStruts) now use a VelocityEngine instead > of the Velocity singleton > - Many new tools (AbstractPagerTool, ValueParser, SortTool, ListTool, > BrowserSnifferTool, EscapeTool, and Alternator) > - Many improvements to existing tools (DateTool, MathTool, etc.) > - Many bug fixes > - And other miscellaneous improvements... > > My personal take on the state of the codebase is that the code is > ready, and i've cleaned up and prepared the documentation. The only > hang up is that one bum JSP in the velstruts example app that i wrote > about this morning. At this point, i've put more time than i should > into getting this ready. If no one can step forward with a fix for > that in the next few days, I will just excise that page from the app. > It is not an essential piece. > > This means that within a few days, we will be 100% ready to go (at > least in my opinion). So, i'm asking for support for the following > release plan. > > VelocityTools 1.2 Release Plan: > 1. Call for a vote on this plan and wait a few days for results. > 2. Build a VelocityTools 1.2-rc1 and put it up at > http://people.apache.org/~nbubna/ > 3. Announce the release candidate on the Velocity, Struts, and > announcements lists. > 4. Give people a couple weeks to test it. > 5. If no issues are found with it: > a. Call for vote to final release, wait a few days for results, > then notify PMC > b. Rebuild as VelocityTools 1.2 and upload for mirroring and all > that > c. Update VelocityTools website docs > d. Announce final release to the various lists, and update > various news pages > 6. If issues are found, fix them ASAP and go back to step two. > > -------------------------------------------------------------------- > Vote: VelocityTools 1.2 release plan > [ ] +1 I fully support this plan. > [ ] +0 I like it, but... > [ ] -0 I'm not sure this is a good idea because... > [ ] -1 I am against this because... > -------------------------------------------------------------------- > > My vote is, of course, +1 :) > > -nathan > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- 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]
