GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Document CPython lifecycle periods of reduced core dev capacity · Issue #937 · python/devguide

Document CPython lifecycle periods of reduced core dev capacity #937

New issue
Copy link
New issue
Copy link
Closed as not planned
Closed as not planned
Document CPython lifecycle periods of reduced core dev capacity#937
Copy link

Description

@arhadthedev
arhadthedev
opened on Aug 18, 2022
Issue body actions

As one of the core developers commented:

We are currently busy with 3.11 release. It may take until 3.11.0 final before we come back to this patch.

Hovewer, seeing no publicly visible increase in CPython PRs, I had no idea that the pre-release period (few last betas and all release candidates?) is loaded. Only after becoming aware of current priorities I've got the idea that monthly massive bumping of all my PRs is counterproductive and just reduces the capacity even further.

I believe that such annual hot periods of Python lifetime should be documented in, for example, Lifecycle of a Pull Request section of the devguide. Probably, it can be published as a mapping of day&month spans to relevant affairs.

Activity

  1. terryjreedy commented on Aug 18, 2022

    @terryjreedy
    terryjreedy
    on Aug 18, 2022
    Member
    More actions

    I believe the 'we' in Heimes' comment referred pretty specifically to himself and G. Smith. Your PR is not labelled as 'bugfix' or 'feature'. Some devs focus on bugfixes during the beta period. Some devs (including me) are focusing on doc fixes during this first candidate period as that is what can be merged most easily. Others on final critical bugfixes. Others seem to be on 'vacation'. The devguide could point to the annual version cycle as having some effect on dev time, but it is hard to generalize across all of us.

    Reacted by Erlend E. Aasland, Jelle Zijlstra, Oleg Iarygin and Ezio Melotti
  2. ezio-melotti commented on Aug 19, 2022

    @ezio-melotti
    ezio-melotti
    on Aug 19, 2022
    Member
    More actions

    This will also need to be maintained and updated, and someone will have to link it from issues/PRs (possibly as a canned response), since it seems unlikely that contributors will go looking for it in the devguide. As Terry mentioned, we could point to the annual version cycle, but if contributors are not going to see the pointer then it's kind of moot doing it.

    I suggest closing this issue as not planned.

  3. arhadthedev
    closed this as completedon Aug 19, 2022
  4. ezio-melotti
    closed this as not plannedon Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.