From larry at hastings.org  Fri Jun  1 23:23:18 2012
From: larry at hastings.org (Larry Hastings)
Date: Fri, 01 Jun 2012 14:23:18 -0700
Subject: [python-committers] Python Language Summit, Florence, July 2012
In-Reply-To: <4FC60D44.7050602@hastings.org>
References: <4FC60D44.7050602@hastings.org>
Message-ID: <4FC932C6.6030101@hastings.org>


On 05/30/2012 05:06 AM, Larry Hastings wrote:
> Like Python?  Like Italy?  Like meetings?  Then I've got a treat for you!
>
> I'll be chairing a Python Language Summit this July in historic 
> Florence, Italy.  It'll be on July 1st (the day before EuroPython 
> starts) at the Grand Hotel Mediterraneo conference center.

I have an update and a clarification.

First, the clarification: the Language Summit is really intended for 
core developers.  If you're not a core developer, then the meeting isn't 
for you.  (Don't worry, you're not missing anything.  It's about as 
interesting as doing your taxes.)

Second, an update: enough people said it was too early for them to 
attend that we've rescheduled.  It's now Saturday July 7th, the first 
day of the sprints.

As before, please email me if you can attend (and you're a core 
developer!) so I can get a rough headcount.

Ciao,


//arry/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120601/7a98d458/attachment.html>

From patcam at python.org  Mon Jun  4 17:30:13 2012
From: patcam at python.org (Pat Campbell)
Date: Mon, 4 Jun 2012 11:30:13 -0400
Subject: [python-committers] Contributor agreement
In-Reply-To: <4FCB7062.6010806@gmail.com>
References: <4FCB7062.6010806@gmail.com>
Message-ID: <CAFy_4dLz14xN=WXEgNUkYSqupWXJKZzMb2hF=_KZ31CFcqCnOg@mail.gmail.com>

Hi Ronan:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to the online bug tracker.


On Sun, Jun 3, 2012 at 10:10 AM, Ronan Lamy <ronan.lamy at gmail.com> wrote:

