[python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California

[Łukasz Langa]

Update: the sprint is on!

Good news: Facebook is covering the venue, food and hotel costs. This is 
confirmed. I'm working on getting a PSF grant for flights like last year.

Please book your airplane tickets as soon as possible. Like last year, we can 
reimburse up to $500 for domestic roundtrip flights and up to $1500 for 
international roundtrip flights. If that’s not enough to get you to California 
and back, let me know and we’ll figure something out. Send me the receipts my 
way, you should get your money back before the event, preferably as soon as I 
get the grant wired. For sums smaller than $500, provide me with a PayPal 
e-mail. For larger ones, I will need your details to set up a wire transfer. I 
will use TransferWise for the latter to cut down the wire costs.  I recommend 
flying in on Sunday and flying out on Saturday.

Please DO NOT book hotels, Facebook is covering this, preferably in the same 
hotel as close to Facebook HQ as possible. NOTE: I cannot confirm your hotel 
room until I have your flight information.

Full list of confirmed attendance:
zware
ned-deily
ncoghlan
warsaw
benjaminp
tiran
ericvsmith
1st1
larryhastings
ericsnowcurrently
Mariatta
ezio-melotti
applio
nascheme
bitdancer
gvanrossum
gpshead
zooba
haypo
rhettinger

If for any reason you can no longer come, please let me know immediately.

- Ł



> On Jun 13, 2017, at 1:04 AM, Lukasz Langa  wrote:
> 
> Hello fellow committers!
> I'm organizing another core sprint this year to make Python 3.7 the best 
> release possible.
> 
> WHY:
> 1. Community.  The sprints at the end of PyCon are great but they mostly get 
> the same people in the room year after year.  Many of the most active 
> contributors never attend conferences.  My goal with this sprint is to bring 
> together many core devs who rarely if ever meet!
> 2. Focus.  When we have sprints at the end of a conference, many of us are 
> pretty tired and less productive than we could have been without the late 
> dinners, endless hallway sessions, and so on.  Some of the sprinters are 
> preoccupied with tutoring newcomers.  This sprint won't be after a major 
> conference, and it's only for seasoned CPython core devs--so get to work!
> 3. Communication. There are tremendous benefits to getting everyone together 
> in one big room.  Conversations that drag on on python-dev can be solved 
> quickly in person.  Even contentious debates become faster, easier, and more 
> civil.  And meeting face-to-face helps us all feel more connected to our 
> community.
> 
> WHY THE BAY AREA: We have a large population of core contributors here.  
> Also, I can arrange for Facebook to provide us a "war room" for the whole 
> week, with full access to the campus during the sprints. That includes free 
> food for breakfast, lunch, dinner, and snacks, compatible with almost any 
> dietary restrictions.
> 
> WHY EARLY SEPTEMBER: It's almost impossible to find a time that doesn't 
> overlap with a PyCon. This week worked well last year so we're redoing it 
> that way. Monday September 4 is Labor Day in the US, which may make it easier 
> for employees of US companies to attend, as they'd only be taking off four 
> days instead of five.
> 
> HOW LONG: A full week Monday, Sep 4 to Friday, Sep 8 evening. You can check 
> into your hotel the day before the sprint (Sunday, Sep 3) and check out the 
> day after (Saturday, Sep 9).
> 
> HOW BIG: No fewer than 10, no more than 20.  More than 20 people would be 
> great but it'd be hard for me to organize a sprint that big.
> 
> WHO PAYS: The venue, hotels, and food are provided by Facebook. I'm working 
> on getting flight reimbursements. Last year they were provided by the Python 
> Software Foundation. Anybody is free to waive their reimbursement.
> 
> PLEASE REPLY: If you're interested in attending and have the commit bit on 
> GitHub's python/cpython, fill out this Google Form:
> https://goo.gl/forms/MzrNtRe0NAmzvGwF2 
> 
> 
> DISCLAIMER: I'd like to be able to host everybody. However, if I receive more 
> than 20 applications, this is not going to be possible. In this case, the 
> following will happen:
> 
> 1. I will look at your current level of involvement in CPython development. 
> This includes metrics like commits / PRs, activity on the bug tracker and 
> python-dev, special role (release manager, infrastructure dev, etc.).
> 2. I will look at your sprint plan and ability to participate in the entire 
> sprint (per answers to the questions above).
> 3. I will gather all this data and leave the final decision to our Benevolent 
> Dictator (who is also attending the sprint). This is one of those occasions 
> where having a dictator is useful.
> 
> DON'T WAIT: September is closer than you think! Please let me know as soon as 
> possible so we can start setting up the event. I'm going to close the sign-up 
> form on June 23rd.
> 
> Organizational-ly yours,
> Ł
> Vice-Minister of Silly Sprints
> ___

[python-committers] Should I make a 3.4.7rc1 next weekend?

[Larry Hastings]

I'm scheduled to tag and release 3.5.4rc1 next weekend.  I've been 
releasing 3.4 and 3.5 at the same time for the last year; this is 
convenient for me as it halves the frequency with which I have to put on 
the "release manager" hat.


There are currently no scheduled dates to release 3.4.7.  The reason 
being that until very recently there was almost no work done in 3.4 
since 3.4.6 was tagged.  But!  The reason for /that/ was because of a 
change in the workflow: once we switched to Github, for branches that 
are in security-fixes-only mode, only the Release Manager is allowed to 
accept PRs into that branch.  It turned out there were a bunch of PRs 
waiting for my approval.


After a flurry of accepted PRs, I have now accrued about ten fresh 
security fixes in the 3.4 branch.  (Mostly from Victor, but also Serhiy, 
and one from Barry--thanks everyone!)  There are now no outstanding 
security fix PRs against 3.4.


Since I'm releasing 3.5.4rc1 next weekend, I wouldn't mind /also/ 
releasing 3.47rc1 next weekend.  That would put 3.4.7 final the same day 
as 3.5.4 final: just over three weeks from now, releasing on Sunday 
August 5.  I realize it's not much notice, and that's normally not how 
we do things in the CPython world.  (Sorry for the short notice--it's my 
fault for not adjusting to the new workflow quickly enough.)


Anyway the point of this email is to call for a vote.  Which of these 
statements do you agree with:


 * Larry should tag and release 3.4.7rc1 next weekend.
 * Larry should schedule 3.4.7rc1 for a month from now, to give people
   time to get their work in.

In particular, Victor and Serhiy, I'm interested in your votes.  You 
both get veto powers for the short notice--if either of you say "do it a 
month from now" then it'll be a month from now.



Also, if anybody has security fixes you want to get in to the next 
release of 3.4, but you haven't made a PR yet, please reply and describe 
them.  (Please reply to list if appropriate, but if it should be kept 
quiet please reply to me directly.)



Braising in my own juices at EuroPython,


//arry/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Reminder: 3.5.4rc1 will be tagged next Saturday, July 22 2017

[Larry Hastings]

Just a quick reminder. I'll be tagging 3.5.4rc1 next Saturday, July 22.  
3.5.4 final will be the last release of 3.5.4 that accepts bugfixes; 
after that, the 3.5 branch will transition to security-fixes-only mode.


If you have bugfixes you want to ship with 3.5.4, please get them 
committed in the next nine days.




Happy hacking,


//arry/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Should I make a 3.4.7rc1 next weekend?

[Victor Stinner]

I would love to have a new 3.4 release including all security fixes,
sure! It would reduce the number of known vulnerability in Python 3.4:

   http://python-security.readthedocs.io/vulnerabilities.html

2017-07-12 15:09 GMT+02:00 Larry Hastings :
> After a flurry of accepted PRs, I have now accrued about ten fresh security
> fixes in the 3.4 branch.  (Mostly from Victor, but also Serhiy, and one from
> Barry--thanks everyone!)  There are now no outstanding security fix PRs
> against 3.4.

Thanks for merging them ;-)

