On Tue, Apr 6, 2010 at 3:09 AM, Claude Brisson <[email protected]> wrote: >> Tools 2.0 has been languishing in beta due to unfinished docs. No >> one has stepped up to help and really the docs aren't that bad, so i'm >> done with that. Expect a CFV for Tools 2.0 final soon. Object >> quickly if you have other ideas. :) > > I'll try to spend sometime on the docs this week - but anyway, let's > push it out!
that would be cool. i'm going to tentatively plan to roll out the test build on Saturday. i hope to find a couple hours to fix VELTOOLS-124 and drop in the new tools by then. >> In other Tools news, there are a few unpublished tools i've been >> sitting on that are in various states of completion/polish. I had >> intended them to be part of a 2.1 release, but that now feels too far >> away to consider. As such, i intend to add them to 2.0, while >> somehow denoting them as "beta" level. Really, we are overdue for a >> means of classifying tools, as they all have various levels of support >> and polish. Obviously, i will mention their status in their docs and >> leave them out of the default tools.xml files, but i was wondering if >> i should take it further. Perhaps, by putting them in a "beta" >> package like org.apache.velocity.tools.generic.beta.FooTool? Any >> thoughts on this? > > The most convenient for tools candidates that still need some work is > probably to have them sit in the svn tree with their final package names > but under a "beta" or "sandbox" or "experimental" subdirectory. We can > put this subdirectory in the released source tree and mention them in > the docs, interested people will be able to use them and help completing > them. And 2.1 can come out not that far after 2.0, you're not alone :-) Hmm. That would only be convenient if there were an ant task to build those, which i suppose could be done. But only one of the two i intend to could be called experimental; the other is one i already make significant use of and deserves better, i think. I just haven't time to improve the docs or make a demo page in the showcase, and i'd rather not add a new "final" feature between beta4 and final releases. Also, a new directory and task(s) support is extra work. > By the way, among the new (or soon new) commiters, who is using the > tools subproject and might give some help? Byron? Jarkko? Christopher? I know Christopher has used tools. >> Anyhow, i will continue to be on the lists (even if my answers are >> more delayed than before) and will certainly be able to help walk >> people through release processes and such, but in general, i am less >> available than before. Jarkko, this especially means that we need to >> finalize your committer status so you can commit your own patches. > > > Thanks for all the time you gave so far to our community! > > > Claude > > > > --------------------------------------------------------------------- > 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]
