On 10/28/07, Claude Brisson <[EMAIL PROTECTED]> wrote: > Le vendredi 26 octobre 2007 à 11:38 -0700, Nathan Bubna a écrit : > > Hey Velocity folks (and especially VelocityTools folks), > > > > VelocityTools 2 is working well and pretty much ready for another > > alpha release, but it's not moving as quickly as i'd hoped. In the > > meantime, VelocityTools 1.x has a few unreleased features and fixes > > that are overdue for release. This has created something of an > > impasse for me, and i'd love your input on a few things. > > Why not target a beta release? I'm already using it and quite happy with > it.
i'm not comfortable attaching the word beta to a 2.0 release whose docs are almost completely unchange from the last 1.x release. i do agree the code is beta-quality, but the 2.0 docs are truly alpha. > > I have scratched my main personal itches for VelocityTools 2, but > > there are still some things i was planning to have before we release > > 2.0, specifically updated docs, updated showcase examples, Tiles2 > > support and complete caching for VelocityViewTag. Updating the docs > > and showcase examples are firm requirements for me, but the other two > > features are not things i personally need. > > Me neither... > > > So, question one, what are > > your thoughts and feelings on the use/importance of: > > > > Tiles2 support? > > caching for the VelocityViewTag? > > something else i'm forgetting? > > > > Now, in regards to VelocityTools 1.x. VelocityTools 2 is almost > > completely compatible (though with much deprecation) with > > VelocityTools 1.3. Second question: what should we do with the 1.x > > series? > > +1 to Will suggestion: release a 1.3.1 and inform users that they should > move to 2.0. i'm ok with that. if anyone out there objects, speak up soon! :) > > stop now and focus on getting 2.0 out and easing transition from 1.3 to 2.0? > > release the trunk as 1.4 and be done with it? > > release the trunk as 1.3.1 (since there's not a ton of new stuff) and > > be done with it? > > continue developing both 1.x and 2.x in parallel? > > some other option? > > > > Finally, my third question, will you help? Claude? Marino? > > Christopher T.? Christopher S.? Will? I know you guys are out there! > > :) And yeah, i know life is busy, and i've been charging madly ahead > > with 2.0 development, making it hard to jump in. But, 2.0 has largely > > gelled at this point, and i could REALLY use some help with filling > > out tests and updating documentation for it (which are all fairly easy > > for multiple devs to do in parallel). > > I'll do my best... in terms of documentation, I'm searching for a way to > give more visibility to the VelTools library an an efficient alternative > to framework based approaches for small webapp projects. I've got the > feeling that newcomers may perceive VelTools at first as a bunch of > unordered goodies for Velocity, which it is definitely not. yeah, that would be great. feel free to experiment! i'll chime in as i think of things. > > Also, i'm seriously lacking in > > motivation to get the latest stuff in 1.x documented and released, > > since i'm just using 2.0 now. If any of you guys are still invested > > in 1.x and interested in seeing another release (or more), now is the > > time to speak up and help out. I know i told someone months ago that > > i'd rattle off another 1.x release, but i'm just not sure it's worth > > it at this point. Sorry. :( > > > > Thanks for reading! Please let me know your thoughts and seriously > > consider helping out. Oh, and if you want to help out with > > documentation for 2.0, i have actually written quite a bit, but it is > > all plain text. I mostly need help either integrating it into the old > > DVSL doc system or (if you're feeling ambitious) Henning's new > > Maven-based doc system that Engine is using now. > > Plain text is much more than nothing! :) when code/docs/whatever exists in only one digital location, it is just a small step away from nothing. working to get the text on the wiki for more permanency... > > > > peace, > > 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]
