issues: 1108564253
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1108564253 | I_kwDOAMm_X85CE1kd | 6176 | Xarray versioning to switch to CalVer | 2443309 | closed | 0 | 10 | 2022-01-19T21:09:45Z | 2022-03-03T04:32:10Z | 2022-01-31T18:35:27Z | MEMBER | Xarray is planning to switch to Calendar versioning (calver). This issue serves as a general announcement. The idea has come up in multiple developer meetings (#4001) and is part of a larger effort to increase our release cadence (#5927). Today's developer meeting included unanimous consent for the change. Other projects in Xarray's ecosystem have also made this change recently (e.g. https://github.com/dask/community/issues/100). While it is likely we will make this change in the next release or two, users and developers should feel free to voice objections here. The proposed calver implementation follows the same schema as the Dask project, that is; ```python In [1]: import xarray as xr currentIn [2]: xr.version Out[2]: '0.19.1' proposedIn [2]: xr.version Out[2]: '2022.01.0' ``` cc @pydata/xarray |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/6176/reactions", "total_count": 6, "+1": 6, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |