issue_comments: 844423790
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/5298#issuecomment-844423790 | https://api.github.com/repos/pydata/xarray/issues/5298 | 844423790 | MDEyOklzc3VlQ29tbWVudDg0NDQyMzc5MA== | 5635139 | 2021-05-19T19:56:08Z | 2021-05-19T19:56:54Z | MEMBER | From https://github.com/pydata/xarray/pull/4753#issuecomment-841894087
I am keen on whatever lets us release faster and easier — very open to a set schedule. Releasing has got to a place such that increasing the frequency isn't costly. The recent work by @andersy005 and others to automate PyPI has made that even more so. There are some smaller tasks we can put into pipelines if we want to squeeze more out there (e.g. updating stable branch, adding contributor lists). The only really necessary tasks are writing the summary, organizing the whatsnew, sending out communications. There's an extreme end of "constantly release new main branches". I don't see anything functionally wrong with that, but I'm sure there are unexplored consequences, and I'm not sure our role is to forge a new path in OSS release cycles. So maybe monthly is a reasonable balance? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
891200849 |