Hi pypy-dev, 

it makes sense to discuss a few issuses regarding future 
development work (apart from the very nice and successful 
translation meeting we had last week).  I suggest to meet 

    Thursday, 2nd June, 3pm (CEST == GMT+1) 

on #pypy at irc.freenode.net.  Here are suggested topics: 

- sprint announcement/themes: 

  although times and city are fixed already, the actual sprint
  topics for the post-europython sprint from 1st July - 7th
  July in Goetheborg (Sweden) are not yet decided and
  announced.  However, almost all active developers will come and
  it's already safe to reserve the time and book your flights 
  if you want to attend a newcomer-friendly sprint! 
    
- release planning: there is the idea to do a PyPy-0.6.2 
  around EuroPython or even as the finishing event of the 
  public EuroPython sprint.  Goals for this possible release 
  need some discussion, though.  Here is a suggestion: 

    - move our lib-python base to 2.4.1 

    - make documentation  more complete (e.g. interpreter/ 
      docs are still missing) 

    - integrate parser module (possibly making it RPython
      conformant) 

    (- maybe offer a small tool to translate small 
      RPython programs)

- giving the translation efforts a stable base: 

  One problem with ongoing development of PyPy is that
  the translation process is still somewhat fragile with
  respect to type inference (annotation) on our source tree.  
  Therefore, it would be good if translation could for some time 
  rely on a non-changing PyPy base.  One simple idea 
  is to fork off translation work in a branch, although
  i'd like to avoid that if possible.  For starters, 
  documentation changes in the branch would not be 
  immediately seen on the website. Any other _simple_ ideas? 
  
- Advancing Issue Tracking: 

  we probably want to decide how we proceed with issue tracking
  and especially classifications of issues.  There is the
  simple idea of assigning an 'easy', 'medium' and 'hard'
  value to each issue to make it easier for newcomers and for
  ourselves. 

  Moreover, if we go for a 0.6.2 release i think we should
  redesign the tracker schema to use 'release' instead of 
  'milestone'. 

- news/infos: 

  there are news regarding a guy who is likely to enter 
  the EU/PyPy project and who comes from the Squeak (Smalltalk
  mostly implemented in Smalltalk) world. Just so you know. 

- anything else i forgot (please post before instead of 
  suggesting it at the meeting -> better planning)

cheers & see you, 

    holger
_______________________________________________
[email protected]
http://codespeak.net/mailman/listinfo/pypy-dev

Reply via email to