> Hello,
>
> Please find herein my contributor agreement, as asked by Brett Cannon (
> http://bugs.python.org/**issue14938 <http://bugs.python.org/issue14938>).
>
> Best regards,
> Ronan Lamy
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120604/0a3969f1/attachment.html>

From patcam at python.org  Mon Jun  4 19:02:53 2012
From: patcam at python.org (Pat Campbell)
Date: Mon, 4 Jun 2012 13:02:53 -0400
Subject: [python-committers] contrib form for Alon Horev
In-Reply-To: <CAKZkVDu80jjQ6aEMrrZzs8A-OfN-APKxOgr2y8whGtOu6tz6rQ@mail.gmail.com>
References: <CAKZkVDu80jjQ6aEMrrZzs8A-OfN-APKxOgr2y8whGtOu6tz6rQ@mail.gmail.com>
Message-ID: <CAFy_4dK-eyRNEtbo4vkxkcq9xWmQ+XtPj=bDvuzLzCoPU=3Apg@mail.gmail.com>

Hi Alon:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to the online bug tracker.

Pat

On Sun, Jun 3, 2012 at 9:58 AM, Alon Horev <alonho at gmail.com> wrote:

>
>


-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120604/2d3c2a5f/attachment.html>

From patcam at python.org  Mon Jun  4 20:13:07 2012
From: patcam at python.org (Pat Campbell)
Date: Mon, 4 Jun 2012 14:13:07 -0400
Subject: [python-committers] Dan Boswell Contributor Agreement
In-Reply-To: <20120604174212.DB40F25009E@webabinitio.net>
References: <1338326851.13566.140661082334141.63EC9843@webmail.messagingengine.com>
	<20120530161446.258F725003F@webabinitio.net>
	<1338402516.9571.140661082837237.323788A7@webmail.messagingengine.com>
	<CAFy_4d+fP6h6VLvEOydmpsRa8Zgaj0BDW6okMeoAkC=VcXSJ0g@mail.gmail.com>
	<20120604174212.DB40F25009E@webabinitio.net>
Message-ID: <CAFy_4dLK-gjK1gK12pLxwZSNEv68xomNLM0xf+YTTB3gd=fEbA@mail.gmail.com>

Hi David:

If you or Dan want to send it directly to me.
Please find a contributor agreement form here:

http://www.python.org/psf/contrib/

and send it to me from this email address:

contributors at python.org

and then, I will process the form and add it to
the online bug tracker once there has been a tracker
profile completed by Dan Boswell.

If you have any questions, please let me know.

Thanks,
Pat


On Mon, Jun 4, 2012 at 1:42 PM, R. David Murray <rdmurray at bitdance.com>wrote:

> On Mon, 04 Jun 2012 13:27:48 -0400, Pat Campbell <patcam at python.org>
> wrote:
> > The group/batch of forms you mailed out to me did not include
> > a contributor agreement form for Dan.
>
> Yeah, that was Kurt's report, too.  I figure I must have mixed Dan up
> with someone else and did not in fact have a form for him.
>
> Thanks for checking.
>
> --David
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120604/cc0f78c4/attachment.html>

From patcam at python.org  Tue Jun  5 22:31:41 2012
From: patcam at python.org (Pat Campbell)
Date: Tue, 5 Jun 2012 16:31:41 -0400
Subject: [python-committers] contributor agreement
In-Reply-To: <41FE8500-4029-493B-AF86-007983DD4B3D@sprymix.com>
References: <41FE8500-4029-493B-AF86-007983DD4B3D@sprymix.com>
Message-ID: <CAFy_4dJVfVDOBcu1FU5RB9+Q8sdkwgNeRbQpX73D1_qNbe37EA@mail.gmail.com>

Hi Yury:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to our online bug tracker.

Pat

On Tue, Jun 5, 2012 at 1:14 PM, Yury Selivanov <yselivanov at sprymix.com>wrote:

> Hello,
>
> As part of working on PEP 362 implementation, I'm submitting you the
> signed Contributor Agreement form.
>
> Please find it attached.
>
> Thank you,
>
>
> -
> Yury Selivanov
> +1.416.509.2807
>
>
>


-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120605/e1bb6e43/attachment.html>

From patcam at python.org  Wed Jun  6 17:50:17 2012
From: patcam at python.org (Pat Campbell)
Date: Wed, 6 Jun 2012 11:50:17 -0400
Subject: [python-committers] My contributor agreement
In-Reply-To: <CAKimPHU-GBSU6drQMD0K99K2W8_MTbb-8pRqDWq8BLVpONWxEQ@mail.gmail.com>
References: <CAKimPHU-GBSU6drQMD0K99K2W8_MTbb-8pRqDWq8BLVpONWxEQ@mail.gmail.com>
Message-ID: <CAFy_4dKNvOTaxkNsBfe47durydxDOSbs30p2+tEF_MBR2vMJMw@mail.gmail.com>

Hi Dmitry:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to our online bug tracker.

Pat

On Wed, Jun 6, 2012 at 9:28 AM, Dmitry Shachnev <mitya57 at gmail.com> wrote:

> Name: Dmitry Shachnev
> bugs.python.org username: mitya57
>
> Scan of my agreement attached.
>
> --
> Dmitry Shachnev
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120606/2f2268c4/attachment.html>

From patcam at python.org  Fri Jun  8 18:56:21 2012
From: patcam at python.org (Pat Campbell)
Date: Fri, 8 Jun 2012 12:56:21 -0400
Subject: [python-committers] Contributor agreement for jcbollinger
In-Reply-To: <8F77913624F7524AACD2A92EAF3BFA544EB98204AB@11.stjude.org>
References: <8F77913624F7524AACD2A92EAF3BFA544EB98204AB@11.stjude.org>
Message-ID: <CAFy_4dKGhRYPEijXh34FRmYYjsYM6HG0BxKY+qQ7nms-7QNjFQ@mail.gmail.com>

Hi John:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to our online bug tracker.

Pat

On Wed, Jun 6, 2012 at 4:43 PM, Bollinger, John C <John.Bollinger at stjude.org
> wrote:

>  Dear Python Software Foundation,****
>
> ** **
>
> I attach a ZIP file containing a scanned image of my contributor
> agreement.  Though I am communicating via my work e-mail, the agreement is
> for contributions I may make as an individual, not a representative of my
> employer.  Please let me know whether it is satisfactory.****
>
> ** **
>
> Thanks,****
>
> ** **
>
> John Bollinger****
>
> --****
>
> John C. Bollinger****
>
> John.Bollinger at StJude.org****
>
> Thinman42 at yahoo.com****
>
> ** **
>
> ** **
>
> ** **
>
> -- ****
>
> John C. Bollinger, Ph.D.****
>
> Computing and X-Ray Scientist****
>
> Department of Structural Biology****
>
> St. Jude Children's Research Hospital****
>
> John.Bollinger at StJude.org****
>
> (901) 595-3166 [office]****
>
> www.stjude.org****
>
> ** **
>
> ** **
>
> ------------------------------
> Email Disclaimer: www.stjude.org/emaildisclaimer
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120608/510cf27d/attachment.html>

From patcam at python.org  Thu Jun 14 14:54:46 2012
From: patcam at python.org (Pat Campbell)
Date: Thu, 14 Jun 2012 08:54:46 -0400
Subject: [python-committers] PSF contributor agreement
In-Reply-To: <CAHg_5gpL81_FQ34U8xvy--O-fXCSSEgwgH4asgxTXA7Jxn4vug@mail.gmail.com>
References: <CAHg_5gpL81_FQ34U8xvy--O-fXCSSEgwgH4asgxTXA7Jxn4vug@mail.gmail.com>
Message-ID: <CAFy_4dKbuR2agJykwQ-kfnSoWkUkzJM-Ne4b8_cE53guepAK1A@mail.gmail.com>

Hi Catalin:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to our online bug tracker.

Pat

On Wed, Jun 13, 2012 at 2:53 AM, Catalin Iacob <iacobcatalin at gmail.com>wrote:

> Dear PSF member,
>
> Please find attached my contributor agreement.
>
> Regards,
> Catalin Iacob
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120614/6a3068e2/attachment.html>

From patcam at python.org  Thu Jun 14 17:11:45 2012
From: patcam at python.org (Pat Campbell)
Date: Thu, 14 Jun 2012 11:11:45 -0400
Subject: [python-committers] Contributor Agreement form for Mike Driscoll
Message-ID: <CAFy_4dKbFd4qXR-xYyAk3KGjXfqbkoMDNx1f6vV1_5L+fdDPXg@mail.gmail.com>

Hi Michael:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to our online bug tracker.

Pat

-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120614/ff5ab48c/attachment.html>

From patcam at python.org  Mon Jun 18 22:14:36 2012
From: patcam at python.org (Pat Campbell)
Date: Mon, 18 Jun 2012 16:14:36 -0400
Subject: [python-committers] Contributor Agreement Form
In-Reply-To: <CABVpgLX-iPdLep0j=2HH3ipa9PvuvDLteF_cu=gaFwoi02fOBQ@mail.gmail.com>
References: <CABVpgLX-iPdLep0j=2HH3ipa9PvuvDLteF_cu=gaFwoi02fOBQ@mail.gmail.com>
Message-ID: <CAFy_4dL3Tb0cXjK2M0-v7fQXJZQD1ZPnWJ+4acQe-dfH3=Ai_A@mail.gmail.com>

Hi Jez:

Thank-you for submitting your contributor agreement form. I would like to
add your
form to the PSF online bug tracker.

In order for me to add your contributor agreement form to your profile (on
the online bug
tracker) I will need to access your user number webpage or please provide
the link to your

"user# editing" webpage in order for me to mark (Yes) to receiving your
contributor
agreement form.

Or, you could provide me with your "user name, user number, & real name
(the way it

appears on the online bug tracker "login" webpage, since I was not able to
access the

webpage based on the information provided on the form. The login webpage is
"case

sensitive", therefore, the data used to access a webpage on this site must
be exact.

Thanking you in advance,
Pat


On Sun, Jun 17, 2012 at 11:26 PM, Jez <jezreel at gmail.com> wrote:

> Hi,
>
> My contributor agreement form is attached. I don't have a scanner handy,
> so this was taken with a phone camera -- I hope the quality's not too bad.
>
> Regards,
> Jez
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120618/1bbe2825/attachment.html>

From fwierzbicki at gmail.com  Mon Jun 18 22:17:17 2012
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Mon, 18 Jun 2012 13:17:17 -0700
Subject: [python-committers] Contributor Agreement Form
In-Reply-To: <CAFy_4dL3Tb0cXjK2M0-v7fQXJZQD1ZPnWJ+4acQe-dfH3=Ai_A@mail.gmail.com>
References: <CABVpgLX-iPdLep0j=2HH3ipa9PvuvDLteF_cu=gaFwoi02fOBQ@mail.gmail.com>
	<CAFy_4dL3Tb0cXjK2M0-v7fQXJZQD1ZPnWJ+4acQe-dfH3=Ai_A@mail.gmail.com>
Message-ID: <CADrh4z+UK2XPqsSy0jxM_Hs00Yqm+T03xCWF=g=mDak=k3nEkA@mail.gmail.com>

On Mon, Jun 18, 2012 at 1:14 PM, Pat Campbell <patcam at python.org> wrote:
> Hi Jez:
>
> Thank-you for submitting your contributor agreement form. I would like to
> add your
> form to the PSF online bug tracker.
>
> In order for me to add your contributor agreement form to your profile (on
> the online bug
> tracker) I will need to access your user number webpage or please provide
> the link to your
BTW Jez, you'll need to provide an id for the tracker at
bugs.python.org, not bugs.jython.org.

-Frank

From patcam at python.org  Tue Jun 19 17:39:00 2012
From: patcam at python.org (Pat Campbell)
Date: Tue, 19 Jun 2012 11:39:00 -0400
Subject: [python-committers] Contributor Agreement Form
In-Reply-To: <CABVpgLVzDVpqoysymWngrx56qyA58=y7iaD0=+7Mpj7vSuZHOA@mail.gmail.com>
References: <CABVpgLX-iPdLep0j=2HH3ipa9PvuvDLteF_cu=gaFwoi02fOBQ@mail.gmail.com>
	<CAFy_4dL3Tb0cXjK2M0-v7fQXJZQD1ZPnWJ+4acQe-dfH3=Ai_A@mail.gmail.com>
	<CABVpgLVzDVpqoysymWngrx56qyA58=y7iaD0=+7Mpj7vSuZHOA@mail.gmail.com>
Message-ID: <CAFy_4dJQnP1=JEZSg9ideipNGTrnt=Cy00UiA7v4H5dCmLthww@mail.gmail.com>

Hi Jez:

Thank-you for submitting your contributor agreement form to the PSF. It
has been added to our online bug tracker.

Pat


On Mon, Jun 18, 2012 at 5:35 PM, Jez <jezreel at gmail.com> wrote:

> Hi Pat,
>
> http://bugs.python.org/user16166 is my user profile page. I only had a
> Jython bug tracker account when I submitted the request, sorry for the
> confusion caused :)
>
> Regards,
> Jez
>
>
> On Mon, Jun 18, 2012 at 1:14 PM, Pat Campbell <patcam at python.org> wrote:
>
>> Hi Jez:
>>
>> Thank-you for submitting your contributor agreement form. I would like to
>> add your
>> form to the PSF online bug tracker.
>>
>> In order for me to add your contributor agreement form to your profile
>> (on the online bug
>> tracker) I will need to access your user number webpage or please provide
>> the link to your
>>
>> "user# editing" webpage in order for me to mark (Yes) to receiving your
>> contributor
>> agreement form.
>>
>> Or, you could provide me with your "user name, user number, & real name
>> (the way it
>>
>> appears on the online bug tracker "login" webpage, since I was not able
>> to access the
>>
>> webpage based on the information provided on the form. The login webpage
>> is "case
>>
>> sensitive", therefore, the data used to access a webpage on this site
>> must be exact.
>>
>> Thanking you in advance,
>> Pat
>>
>>
>> On Sun, Jun 17, 2012 at 11:26 PM, Jez <jezreel at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> My contributor agreement form is attached. I don't have a scanner handy,
>>> so this was taken with a phone camera -- I hope the quality's not too bad.
>>>
>>> Regards,
>>> Jez
>>>
>>
>>
>>
>> --
>> Pat Campbell
>> PSF Administrator/Secretary
>> patcam at python.org
>>
>
>


-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120619/a78b1830/attachment.html>

From patcam at python.org  Tue Jun 26 19:56:20 2012
From: patcam at python.org (Pat Campbell)
Date: Tue, 26 Jun 2012 13:56:20 -0400
Subject: [python-committers] Contributor agreement for GSoC2012
In-Reply-To: <4FE252AE.3030002@gmail.com>
References: <4FE252AE.3030002@gmail.com>
Message-ID: <CAFy_4dKORxLO5NbZWnNPaZEJxmwQqR7UGEnY8p8m-WN3w6Ecjg@mail.gmail.com>

Hi Stefan:

Thank-you for submitting your contributor agreement form. I would like to
add your
form to the PSF online bug tracker.

In order for me to add your contributor agreement form to your profile (on
the online bug
tracker) I will need to access your user number webpage or please provide
the link to your

"user# editing" webpage in order for me to mark (Yes) to receiving your
contributor
agreement form.

Or, you could provide me with your "user name, user number, & real name
(the way it appears

on the online bug tracker "login" webpage, since I was not able to access
the webpage based on

the information provided on the form. The login webpage is "case
sensitive", therefore, the data

used to access a webpage on this site must be exact.

Thanking you in advance,
Pat


On Wed, Jun 20, 2012 at 6:46 PM, M Stefan <mstefanro at gmail.com> wrote:

> Hello, I'm a student at Google Summer of Code 2012 working on improving
> the pickle serializer in Python.
>
> My mentor is Alexandre Vassalotti and most of the work I'm planning to do
> is
> explained in PEP 3154[1]. If interested, my progress can be tracked in the
> blog
> at [2] and bitbucket repo at [3].
>
> Attached is my PSF contributor agreement. I apologize for the delay.
>
> Yours,
>  Stefan Mihaila
>
> [1] http://www.python.org/dev/**peps/pep-3154/<http://www.python.org/dev/peps/pep-3154/>
> [2] http://pypickle4.wordpress.**com/ <http://pypickle4.wordpress.com/>
> [3] https://bitbucket.org/**mstefanro/pickle4/<https://bitbucket.org/mstefanro/pickle4/>
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120626/c026f72c/attachment.html>

From patcam at python.org  Tue Jun 26 20:09:59 2012
From: patcam at python.org (Pat Campbell)
Date: Tue, 26 Jun 2012 14:09:59 -0400
Subject: [python-committers] contributor agreement
In-Reply-To: <5EABA81A-BC25-4D7F-9AEE-252981944721@sprymix.com>
References: <41FE8500-4029-493B-AF86-007983DD4B3D@sprymix.com>
	<CAFy_4dJVfVDOBcu1FU5RB9+Q8sdkwgNeRbQpX73D1_qNbe37EA@mail.gmail.com>
	<5EABA81A-BC25-4D7F-9AEE-252981944721@sprymix.com>
Message-ID: <CAFy_4d+2Yx=KPx7GVcf__EYE42QcpFDg1jX3fR--iHLpVLf3FQ@mail.gmail.com>

Hi Yury:

I have reassigned your agreement to your new login name -- as requested.

Thanks,
Pat

On Mon, Jun 25, 2012 at 7:15 PM, Yury Selivanov <yselivanov at sprymix.com>wrote:

> On 2012-06-05, at 4:31 PM, Pat Campbell wrote:
>
> > Hi Yury:
> >
> > Thank-you for submitting your contributor agreement form to the PSF. It
> > has been added to our online bug tracker.
>
> Hello Pat,
>
> I've used to use my google-open-id login for bugs.python.org, and
> now I created a new proper account - 'yselivanov'.  Could you please
> reassign my agreement to the new login name?
>
> Thank you,
> -
> Yury
>



-- 
Pat Campbell
PSF Administrator/Secretary
patcam at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120626/3dd7a111/attachment.html>

From alexandre at peadrop.com  Wed Jun 27 22:22:24 2012
From: alexandre at peadrop.com (Alexandre Vassalotti)
Date: Wed, 27 Jun 2012 13:22:24 -0700
Subject: [python-committers] Contributor agreement for GSoC2012
In-Reply-To: <CAFy_4dKORxLO5NbZWnNPaZEJxmwQqR7UGEnY8p8m-WN3w6Ecjg@mail.gmail.com>
References: <4FE252AE.3030002@gmail.com>
	<CAFy_4dKORxLO5NbZWnNPaZEJxmwQqR7UGEnY8p8m-WN3w6Ecjg@mail.gmail.com>
Message-ID: <CANcUUecCZxxQrGMx3cMLi2MdDpco0tkDjk4_8zBBE+wuNSKbCQ@mail.gmail.com>

On Tue, Jun 26, 2012 at 10:56 AM, Pat Campbell <patcam at python.org> wrote:

> In order for me to add your contributor agreement form to your profile (on
> the online bug
> tracker) I will need to access your user number webpage or please provide
> the link to your
>
> "user# editing" webpage in order for me to mark (Yes) to receiving your
> contributor
> agreement form.
>


Hi Pat,

This is Stefan's user page: http://bugs.python.org/user16149
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120627/acc1e98e/attachment.html>

From jcea at jcea.es  Fri Jun 29 02:23:12 2012
From: jcea at jcea.es (Jesus Cea)
Date: Fri, 29 Jun 2012 02:23:12 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
Message-ID: <4FECF570.1070202@jcea.es>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Python 3.3 is currently in beta, so the rythm of new patches in
"default" will decrease and people with new features MUST wait until
3.3 is out. I think this is a waste of time. And even if people is
working with HG private clones, they can't test using the buildbots
neither mark a bug as fixed in the tracker.

If we create a new 3.3 branch *NOW* and add it to the buildbots,
people can keep working in "default" full speed (for 3.4), while 3.3
branch is getting ready for general release. We only need to remember
to appy the same rule current rule: any patch in branch "x" must be
"merged" into branch "x+1" too.

Has this step been considered?. I think it is a nice improvement that
HG enables and we are not using.

What do you think?.

PS: In the past some people said that this "feature freeze" forces
devs to concentrate in getting the release ready. This is a good
point, but it should be a social issue to solve, not a technical one.
I, for one, would personally invest more time in fixing upcoming 3.3
(soon to be released) than hacking future 3.4 (two years away!). No
need to "press me" with an ?obsolete? technical limitation.

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBT+z1cJlgi5GaxT1NAQLt0AP8DsFzMms7Z5JhomDZaTZkZB2X5Dh7SBkK
0XwM5oKASIa2k9OEX8CbKJI6u6dCUT3VGS3qbXNcv1baoK8ldykt2Ats9XHXL3gD
9ZX4Ofcm6Qw738s9OgvsQnDFYcx9FtB8wew5b6qnAsRtDWEo5iv88ZzZEtNMNbxW
Rcv9exP38JY=
=N8z9
-----END PGP SIGNATURE-----

From rdmurray at bitdance.com  Fri Jun 29 04:13:59 2012
From: rdmurray at bitdance.com (R. David Murray)
Date: Thu, 28 Jun 2012 22:13:59 -0400
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <4FECF570.1070202@jcea.es>
References: <4FECF570.1070202@jcea.es>
Message-ID: <20120629021400.1361E250840@webabinitio.net>

On Fri, 29 Jun 2012 02:23:12 +0200, Jesus Cea <jcea at jcea.es> wrote:
> Python 3.3 is currently in beta, so the rythm of new patches in
> "default" will decrease and people with new features MUST wait until
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG private clones, they can't test using the buildbots
> neither mark a bug as fixed in the tracker.
> 
> If we create a new 3.3 branch *NOW* and add it to the buildbots,
> people can keep working in "default" full speed (for 3.4), while 3.3
> branch is getting ready for general release. We only need to remember
> to appy the same rule current rule: any patch in branch "x" must be
> "merged" into branch "x+1" too.
> 
> Has this step been considered?. I think it is a nice improvement that
> HG enables and we are not using.

Yes, it has been considered.  It was rejected by the RM.

> What do you think?.
> 
> PS: In the past some people said that this "feature freeze" forces
> devs to concentrate in getting the release ready. This is a good
> point, but it should be a social issue to solve, not a technical one.
> I, for one, would personally invest more time in fixing upcoming 3.3
> (soon to be released) than hacking future 3.4 (two years away!). No
> need to "press me" with an ??obsolete? technical limitation.

For exactly this reason.  We want to focus on fixing bugs for 3.3.  Having
to commit to yet another branch at this time would be a distraction,
as would having to pay attention to feature patches going in to default.
If the active committers are working on bug fixes, then no features
would be getting committed anyway, and the extra merge would just be
pointlessly annoying.

Opinions on this can differ, of course.

There is still nothing stopping people from posting new features to
the tracker, so there is no reason that non-committer workflow needs
to change, they just may need to wait a bit longer for feedback...which
they'd have to do regardless of whether we branch now or not.

Georg has indicated he will branch 3.3 at rc1, which I personally
think is sensible.

--David

From benjamin at python.org  Fri Jun 29 04:41:37 2012
From: benjamin at python.org (Benjamin Peterson)
Date: Thu, 28 Jun 2012 19:41:37 -0700
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <4FECF570.1070202@jcea.es>
References: <4FECF570.1070202@jcea.es>
Message-ID: <CAPZV6o-p8ss+fAXZc0F2-QTqTOSDvqj3tXuEQ5yLGsfYPyBbEA@mail.gmail.com>

2012/6/28 Jesus Cea <jcea at jcea.es>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Python 3.3 is currently in beta, so the rythm of new patches in
> "default" will decrease and people with new features MUST wait until
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG private clones, they can't test using the buildbots
> neither mark a bug as fixed in the tracker.
>
> If we create a new 3.3 branch *NOW* and add it to the buildbots,
> people can keep working in "default" full speed (for 3.4), while 3.3
> branch is getting ready for general release. We only need to remember
> to appy the same rule current rule: any patch in branch "x" must be
> "merged" into branch "x+1" too.
>
> Has this step been considered?. I think it is a nice improvement that
> HG enables and we are not using.
>
> What do you think?.

I, for one, had my fill of maintaining 4 branches when we were doing
two versions of 2.x and two versions of 3.x.

People are free to put their features in their own private clones and
await 3.4 development beginning.


-- 
Regards,
Benjamin

From ncoghlan at gmail.com  Fri Jun 29 06:02:55 2012
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Fri, 29 Jun 2012 14:02:55 +1000
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <20120629021400.1361E250840@webabinitio.net>
References: <4FECF570.1070202@jcea.es>
	<20120629021400.1361E250840@webabinitio.net>
Message-ID: <CADiSq7cWG54rO=sOSyRr_STxgjN3q81SgGFmcMhRj2QCMTsD5Q@mail.gmail.com>

On Fri, Jun 29, 2012 at 12:13 PM, R. David Murray <rdmurray at bitdance.com> wrote:
> There is still nothing stopping people from posting new features to
> the tracker, so there is no reason that non-committer workflow needs
> to change, they just may need to wait a bit longer for feedback...which
> they'd have to do regardless of whether we branch now or not.

Also see my previous email regarding the early flagging of high
priority or release blocker issues for 3.4, or assigning items to
ourselves for later review - we have a triage tool to keep track of
changes before they hit the main repo, we may as well make use of it.

> Georg has indicated he will branch 3.3 at rc1, which I personally
> think is sensible.

As do I - it's a not-so-subtle hint as to what our priorities should
be between now and rc1 :)

Cheers,
Nick.

-- 
Nick Coghlan?? |?? ncoghlan at gmail.com?? |?? Brisbane, Australia

From rosslagerwall at gmail.com  Fri Jun 29 06:29:06 2012
From: rosslagerwall at gmail.com (Ross Lagerwall)
Date: Fri, 29 Jun 2012 06:29:06 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <4FECF570.1070202@jcea.es>
References: <4FECF570.1070202@jcea.es>
Message-ID: <4FED2F12.2030304@gmail.com>

On 06/29/2012 02:23 AM, Jesus Cea wrote:
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG private clones, they can't test using the buildbots
> neither mark a bug as fixed in the tracker.

This is also a nice improvement that Mercurial enables, you can commit
your code into a private or even public branch and just merge it into
default when both your code and default are ready for it.

Regards
-- 
Ross Lagerwall



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 294 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-committers/attachments/20120629/ecbf5f45/attachment.pgp>

From hs at ox.cx  Fri Jun 29 08:40:52 2012
From: hs at ox.cx (Hynek Schlawack)
Date: Fri, 29 Jun 2012 08:40:52 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <20120629021400.1361E250840@webabinitio.net>
References: <4FECF570.1070202@jcea.es>
	<20120629021400.1361E250840@webabinitio.net>
Message-ID: <4FED4DF4.8050202@ox.cx>

> For exactly this reason.  We want to focus on fixing bugs for 3.3.  Having
> to commit to yet another branch at this time would be a distraction,
> as would having to pay attention to feature patches going in to default.
> If the active committers are working on bug fixes, then no features
> would be getting committed anyway, and the extra merge would just be
> pointlessly annoying.

+1 on that one, I?m really glad the current polishing is more or less
frictionless. Merging across branches is especially annoying when the
commit rates are fairly high like now.

From g.brandl at gmx.net  Fri Jun 29 10:07:32 2012
From: g.brandl at gmx.net (Georg Brandl)
Date: Fri, 29 Jun 2012 10:07:32 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <4FECF570.1070202@jcea.es>
References: <4FECF570.1070202@jcea.es>
Message-ID: <jsjnms$o55$1@dough.gmane.org>

On 29.06.2012 02:23, Jesus Cea wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Python 3.3 is currently in beta, so the rythm of new patches in
> "default" will decrease and people with new features MUST wait until
> 3.3 is out. I think this is a waste of time. And even if people is
> working with HG private clones, they can't test using the buildbots
> neither mark a bug as fixed in the tracker.
>
> If we create a new 3.3 branch *NOW* and add it to the buildbots,
> people can keep working in "default" full speed (for 3.4), while 3.3
> branch is getting ready for general release. We only need to remember
> to appy the same rule current rule: any patch in branch "x" must be
> "merged" into branch "x+1" too.
>
> Has this step been considered?. I think it is a nice improvement that
> HG enables and we are not using.
>
> What do you think?.
>
> PS: In the past some people said that this "feature freeze" forces
> devs to concentrate in getting the release ready. This is a good
> point, but it should be a social issue to solve, not a technical one.
> I, for one, would personally invest more time in fixing upcoming 3.3
> (soon to be released) than hacking future 3.4 (two years away!). No
> need to "press me" with an ?obsolete? technical limitation.

Others have already explained my motive for keeping the "technical
limitation": it is really about workload for developers.

And as Ross says: you *can* use the buildbots for personal branches.
And if you put the right "Closes #12345" in your commit messages
you don't even have to care to remember to close issues after they
are merged into mainline.

Georg


From jcea at jcea.es  Fri Jun 29 14:20:43 2012
From: jcea at jcea.es (Jesus Cea)
Date: Fri, 29 Jun 2012 14:20:43 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <jsjnms$o55$1@dough.gmane.org>
References: <4FECF570.1070202@jcea.es> <jsjnms$o55$1@dough.gmane.org>
Message-ID: <4FED9D9B.9030609@jcea.es>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29/06/12 10:07, Georg Brandl wrote:
> And as Ross says: you *can* use the buildbots for personal
> branches.

I missed that. How is it done?.

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBT+2dm5lgi5GaxT1NAQIweAP/fm3lUsr/3T2or6+7mHpzAR5P5+6nGd3g
UO2dZWTYjT4FxqMRiZotuO0RgQ6KKUshi2q1KE+0uPgWBUGCpDVBdPl9pmjO8GXK
q63vIKzXtrE38UKtMxc9Lu+Ub1oj6C5i6g885WhAdUU9Txm0xfyc4DH0vXNiM1Dn
D/CEm13XaeA=
=d/GU
-----END PGP SIGNATURE-----

From nadeem.vawda at gmail.com  Fri Jun 29 14:27:52 2012
From: nadeem.vawda at gmail.com (Nadeem Vawda)
Date: Fri, 29 Jun 2012 14:27:52 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <4FED9D9B.9030609@jcea.es>
References: <4FECF570.1070202@jcea.es> <jsjnms$o55$1@dough.gmane.org>
	<4FED9D9B.9030609@jcea.es>
Message-ID: <CANF4RMnLrfW8hruEeHU6sPcPpTmtQ+XE8JtH495L-wGwm+vdwQ@mail.gmail.com>

On Fri, Jun 29, 2012 at 2:20 PM, Jesus Cea <jcea at jcea.es> wrote:
> On 29/06/12 10:07, Georg Brandl wrote:
>> And as Ross says: you *can* use the buildbots for personal
>> branches.
>
> I missed that. How is it done?.

Go to one of the "custom" builders at
http://buildbot.python.org/all/waterfall, for example
http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%20custom.
Then fill out the "Force build" form with the details of your sandbox
repository on hg.python.org.

Unfortunately, it looks like most of the custom builders are currently
offline, but I assume that's a transient issue related to the recent
change in the location of the buildbot master.

Cheers,
Nadeem

From solipsis at pitrou.net  Fri Jun 29 14:34:40 2012
From: solipsis at pitrou.net (Antoine Pitrou)
Date: Fri, 29 Jun 2012 14:34:40 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <CANF4RMnLrfW8hruEeHU6sPcPpTmtQ+XE8JtH495L-wGwm+vdwQ@mail.gmail.com>
References: <4FECF570.1070202@jcea.es> <jsjnms$o55$1@dough.gmane.org>
	<4FED9D9B.9030609@jcea.es>
	<CANF4RMnLrfW8hruEeHU6sPcPpTmtQ+XE8JtH495L-wGwm+vdwQ@mail.gmail.com>
Message-ID: <1340973280.3387.1.camel@localhost.localdomain>

Le vendredi 29 juin 2012 ? 14:27 +0200, Nadeem Vawda a ?crit :
> On Fri, Jun 29, 2012 at 2:20 PM, Jesus Cea <jcea at jcea.es> wrote:
> > On 29/06/12 10:07, Georg Brandl wrote:
> >> And as Ross says: you *can* use the buildbots for personal
> >> branches.
> >
> > I missed that. How is it done?.
> 
> Go to one of the "custom" builders at
> http://buildbot.python.org/all/waterfall, for example
> http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%20custom.
> Then fill out the "Force build" form with the details of your sandbox
> repository on hg.python.org.
> 
> Unfortunately, it looks like most of the custom builders are currently
> offline, but I assume that's a transient issue related to the recent
> change in the location of the buildbot master.

Uh? Most of them are online:
http://buildbot.python.org/all/waterfall?category=custom.stable&category=custom.unstable

Those which are offline are because the buildslaves themselves are
offline.

Regards

Antoine.



From nadeem.vawda at gmail.com  Fri Jun 29 15:05:10 2012
From: nadeem.vawda at gmail.com (Nadeem Vawda)
Date: Fri, 29 Jun 2012 15:05:10 +0200
Subject: [python-committers] Cutting 3.3 branch now. Why not?
In-Reply-To: <1340973280.3387.1.camel@localhost.localdomain>
References: <4FECF570.1070202@jcea.es> <jsjnms$o55$1@dough.gmane.org>
	<4FED9D9B.9030609@jcea.es>
	<CANF4RMnLrfW8hruEeHU6sPcPpTmtQ+XE8JtH495L-wGwm+vdwQ@mail.gmail.com>
	<1340973280.3387.1.camel@localhost.localdomain>
Message-ID: <CANF4RMmB6zb+dP8hQrQNKtju=F=2BMJ-SqxcCkeuJO8k2nZhqQ@mail.gmail.com>

On Fri, Jun 29, 2012 at 2:34 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> Uh? Most of them are online:
> http://buildbot.python.org/all/waterfall?category=custom.stable&category=custom.unstable
>
> Those which are offline are because the buildslaves themselves are
> offline.

Oops, my mistake. I should have read more carefully...