Here at BeOpen we're scrambling to get the release schedule for the rest of Python 1.6 planned. We're now looking at releasing Python 1.6b1 (or maybe it's going to be called 1.6a3 after all) on June 30! This means that if SRE isn't ready, we'll go with an incomplete SRE. Still better than no SRE! Please, PLEASE, if you have pending patches that you think should go into 1.6b1, submit them to SourceForge. We'll do our best to have a look at every patch submitted; but don't wait until the last moment. (Trent Mick, it would be helpful if you assigned each of your patches a potential reviewer from the list of existing developers -- that way we can split up the review load.) --Guido van Rossum (home page: http://www.python.org/~guido/)
guido wrote:
Here at BeOpen we're scrambling to get the release schedule for the rest of Python 1.6 planned. We're now looking at releasing Python 1.6b1 (or maybe it's going to be called 1.6a3 after all) on June 30! This means that if SRE isn't ready, we'll go with an incomplete SRE. Still better than no SRE!
a major SRE patch is coming up later today. btw, what would it take for me to check it in myself (assuming someone will give me commit privs, of course)? can I apply patches via sourceforge's web interface, or do I have to figure out how to run cvs over ssh etc etc (tim? where's the second installment of your sourceforge vs. windows series?) </F>
[effbot]
a major SRE patch is coming up later today.
Great!
btw, what would it take for me to check it in myself (assuming someone will give me commit privs, of course)? can I apply patches via sourceforge's web interface, or do I have to figure out how to run cvs over ssh etc etc
Erm, the latter. From a Unix system it's a breeze. From Windows, it's a relative breeze to do an *anonymous* checkout (no SSH required), but getting commit permission is a pain -- Tim will research this. (Do you have access to any Unix or Linux system at all?) I'll make you a developer anyway.
(tim? where's the second installment of your sourceforge vs. windows series?)
I'm waiting too! --Guido van Rossum (home page: http://www.python.org/~guido/)
[Fredrik Lundh]
(tim? where's the second installment of your sourceforge vs. windows series?)
Waiting for you to finish SRE <wink>. Seriously, I don't *need* to get Windows checkin access for the imminent release, so I moved this down my priority list. I needed to move *something* down because finding a place to live around here is both urgent & consuming much more time than I had planned on (vacancy rate: 0%). Windows vs SourceForge is still on my plate, and I'm not giving up on it, just slipping it. just-carrying-my-plans-between-the-bathroom-&-the-bed-is- invigorating-exercise-ly y'rs - tim
just-carrying-my-plans-between-the-bathroom-&-the-bed-is- invigorating-exercise-ly y'rs - tim
[Mark Hammond]
Your plans, or your pans?
I-knew-you-were-old-but-not-that-old-<wink>-ly,
My pans are in storage somewhere in Baltimore, so I can't report on their possible growth. Or is this an Australian thing <wink>? put-another-pan-on-the-barbie-mate?-ly y'rs - tim PS: My testicles *have* grown since I moved to VA! I'm wondering whether it's an early symptom of Lyme disease. They're still easy to carry from room to room, though, provided simply I'm careful not to trip over them.
Guido van Rossum wrote:
Here at BeOpen we're scrambling to get the release schedule for the rest of Python 1.6 planned. We're now looking at releasing Python 1.6b1 (or maybe it's going to be called 1.6a3 after all) on June 30! This means that if SRE isn't ready, we'll go with an incomplete SRE. Still better than no SRE!
Please, PLEASE, if you have pending patches that you think should go into 1.6b1, submit them to SourceForge. We'll do our best to have a look at every patch submitted; but don't wait until the last moment.
So, to sum up (because I'm a bit lost after all this patch-related messages), what should I do to avoid at best adding to the collective burden : 1. Should I send patches to SF and be quiet until June 30 ? 2. Should I apply for privileges and spend <big time> installing an SSH client on my box (illegal in France ;), then make my Python way into the SF galaxy ? 3. If I volunteer for help with the patches backlog, what do I do ? 4. Other options presented to me ? Context : I (will) have some patches lying around, there are some patches of mine on the pile sent to patches@python.org that I'm confident about, I have read the FAQ at SF which gave me 0 clues on how things are being set up there (only general info about who why and what for + terms of service), and I managed to create an account with a personal page containing two bookmarks in it (after being distracted with personal and project ratings + gobs of links to gobs of stuff). -- Vladimir MARANGOZOV | Vladimir.Marangozov@inrialpes.fr http://sirac.inrialpes.fr/~marangoz | tel:(+33-4)76615277 fax:76615252
1. Should I send patches to SF and be quiet until June 30 ?
Yes. Not too quiet -- helping selecting which old patches are good would help. Also downloading patches from SF and commenting on them (+1/-1) in the patches list would help.
2. Should I apply for privileges and spend <big time> installing an SSH client on my box (illegal in France ;), then make my Python way into the SF galaxy ?
Probably no.
3. If I volunteer for help with the patches backlog, what do I do ?
Go through the patches archives and review patches. If you find one for which you would vote +1 and which you think I might like, submit it to SF.
4. Other options presented to me ?
Context : I (will) have some patches lying around, there are some patches of mine on the pile sent to patches@python.org that I'm confident about, I have read the FAQ at SF which gave me 0 clues on how things are being set up there (only general info about who why and what for + terms of service), and I managed to create an account with a personal page containing two bookmarks in it (after being distracted with personal and project ratings + gobs of links to gobs of stuff).
Go to the Python Project Summary, then to the Patch Manager. At the top, click on Submit Patch. --Guido van Rossum (home page: http://www.python.org/~guido/)
On Mon, Jun 26, 2000 at 09:35:52PM -0500, Guido van Rossum wrote:
(Trent Mick, it would be helpful if you assigned each of your patches a potential reviewer from the list of existing developers -- that way we can split up the review load.)
Do you mean I should reassigned patch-reviewing over and above the assignments that you have done recently? I was just going to put up twenty more patches and assign them all to Tim as well. :) Kidding. If, "yes", then I will make a go at that today. BTW I have answered a couple a questions on my patches. Does the person to whom the patch is assigned get an update notification? Trent -- Trent Mick trentm@activestate.com
participants (6)
-
Fredrik Lundh -
Guido van Rossum -
Mark Hammond -
Tim Peters -
Trent Mick -
Vladimir.Marangozov＠inrialpes.fr