issue_comments

Table actions

10 rows where author_association = "MEMBER", issue = 484711431 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 10 ✖

issue 1

  • 0.13.0 release · 10 ✖

author_association 1

  • MEMBER · 10 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
532485672 https://github.com/pydata/xarray/issues/3257#issuecomment-532485672 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUzMjQ4NTY3Mg== shoyer 1217238 2019-09-18T02:00:56Z 2019-09-18T02:00:56Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
532403088 https://github.com/pydata/xarray/issues/3257#issuecomment-532403088 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUzMjQwMzA4OA== shoyer 1217238 2019-09-17T21:08:54Z 2019-09-17T21:08:54Z MEMBER

@dcherian done! you should have permissions for both RTD and pypi now

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
532390716 https://github.com/pydata/xarray/issues/3257#issuecomment-532390716 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUzMjM5MDcxNg== shoyer 1217238 2019-09-17T20:34:50Z 2019-09-17T20:34:50Z MEMBER

Maintainers permissions enable: "Can upload releases for a package. Cannot add collaborators. Cannot delete files, releases, or the project."

I'm pretty happy passing that out to anyone interested :)

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 1,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
532384520 https://github.com/pydata/xarray/issues/3257#issuecomment-532384520 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUzMjM4NDUyMA== shoyer 1217238 2019-09-17T20:17:35Z 2019-09-17T20:17:35Z MEMBER

@dcherian (and anyone else who's interested) could you please send me your pypi and RTD account names?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
532290239 https://github.com/pydata/xarray/issues/3257#issuecomment-532290239 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUzMjI5MDIzOQ== shoyer 1217238 2019-09-17T16:09:48Z 2019-09-17T16:09:48Z MEMBER

OK, @max-sixty or @dcherian do one of you want to take the lead on issuing the release this time? Everything should be in the HOW_TO_RELEASE checklist, but I'm sure something will come up -- nonetheless, it's good to increase the bus factor!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
530123503 https://github.com/pydata/xarray/issues/3257#issuecomment-530123503 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUzMDEyMzUwMw== shoyer 1217238 2019-09-10T21:15:54Z 2019-09-10T21:15:54Z MEMBER

Yes, we can merge/rebase changes into "stable" even after cutting a release.

On Tue, Sep 10, 2019 at 1:56 PM Deepak Cherian notifications@github.com wrote:

On the other hand, I feel like most doc users are just looking at the "latest" docs

I'm not so sure of this. The default is stable. and it isn't very obvious how to change it.

We can also merge that branch multiple times...

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/3257?email_source=notifications&email_token=AAJJFVV7GENIIQAJJHZ73VDQJACZPA5CNFSM4IPDKA22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6MO3VI#issuecomment-530116053, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJJFVTWYNFSRJMKFL3GOFDQJACZPANCNFSM4IPDKA2Q . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
527992071 https://github.com/pydata/xarray/issues/3257#issuecomment-527992071 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUyNzk5MjA3MQ== shoyer 1217238 2019-09-04T17:00:21Z 2019-09-04T17:00:21Z MEMBER

I did some searching for "FutureWarning" and "DeprecationWarning", and turned up a bunch worth cleaning up for 0.13: https://github.com/pydata/xarray/issues/3280

Otherwise I think we're ready do a release?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
525380237 https://github.com/pydata/xarray/issues/3257#issuecomment-525380237 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUyNTM4MDIzNw== shoyer 1217238 2019-08-27T16:29:30Z 2019-08-27T16:29:30Z MEMBER

My experience has been that the manual processes (e.g., checking release notes, finishing up deprecation cycles) take up most of the effort of issuing a new release. The commands 4-9 take about 5 minutes to run. I agree that the main value of automation there would be reducing the likelihood of manual mistakes.

It looks like there's an experimental documentation builder for pull requests with read the docs. It would be interesting to explore using it in xarray: https://blog.readthedocs.com/building-docs-for-pull-requests/

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
524516543 https://github.com/pydata/xarray/issues/3257#issuecomment-524516543 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUyNDUxNjU0Mw== shoyer 1217238 2019-08-24T03:54:57Z 2019-08-24T03:54:57Z MEMBER

Also it would be great if you’d like to try going through the release process. We can potentially automate and/or remove some of those steps.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
524516433 https://github.com/pydata/xarray/issues/3257#issuecomment-524516433 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUyNDUxNjQzMw== shoyer 1217238 2019-08-24T03:53:59Z 2019-08-24T03:53:59Z MEMBER

There are couple of small fixes for sparse arrays with open pull requests. I would lean toward getting those in before the release.

One thing that would be especially helpful is finalizing some deprecations that have been open for a while, e.g., the removal of the inplace argument and sel_points().

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431

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