I think this is a good idea. Also, not so much part of the PyPy 1.0 release, but I'll have the command line compiler done this weekend. I'll host to source on my servers and email the list when it's up.
Paul On 2/1/07, Carl Friedrich Bolz <[EMAIL PROTECTED]> wrote:
Hi all! Michael Hudson wrote: > Task Planning > ============= > > This topic is to collect tasks to be done for the release and divide them > among people. Some tasks that we could think of: > > * work out a timeframe for jit usefulness > * fix llvm(?) > * test pypy-cs, run benchmarks. > * windows testing! > * documentation!!! > * pypy.net > * object optimizations (WP6) > * release announcement > * improve getting-started > * transparent proxies > * security prototype > * make build-tool useable > * polish js backend? Another task that I came up with: we should try to document our config options. Maybe not the more obscure ones, though :-). Imo this is quite important, since the list of options is very big and makes it hard to find what you are looking for. There should also be more "high-level" options like --allworkingmodules and --faassen (which should be renamed for the release, I guess :-) ). And maybe a small "guide through the option jungle" or something like this. Cheers, Carl Friedrich _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
_______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
