Mailman 3 November 2005 - pypy-dev

pypy sync meeting on 3th November, 2005
by Carl Friedrich Bolz Nov. 3, 2005

Nov. 3, 2005

Hi PyPy-dev! yet another wonderful pypy-sync meeting is coming! Please be all there and send me a mail with your activity report if you cannot come. ========================================= pypy-sync developer meeting 3th November ========================================= Time & location: 1.00 - 1.30 pm (GMT+2) at #pypy-sync Regular Topics ==================== - activity reports (3 prepared lines of info, LAST/NEXT/BLOCKERS). - resolve conflicts/blockers Annotated Topics of the week ================================= gothenburg sprint top.ics -------------------------- (topic suggested by Bea, moved over from last week) We have a sprint planned at the beginning of December in Gothenburg. What should the topics of the sprint be? Will it be a more open sprint or more rather targeted at core developpers? finalizing the release -------------------------- The release seems to be progressing very well, there are some small final tasks to be distributed, like who sends out the announcement mails, etc. See you all tomorrow, Carl Friedrich

1 1

I have updated the LICENSE file for 0.8 and copyright holders list
by Samuele Pedroni Nov. 1, 2005

Nov. 1, 2005

http://codespeak.net/pipermail/pypy-svn/2005-November/009556.html this lists the copyright holders (we have a different list of contributor that contains all contributors, including people that just did small contributions or didn't want to be listed as copyright holders). The additions are mostly people that were at the Paris sprint and contributed there. If people don't want to be listed please tell us so, as people did in the past. regards, Samuele Pedroni.

1 0

rel 0.8 coord meeting, 2pm GMT+1 monday 31 Oct 2005 on #pypy
by Samuele Pedroni Nov. 1, 2005

Nov. 1, 2005

As already pointed out the scope of the 0.8 release is mainly: - Ship our integrated and now translated AST compiler - Ship the speed improvements we had since 0.7, which mainly means updating the documentation that discuss current speed - Ship a release in which the thunk space can also be translated The meeting is for people who think can spend some time helping with the release during the week. Agenda for the meeting (max ~1h): Status of the branch and regressions (max 15-20min) ------------------------------------------------- I have run tests and compliancy tests on the branch made on Friday: see issue 147 and http://www.strakt.com/~pedronis/testresult-pre0.8/ We have basically two regressions: - we have a failure in test_sort, because switching to using rpython lists directly has broken detecting changes during list sort in some situations. - translation with threads doesn't work at least because stack_too_big is not thread-safe, there may be other issues. Making stack_too_big thread-safe is not trivial x-platform wise. Discuss whether there are low-risk solutions that can be implemented in 1/2 days, otherwise I think the regressions are not show stoppers. Release tasks, mostly documentation updates (20-25min) ------------------------------------------------------ I have started adding issues to the tracker, under release 0.8, for updates/writing required for the release: - go through the list, see if something is amiss, possibly assign people to tasks and reviewing texts Packaging, uploading (15-20min) ---------------------------------- When and how to proceed making the candidate tarballs, uploading them and cutting the release. This is something so far Holger took care of, can this be delegated (or not for this release), how do we want to proceed? Thanks, Samuele.

2 1

Re: [pypy-svn] r19249 - pypy/release/0.8.x/pypy/doc
by holger krekel Nov. 1, 2005

Nov. 1, 2005

On Mon, Oct 31, 2005 at 16:45 +0100, ale(a)codespeak.net wrote: > Author: ale > Date: Mon Oct 31 16:45:24 2005 > New Revision: 19249 > > Modified: > pypy/release/0.8.x/pypy/doc/release-0.8.0.txt > Log: > First draft of release announcement. > > I have trunkated the contributor list to the 6 most active developer and point to contributor.html for the rest. > > Please comment I think at least 8 or 10 people should be listed. Btw, I once had a different (half-manual) process of determining contributions by using "svn blame" and counting the lines. One has to be careful, though, because we have some large files (like the unicode-database) which are not really programmed code and distort the statistics. cheers, holger

1 0