home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 881656736

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/5588#issuecomment-881656736 https://api.github.com/repos/pydata/xarray/issues/5588 881656736 IC_kwDOAMm_X840jQOg 35968931 2021-07-16T19:05:37Z 2021-07-16T19:05:37Z MEMBER

@max-sixty I think it somewhat depends on the intended purpose of the release: new features or bug fixes? Here the primary motivation was a bug fix so I agree with you in this case.

On Fri, 16 Jul 2021, 12:31 Maximilian Roos, @.***> wrote:

I basically think we should never wait for PRs, or spend time "rounding them up" before doing a release. Stuff is going to go in at some point, and exactly when doesn't matter as much as reducing the burden of doing releases. Indeed — even if we're only attempting to reduce the time between code merging and being released — we'd arguably reduce that more by forgoing this rounding up effort, making releases easier and more frequent.

The only argument I can see is that it's some "call to action" that helps motivate people to push something over the edge.

(but not super confident and realize I am maybe contra-consensus, so weigh appropriately)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/5588#issuecomment-881639368, or unsubscribe https://github.com/notifications/unsubscribe-auth/AISNPI6RT2U2VKR5KPSTYLTTYB3JXANCNFSM5ABEGYEQ .

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  940054482
Powered by Datasette · Queries took 0.906ms · About: xarray-datasette