Author: hpk
Date: Mon Feb 5 22:16:33 2007
New Revision: 37983
Modified:
pypy/extradoc/minute/pypy-sync-2007-02-02.txt
Log:
some clarifications/reformulations from my side
Modified: pypy/extradoc/minute/pypy-sync-2007-02-02.txt
==============================================================================
--- pypy/extradoc/minute/pypy-sync-2007-02-02.txt (original)
+++ pypy/extradoc/minute/pypy-sync-2007-02-02.txt Mon Feb 5 22:16:33 2007
@@ -39,7 +39,7 @@
sandboxing. According to Armin it is a major effort to clean up all these areas and
get a good level of documentation.
-At this point the meeting side-tracked into discussing the state of the JIT and
+At this point the meeting we started discussing the state of the JIT and
the next steps in this area and the general question how to approach development
during the rest of the EU funding. According to Armin it is expected that the
JIT starts producing non-horrible code "any day or week now". Since the
@@ -58,14 +58,15 @@
interesting features in PyPy even without the JIT working. Then the discussion
moved to the expectations of the EU reviewers. The reviewers we had at the last
review meeting were not too interested in the JIT but more in things like
-aspects, constraint and logic programming. The state of PyPy in these areas is
-unclear.
-
-After a lengthy discussion about what is needed to pass the EU review, we got
-back to time planning. Armin proposed to check the state of the JIT again on
-Monday to see how far it improved over the weekend. It was also decided that we
-would meet again on Wednesday, February 7th at 11.00 to discuss the release work
-distribution in detail.
+aspects, constraint and logic programming. However, the current state
+of PyPy in these areas is not completely obvious to the people
+attending the meeting.
+
+It then was agreed to check the state of the JIT again on
+Monday to see how far it improved over the weekend. It was
+also decided that we would meet again on Wednesday, February
+7th at 11.00 to discuss the release work distribution in
+detail.
Task Planning
=============