pull_requests: 1332026498
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1332026498 | PR_kwDOAMm_X85PZRyC | 7793 | closed | 0 | adjust the deprecation policy for python | 14808389 | As discussed in #7765, this extends the policy months by 6 to a total of 30 months. With that, the support for a python version can be removed as soon as the *next* version is at least 30 months old. Together with the 12 month release cycle python has, we get the 42 month release window from NEP 29. Note that this is still missing the release overview proposed in #7765, I'm still thinking about how to best implement the automatic update / formatting, and how to coordinate it with the (still manual) version overrides. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] towards #7765, closes #7777 - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` | 2023-04-28T15:03:51Z | 2023-05-02T11:51:27Z | 2023-05-01T22:26:55Z | 2023-05-01T22:26:55Z | 6d17fa0bea187ccba7247dd2bd9b6179636017b0 | 0 | e8ff9fe1341ec024df4924d559d92f7a9f66c93a | 087ebbb78668bdf5d2d41c3b2553e3f29ce75be1 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/7793 |
Links from other tables
- 1 row from pull_requests_id in labels_pull_requests