issues: 1042652334
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1042652334 | I_kwDOAMm_X84-JZyu | 5927 | Release frequency | 35968931 | open | 0 | 11 | 2021-11-02T17:53:57Z | 2021-11-05T17:12:42Z | MEMBER | In issuing the last 2 xarray releases, I've noticed a pattern, that goes something like this: 1) We don't have a release for 3+ months, for no particular reason. 2) Someone realises they want a release, to fix a bug or make a new feature available. 3) That person announces that they would like a release. 4) Lots of people (myself especially) suggest all sorts of unfinished issues that they think could or should go into that next release. 5) The dev team end up spending the better part of a week trying to finish up all of these miscellaneous PRs. 6) Finally it is deemed "ready" in some fairly arbitrary way. 7) The release is made manually using the "16 easy steps". 8) No-one wants to think about releasing again for another 3 months... FrequencyI mentioned this to @rabernat and he suggested that we should be releasing much more frequently. If we released more regularly then we wouldn't have this effect of "oh and we should try to squeeze XYZ into this release". I think the majority of the time xarray's CI is passing, and even when it's not it's only 1 tiny fix away from passing. That means that we in theory could release the I also don't know of any downside to releasing very regularly (other than that someone has to issue the release). How about we try to release after each of the bi-weekly dev calls? We could make it an official part of the call to end by saying: - "any reason why we can't release right now?" - "no, CI is passing" - "okay [person] volunteers to click the button right after this meeting" That would immediately increase our release frequency by up to 6x. AutomationCan we automate any more steps of our release process? As far as I can tell the only steps that really need human intervention are - "write the release summary" and - "check that all the automated stuff went as expected". We could potentially still automate
- "add new section to the @pydata/xarray thoughts? |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5927/reactions",
"total_count": 4,
"+1": 4,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | issue |