[pypy-svn] r20249 - pypy/dist/pypy/doc/weekly

[mwh at codespeak.net]

Author: mwh
Date: Fri Nov 25 18:45:10 2005
New Revision: 20249

Modified:
   pypy/dist/pypy/doc/weekly/index.txt
   pypy/dist/pypy/doc/weekly/summary-2005-11-25.txt
Log:
more this week in pypy stuff -- i'd like to send this out, so please proofread
:)



Modified: pypy/dist/pypy/doc/weekly/index.txt
==============================================================================
--- pypy/dist/pypy/doc/weekly/index.txt	(original)
+++ pypy/dist/pypy/doc/weekly/index.txt	Fri Nov 25 18:45:10 2005
@@ -57,8 +57,8 @@
    - LLVM progress
    - Sprint preparation
    - PyPy spreads
-   - Whither pypy-sync meetings?
    - Resource consumption
+   - PyPy at conferences
 
 .. _`Week ending 2005-11-04`: summary-2005-11-04.html
 .. _`Week ending 2005-11-11`: summary-2005-11-11.html

Modified: pypy/dist/pypy/doc/weekly/summary-2005-11-25.txt
==============================================================================
--- pypy/dist/pypy/doc/weekly/summary-2005-11-25.txt	(original)
+++ pypy/dist/pypy/doc/weekly/summary-2005-11-25.txt	Fri Nov 25 18:45:10 2005
@@ -21,31 +21,38 @@
 SomePBC-refactoring
 ===================
 
-We attacked the RTyper quite a lot.
+We attacked the RTyper quite a lot, which meant staring at some of the
+most obscure code in the codebase, and made substantial but incomplete
+progress (currently about 60% of the rtyper tests pass).  We're
+optimistic that the majority of work is done on the branch, but there
+may be many strange details to cope with before translate_pypy runs
+again.
 
 
-LLVM progress
-=============
+Sprint Preparation
+==================
 
-Richard (nearly?) implemented threading in the LLVM backend.
+The next sprint is only two and a bit weeks away -- it's definitely
+time to be buying flights and booking accomodation if you're going to
+be there :)
 
 
-Sprint preparation
-==================
+LLVM progress
+=============
 
-Göteborg approaches.
+Richard implemented threading in the LLVM backend, bringing another
+feature that was previously pypy-c only in.  Stacklessness next?
 
 
 PyPy spreads
 ============
 
-Christian consulted in America.
-
-
-Whither pypy-sync meetings?
-===========================
-
-The weekly pypy-sync meeting singularly failed to happen this week.
+Christian returned from America where he'd been consulting for a
+company implementing some systems in RPython which had been
+implemented in Java, and after some effort beating the Java versions
+for performance.  This company had found out about PyPy and RPython
+from reading our mailing lists -- a nice example of how open
+development processes can work (and even make you money!).
 
 
 Resource consumption