On Tuesday 02 April 2002 06:55, you wrote: > Now that 0.7 is out, I think it's high time that we moved Webware > in the direction of a 1.0 release. What things still need to be > done?
In order of priority: - completely automated test suite, that is easy to add new tests to - distutils support, remove ability to run straight from the install dir, and remove need to run makeAppWorkingDir. - a semi-automated release cutting script, that 'cvs up's, updates version numbers, runs the automated test suite, presents the release manager with a summary of all the @@ comments in the source tree and a form to add the release notes, builds the docs and the release tarball, does a dummy install of the tarball and runs the test suite from it, commits the changes to the cvs and adds a new tag, uploads the tarball file to upload.sf.net, runs an automated https session to log the release manager into sf and post the new release, sends a release email to webware-discuss/webware-announce/comp.lang.python, and updates the vaults of parnassus. A goal could be for it should take no more than an hour to cut a beta release. - documentation (formated in either xml-docbook or LaTeX) - better handling of config settings: - refactored to use the wrapper pattern, in which each class is given its settings from the 'Launcher' wrapper instead of having to go and get them. - better config file syntax (pure python or the one used in WebwareExpRefactoring) - ability to provide local subclasses of core classes such as Application - a better logging framework: - separation of error reporting from error logging - based on either Sacha's LoggingKit or PEP 282 (http://python.sourceforge.net/peps/pep-0282.html) - ability for multiple Webkit process to write to the same log (syslog, NT event log, or something similar but Webware specific) > The only item I feel is essential is to write reasonably complete > automated tests. I'd like to be able to sync to the tip of CVS and > run a single command to fully test every Webware component. I agree, this absolutely essential. See the automated testing framework in the experimental refactoring of Webware I've been working on (http://webware.colorstudy.net/twiki/bin/view/Webware/WebwareExpRefactoring). The most difficult and labour intensive part of this is being able to auto-load, run, and shutdown a WebKit process. This requires a builtin http server and a simple mechanism for controlling the config settings. I refactored the configuration mechanism and made it so all settings can be fed into the process via a pickled dictionary. For testing, this is way simpler than having to write each config file separately. > But in my opinion, it's only the lack of automated testing that > really prevents us from being at a 1.0 level. That and distutils support. Cheers Tavis _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
