issue_comments

Table actions

4 rows where issue = 940054482 and user = 35968931 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • TomNicholas · 4 ✖

issue 1

  • Release v0.19? · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
885938059 https://github.com/pydata/xarray/issues/5588#issuecomment-885938059 https://api.github.com/repos/pydata/xarray/issues/5588 IC_kwDOAMm_X840zleL TomNicholas 35968931 2021-07-23T22:09:02Z 2021-07-23T22:09:02Z MEMBER

Good news everyone! The release is done.

 
{
    "total_count": 2,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 2,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Release v0.19? 940054482
884543369 https://github.com/pydata/xarray/issues/5588#issuecomment-884543369 https://api.github.com/repos/pydata/xarray/issues/5588 IC_kwDOAMm_X840uQ-J TomNicholas 35968931 2021-07-21T22:38:57Z 2021-07-21T22:38:57Z MEMBER

Is this just blocking on #5495? What did we decide to do there?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Release v0.19? 940054482
881656736 https://github.com/pydata/xarray/issues/5588#issuecomment-881656736 https://api.github.com/repos/pydata/xarray/issues/5588 IC_kwDOAMm_X840jQOg TomNicholas 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
}
   Release v0.19? 940054482
881158084 https://github.com/pydata/xarray/issues/5588#issuecomment-881158084 https://api.github.com/repos/pydata/xarray/issues/5588 IC_kwDOAMm_X840hWfE TomNicholas 35968931 2021-07-16T03:58:39Z 2021-07-16T04:00:20Z MEMBER

I know I volunteered to do this release, but some of the PRs I wanted to include have taken longer than I thought they would (particularly #5571), and now I'm going to be away from a computer from tomorrow until near the end of next week.

Should we do the release soon anyway?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Release v0.19? 940054482

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);