issue_comments

Table actions

4 rows where issue = 891200849 and user = 5635139 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • max-sixty · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
844460467 https://github.com/pydata/xarray/issues/5298#issuecomment-844460467 https://api.github.com/repos/pydata/xarray/issues/5298 MDEyOklzc3VlQ29tbWVudDg0NDQ2MDQ2Nw== max-sixty 5635139 2021-05-19T20:47:13Z 2021-05-19T20:47:13Z MEMBER

I'm curious.. How are these "new main branches" different from git tags from releases?

I had meant commit rather than branch — i.e. "on every commit to master". But as a thought experiment rather than a proposal

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.18.1 patch release? 891200849
844423790 https://github.com/pydata/xarray/issues/5298#issuecomment-844423790 https://api.github.com/repos/pydata/xarray/issues/5298 MDEyOklzc3VlQ29tbWVudDg0NDQyMzc5MA== max-sixty 5635139 2021-05-19T19:56:08Z 2021-05-19T19:56:54Z MEMBER

From https://github.com/pydata/xarray/pull/4753#issuecomment-841894087

I wonder if we should hold off on merging until after the 0.18.1 release -- or maybe just move to a date based versioning system / release cycle like dask.

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
}
   0.18.1 patch release? 891200849
843799396 https://github.com/pydata/xarray/issues/5298#issuecomment-843799396 https://api.github.com/repos/pydata/xarray/issues/5298 MDEyOklzc3VlQ29tbWVudDg0Mzc5OTM5Ng== max-sixty 5635139 2021-05-19T06:53:12Z 2021-05-19T06:53:12Z MEMBER

This is done. I'll send an email & check the docs are working tomorrow. Let me know anything I missed!

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 1,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.18.1 patch release? 891200849
840733277 https://github.com/pydata/xarray/issues/5298#issuecomment-840733277 https://api.github.com/repos/pydata/xarray/issues/5298 MDEyOklzc3VlQ29tbWVudDg0MDczMzI3Nw== max-sixty 5635139 2021-05-13T18:04:52Z 2021-05-13T18:04:52Z MEMBER

I can "do the release" if that's helpful

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 1,
    "eyes": 0
}
   0.18.1 patch release? 891200849

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]);