I would like to see my "[3.4] Backport CI config from master" PR
merged into 3.4 to get at least a check from Travis and AppVeyor that
there is no major regression on Linux and Windows:
https://github.com/python/cpython/pull/2475

If I recall correctly, it would be the first time that we have a CI
for a branch in security-fix only mode, no?

Victor
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Should I make a 3.4.7rc1 next weekend?

[Serhiy Storchaka]

12.07.17 16:09, Larry Hastings пише:
> Anyway the point of this email is to call for a vote.  Which of these
> statements do you agree with:
>
>   * Larry should tag and release 3.4.7rc1 next weekend.
>   * Larry should schedule 3.4.7rc1 for a month from now, to give people
> time to get their work in.

I'm for releasing 3.4.7rc1 next weekend. There were not much security 
issues and seems all worth fixes already are backported and merged in 
3.4 (thank you for merging them). The rest of the work can be done in 
few days.


I have just one suggestion. Issue26617 and issue28427 were not marked as 
security issues but they look like very bad bugs to me. They are hard to 
catch, can unexpectedly break any program that uses weakref and threads, 
and don't have workarounds. If you will decide to backport them I can 
help with backporting.


https://bugs.python.org/issue26617
https://bugs.python.org/issue28427

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California

[Ezio Melotti]

Hi,

On Wed, Jul 12, 2017 at 1:55 PM, Łukasz Langa  wrote:

