2020 Core Dev Sprint Location & Date

Hello everyone!

Let’s start planning the 2020 Core Dev Sprint! Some things to consider:

  • Date: Last few years we’ve been having it the second full week of September. Do we want to keep the same timeframe or change it to October/November?
  • Location: In 2019 it was in the UK, we should consider a different region this year. This also ties into which organization can help host/sponsor* the event. Is anyone aware of other organizations wanting to host/sponsor?

*Hosting involves providing space for 40+ core developers, breakfast, and lunch daily for 5 days. It is ideal if the organization can also help the PSF fund some of the travel/hotel costs in addition. Additionally, there should be a core dev involved to help with the RSVP process and work on creating the schedule.

If folks have any thoughts, comment here or email me.

5 Likes

Ewa started this thread in response to me piping up as looking to have Google host the sprint this autumn. :slight_smile: I’m following up on everything needed to make that happen internally (local managers supportive, likely feasible, but nothing guaranteed at the moment).

It’d likely be in Sunnyvale, California as that is where I and most of our Python and other languages teams are based.

As far as dates go, I suggest maybe October or early November as that is half way between PyCon 2020 and 2021 and avoids some potential non-python related plans I have mid September.

Looking at the PEP-596 release calendar, 3.9 will be squarely in bugfix-only and release mode this autumn regardless of which date we choose.

Others with venues should also feel free to also propose hosting arrangements.

4 Likes

I personally don’t care. This far out means there’s almost always going to be a conflict.

2 Likes

I’m trying not to miss Canadian thanksgiving with my family for second year in a row, (Monday Oct 12) but otherwise any time October/nov is fine. September is ok too. Thanks.

1 Like

Currently looking into October 19-23 as it appears to avoid holidays and election days and anything listed on https://www.python.org/events/.

3 Likes

(I’m thinking aloud about the date.)

Usually, tons of new features land during the core dev sprint. Some sprints were disaster in term of short term stability: new features means “tons of large changes” merged in a short time. Each change comes with its bag of tiny regressions.

Since PEP 602 (Annual Release Cycle for Python), I’m no longer sure how we should synchronize the sprint with the release. Is it better to land new features at the beginning of a new release, or just before the feature freeze? I guess that a reasonable release manager would prefer the beginning of a dev cycle: so after 3.9 feature freeze for example.

In term of communications, it might be interesting to “launch” a new dev cycle by merging new features. It makes the future release more attractive. Anyway, users would only have to wait for 12 months to get them in the worst case, thanks to PEP 602 :slight_smile:

The other side that if we add attractive features to 3.10 while 3.9 is being stabilized, 3.9 may look less attractive…

A compromise may be to organize the sprint after 3.9.0 release to really “launch” the 3.10 dev cycle (even if technically, it started at the first 3.9.0 beta). So after “3.9.0 final: Monday, 2020-10-05”. Sometime between October 2020 and May 2021?

Some core devs like to fix bugs during the core dev sprints, but in my experience, most core devs prefer to push features. Bugs can be fixed anytime, there is less need to organize a physical meeting for that. Features require discussions and coordination: physical meetings are great for that!