> i think we should generally refer to the Apache Velocity TLP as > "Apache Velocity" and put no further nouns into it. If we need a > generic noun as a synonym, i'd stick with "project" as that is how the > ASF views us collectively.
+1 for "Apache Velocity". Also, subprojects can be called "components". > > > > --> What's the latest version? > > > > > > +1. Latest Version of what? We already have three sub projects. > > > > What about including validation/compatibility/voting steps for > > subprojects, so that a particular version of a subproject is officially > > linked with every engine release? Hence, there would be a "Velocity > > package" version, the same as the core, and newcomers can avoid dealing > > with subproject versions. Advanced users who want to mix versions can > > fetch infos on subprojects pages and use subversion. > > I think this is a great idea. Not a high priority, but definitely > something i'd like to work on once we get the TLP move completed and > Velocity Engine 1.5 and VelocityTools 1.3 out the door. I just realized there are tons of projects on Apache that use the same standardized menus in the "project documentation" section. We don't need to follow the standard, but the "dependencies" and "reactor dependency convergence" pages look quite interesting. I didn't dig too deep but it seems those pages are generated by Maven using POM files, am I right? Claude --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