> Update: the sprint is on!
>
> *Good news*: Facebook is covering the venue, food and hotel costs. This
> is confirmed. I'm working on getting a PSF grant for flights like last year.
>
>
Great news, and thanks for organizing the sprint!


> *Please book your* *airplane tickets* as soon as possible. Like last
> year, we can reimburse up to *$500* for domestic roundtrip flights and up
> to *$1500* for international roundtrip flights. If that’s not enough to
> get you to California and back, let me know and we’ll figure something out.
> Send me the receipts my way, you should get your money back before the
> event, preferably as soon as I get the grant wired. For sums smaller than
> $500, provide me with a PayPal e-mail. For larger ones, I will need your
> details to set up a wire transfer. I will use TransferWise for the latter
> to cut down the wire costs. * I recommend flying in on Sunday and flying
> out on Saturday.*
>
>
Other than the cost, are there any restrictions on the flight?  If possible
I would like to spend some more time in the US after the sprint.  By
booking the return flight on a later date the total price of the flight
should be similar if not cheaper.  Of course I'll take care of the hotel
and other expenses -- I don't want to take advantage of the PSF.  If that
is fine, I can contact you off-list and provide more information.

Both the SFO and SJC airports seem to be close to Menlo Park. Is there any
preference on the airport? Does the hotel provide any shuttle service?



> *Please DO NOT book hotels*, Facebook is covering this, preferably in the
> same hotel as close to Facebook HQ as possible. NOTE: I cannot confirm your
> hotel room until I have your flight information.
>
> *Full list of confirmed attendance:*
> zware
> ned-deily
> ncoghlan
> warsaw
> benjaminp
> tiran
> ericvsmith
> 1st1
> larryhastings
> ericsnowcurrently
> Mariatta
> ezio-melotti
> applio
> nascheme
> bitdancer
> gvanrossum
> gpshead
> zooba
> haypo
> rhettinger
>
>
This is quite an impressive list, I'm looking forward meeting you all!

Best Regards,
Ezio Melotti



> If for any reason you can no longer come, *please let me know immediately*
> .
>
> - Ł
>
>
>
> On Jun 13, 2017, at 1:04 AM, Lukasz Langa  wrote:
>
> Hello fellow committers!
> I'm organizing another core sprint this year to make Python 3.7 the best
> release possible.
>
> *WHY*:
> 1. *Community*.  The sprints at the end of PyCon are great but they
> mostly get the same people in the room year after year.  Many of the most
> active contributors never attend conferences.  My goal with this sprint is
> to bring together many core devs who rarely if ever meet!
> 2. *Focus*.  When we have sprints at the end of a conference, many of us
> are pretty tired and less productive than we could have been without the
> late dinners, endless hallway sessions, and so on.  Some of the sprinters
> are preoccupied with tutoring newcomers.  This sprint won't be after a
> major conference, and it's only for seasoned CPython core devs--so get to
> work!
> 3. *Communication*. There are tremendous benefits to getting everyone
> together in one big room.  Conversations that drag on on python-dev can be
> solved quickly in person.  Even contentious debates become faster, easier,
> and more civil.  And meeting face-to-face helps us all feel more connected
> to our community.
>
> *WHY THE BAY AREA*: We have a large population of core contributors
> here.  Also, I can arrange for Facebook to provide us a "war room" for the
> whole week, with full access to the campus during the sprints. That
> includes free food for breakfast, lunch, dinner, and snacks, compatible
> with almost any dietary restrictions.
>
> *WHY EARLY SEPTEMBER*: It's almost impossible to find a time that doesn't
> overlap with a PyCon. This week worked well last year so we're redoing it
> that way. Monday September 4 is Labor Day in the US, which may make it
> easier for employees of US companies to attend, as they'd only be taking
> off four days instead of five.
>
> *HOW LONG*: A full week Monday, Sep 4 to Friday, Sep 8 evening. You can
> check into your hotel the day before the sprint (Sunday, Sep 3) and check
> out the day after (Saturday, Sep 9).
>
> *HOW BIG*: No fewer than 10, no more than 20.  More than 20 people would
> be great but it'd be hard for me to organize a sprint that big.
>
> *WHO PAYS*: The venue, hotels, and food are provided by Facebook. I'm
> working on getting flight reimbursements. Last year they were provided by
> the Python Software Foundation. Anybody is free to waive their
> reimbursement.
>
> *PLEASE REPLY*: If you're interested in attending and have the commit bit
> on GitHub's python/cpython, fill out this Google Form:
> https://goo.gl/forms/MzrNtRe0NAmzvGwF2
>
> *DISCLAIMER*: I'd like to be able to host everybody. However, if I
> receive more than 20 applications, this is not going to be possible. In
> this case, the f