> Well, this is the BIG THINK, I'd love. For 2.0 we should > have big goals, not minor enhancements ;-) And that it > will break backward compatibility? Who cares? It is 2.0, > it may break things.
Don't think so. Yes, we will have things breaking backwards compatibility but we should put enough effort to reduce the number of incompatibilities to a minimum. We have to think about the numerous users out there and the projects depending on velocity. "Old" templates should work with little unavoidable changes (rare cases dealing with floats for instance). Improvement: Yes. Enhanced featureset: Yes. But no new product. Especially, I would not fiddle around with the current whitespace- handling (though it is inconsistent in some cases...) . I'd rather introduce some kind of filter-mechanism like a BodyTag in JSP (repeating myself, eh? :) BTW: "We" always means all the developers that will contribute to the current and next version. Geir, after putting 1.3.1 together, it would be great to create a feature list and to put priorities on it. Has anybody any idea how to organize this process? I mean, everybody has dozens of ideas in his / her head and I tend to think that we won't manage to get a solid feature-list / development plan while discussing over several mailinglist-threads. And in the end we would need a process that results in decissions (some kind of voting or (worst case :) Geir says what's on the list and what's not - kidding!). Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
