[pypy-dev] Idea for speed.pypy.org

Maciej Fijalkowski fijall at gmail.com
Sat Dec 4 13:35:18 CET 2010


On Sat, Dec 4, 2010 at 1:05 PM, Laura Creighton <lac at openend.se> 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 :)



More information about the Pypy-dev mailing list