Does anyone have an issue with me requesting commit privs for Ask Solem to help me with the multiprocessing module? He's the author of the celery package (http://celeryproject.org/) and one of the biggest multiprocessing users I know of. He's also submitted several patches, and I consult with him on bigger changes.
As it stands, I've not had the time I need or want to dedicate to focusing on fixes, therefore I feel it would be beneficial to pull in a second person to help distribute the load. I would of course mentor him, and coordinate with him for the foreseeable future.
jesse
Am 16.08.2010 19:22, schrieb Jesse Noller:
Does anyone have an issue with me requesting commit privs for Ask Solem to help me with the multiprocessing module? He's the author of the celery package (http://celeryproject.org/) and one of the biggest multiprocessing users I know of. He's also submitted several patches, and I consult with him on bigger changes.
I've never heard of him before, so I'd be skeptical giving him blanket write privileges.
However, if he restricts himself to multiprocessing, I have no concerns. Just make sure he understands what commit policies we have on what branches (dead: <=2.4, 3.0, security-only: 2.5, 2.6, bug fixes only: 2.7, 3.1, new features: 3k)
Unless somebody disagrees, please have him sent me his SSH key, and apply for python-committers.
Regards, Martin
On Mon, Aug 16, 2010 at 4:44 PM, "Martin v. Löwis" <martin@v.loewis.de> wrote:
Am 16.08.2010 19:22, schrieb Jesse Noller:
Does anyone have an issue with me requesting commit privs for Ask Solem to help me with the multiprocessing module? He's the author of the celery package (http://celeryproject.org/) and one of the biggest multiprocessing users I know of. He's also submitted several patches, and I consult with him on bigger changes.
I've never heard of him before, so I'd be skeptical giving him blanket write privileges.
However, if he restricts himself to multiprocessing, I have no concerns. Just make sure he understands what commit policies we have on what branches (dead: <=2.4, 3.0, security-only: 2.5, 2.6, bug fixes only: 2.7, 3.1, new features: 3k)
I completely agree, and that was my plan!
Unless somebody disagrees, please have him sent me his SSH key, and apply for python-committers.
No one has spoken up yet; I will having him ping you if no one has spoken out within 24 hours.
jesse
Just make sure he understands what commit policies we have on what branches (dead: <=2.4, 3.0, security-only: 2.5, 2.6, bug fixes only: 2.7, 3.1, new features: 3k)
I thought 2.5 was dead and 2.6 only got security fixes (and doc changes), now that 2.7 is stable. Am I actually mistaken?
Regards
Just make sure he understands what commit policies we have on what branches (dead: <=2.4, 3.0, security-only: 2.5, 2.6, bug fixes only: 2.7, 3.1, new features: 3k)
Barry confirmed on IRC with this clarification (thanks):
a stable version does not go into security mode as soon as the new stable is out, only some time after, when the last bugfix (i.e. micro) release is made;
an old stable version gets security fixes for five years, even if there is another old stable version before this term.
Regards
participants (3)
-
"Martin v. Löwis" -
Jesse Noller -
Éric Araujo