[pypy-svn] r48989 - pypy/extradoc/sprintinfo/gothenburg-2007

hpk at codespeak.net hpk at codespeak.net
Fri Nov 23 16:55:28 CET 2007


Author: hpk
Date: Fri Nov 23 16:55:27 2007
New Revision: 48989

Added:
   pypy/extradoc/sprintinfo/gothenburg-2007/qa-notes.txt
Log:
outcome of cfbolz, sameuele, holger discussion


Added: pypy/extradoc/sprintinfo/gothenburg-2007/qa-notes.txt
==============================================================================
--- (empty file)
+++ pypy/extradoc/sprintinfo/gothenburg-2007/qa-notes.txt	Fri Nov 23 16:55:27 2007
@@ -0,0 +1,60 @@
+discussion notes about QA issues (cf, pedronis, hpk) 
+
+stability & testing 
+
+status: 
+
+- automated nightly test runs of pypy tests on 32bit linux machine
+  (wyvern)   
+
+- automated nightly builds on tuatara (PowerPC OSX) for builds 
+  and benchmarks 
+
+- nightly run of cpython regression tests on top of several pypy-c's 
+  (running on samuele's linux Desktop machine) 
+
+- maciej (XXX) runs nightly tests of pypy-c, py.test -A on a private
+  machine
+
+
+missing: 
+
+- automated windows tests 
+  - a dedicated remotely accessible windows machine 
+    (cfbolz investigates at HHU) 
+  - setting up nightly runs 
+
+- aggregation of information from all these automated runs
+  goal: present summary of all results from automated runs at one place 
+
+
+releases 
+
+goal: 
+    - what does "making a release" mean?
+ 
+    - in addition to tests, run pypy with some real applications
+    - have pervasive testing (see above) on demand  (and not only
+      nightly) and on branches 
+
+    - write small-to-medium automatically tested example applications
+      for the special features of PyPy (thunk, taint, stackless, greenlets, tp, 
+      sandboxing?, ropes)
+
+    - how to publish new features/enhancements/cool stuff? 
+      - through Blog Posts
+      - maybe dist which snapshots a usable state of that feature 
+
+documentation 
+- goal: try to sort out current pypy/doc mess and bring it to more
+  maintainable state 
+
+- write "books" with many subsections about topics, e.g. 
+  "The complete guide to the Python Standard Interpreter" 
+  "Building and Programming with RPython" 
+  "Architecture and Implementation" 
+
+  in any case, the idea is to keep the number of such "books" around 3, 
+  first think about sections, then migrate existing docs to it 
+
+



More information about the Pypy-commit mailing list