Tavis Rudd <[EMAIL PROTECTED]> wrote: > I think we should aim for a 1.0 release with full docs and > a stable syntax for the end of July. Until then how about > we just keep on incrementing the 0.9.# numbers until we > think we're ready, then have a 2 week freeze period? The implementation can be easily changed after 1.0, but the syntax can't. Considering there's still lots of addition of directives, and changing of the semantics of directives, freezing it any time soon will mean a inelegant syntax with lots of vestigial constructs. One alternative would be to make TS more future-compatible, but versioning the input. I remember browsing some discussion on the Python lists. One person noted a system that had a version at the top the file, and would sometimes edit the code in-place or put in backward compatible features. This way the new syntax could delete things, while the old syntax could still work. Actually doing that support might be hard work -- but it's hard work you can put off for a while, because all that's required now is putting a version at the top. Anyway, I think you shouldn't even *talk* about a freeze date until you really know what you are working towards. I think that's still up in the air for both of the important parts of Cheetah -- the syntax, and the interface. 1.0 means these shouldn't change for a while. Ian _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/webware-devel
