Hey, I was serious when I said I would improve on benchmarks info! Anyone want to help in creating that benchmark description list? Just reply to this mail so that everyone can "review" what the benchmarks do.
2010/12/4 Maciej Fijalkowski <[email protected]>: > On Sat, Dec 4, 2010 at 1:05 PM, Laura Creighton <[email protected]> wrote: >> re: keeping the 'why we are slower/what we could do to fix it' info up >> to date -- one possibility is to make a 'why we were/what we are for >> release 1.4.' Then every time you make a major release, you update >> those fields as needed. And if major changes happen between 'what >> was in the last major release' vs 'what's on trunk now' you can even >> make a note of it -- 'fixed in rev whatever it was, when we merged in >> whoever it was' brank, see blog post over here'. And if you forget, >> well, you will catch it when the next major release comes out. >> >> Just an idea. >> >> Laura >> > > I think the general idea "we know what's wrong" vs "we have no clue" > is good. However, I would like to maybe decide what we do with tons of > docs that we already have first :) > _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
