Geir Magnusson Jr. wrote:
Here's what I think we should do to get code out and contributions in :
1) I'll branch the 1.3.1rc2 tag on the 1.3 branch and to do a 1.3.1 release. I think it's important to release that as-is, pre the patches from Dan.
I'm +1 for a 1.3.1 release, with the prospective of opening the road for some of the requested features on upcoming releases.
2) the recent commits on 1.3.1rc2 will go as a 1.3.2, to RC and get it out because Dan committed those for a reason, and I'm sure he needs a release of it.
3) the current head will become 1.4rc1 and move that as our primary release target to get a v1.4 out there.
4) patches go into head, which will be 1.5-dev
For further releases it would be an advantage to have an updated status page to *know* what the desired features are, to allow contributing in areas where appreciated. Quoting/updating the list presented by Peter (pero):
"Hot" issues have been:
- Number support (Currently you can only cope with Integers)
- Map support (Currently only lists)
- Whitespace-Handling
- "local scope" for context-variables (very useful in Macros)
- More a bug: Macro-Reloading behavior and (perhaps) Macro-Overloading
- Macros with a body
- Escaping fixes, possibly redefining syntax, e.g. ${#} instead of \#
- Quote escaping: "A string containing an embedded quote: "" "
- Multi-line #set directives, Strings and ArrayList definitions
- extracting VelocityServlet from core
- tools, directives an VM contributions
- ... open for additions/modifiationsStill we can KISS, if something is elegantly done with tools or other means, it sould be documented (FAQ) and tools located in the contrib section.
-- :) Christoph Reck
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
