On Thu, Sep 4, 2008 at 9:52 AM, Bill Janssen <[EMAIL PROTECTED]> wrote:
>> but before deciding
>> to fix a bug, please consult at least one other committer, and when it
>> doubt, mail the list.
>
> Is there a handy list of committers available?
>
As always, the python-dev FAQ has an answer:
http:/
> but before deciding
> to fix a bug, please consult at least one other committer, and when it
> doubt, mail the list.
Is there a handy list of committers available?
Bill
___
python-committers mailing list
[email protected]
http://mail.python
On Thu, Aug 21, 2008 at 9:29 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> [Brett]
>>> Since the next step is release candidates, I have two questions:
>>>
>>> 1. Do commits now require a code review?
>
> [Barry]
>> Ideally, all comments are reviewed , but I think the current
>> arrangement wil
[Brett]
>> Since the next step is release candidates, I have two questions:
>>
>> 1. Do commits now require a code review?
[Barry]
> Ideally, all comments are reviewed , but I think the current
> arrangement will have to work for the rc's. I'd say be even more careful
> about the changes you intr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 20, 2008, at 11:24 PM, Brett Cannon wrote:
On Wed, Aug 20, 2008 at 8:10 PM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The releases are done. Thanks, both the 3.0 branch and the trunk
are now o
On Wed, Aug 20, 2008 at 8:10 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The releases are done. Thanks, both the 3.0 branch and the trunk are now open
> for commits.
>
Since the next step is release candidates, I have two questions:
1. Do com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The releases are done. Thanks, both the 3.0 branch and the trunk are now open
for commits.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIrNyb2YZpQepbvXERAq/WAJwMG1nc/7K3D+fgXFOnoYbJ2bmJoQCeNa3Z
ssE/3G13S9YLkXUHt3iv
