8000 Release 0.2? · Issue #52 · pydata/sparse · GitHub
[go: up one dir, main page]
Skip to content

Release 0.2? #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
hameerabbasi opened this issue Dec 28, 2017 · 13 comments
Closed

Release 0.2? #52

hameerabbasi opened this issue Dec 28, 2017 · 13 comments
Labels
discussion

Comments

@hameerabbasi
Copy link
Collaborator

I was wondering if it might be wise at this point to release version 0.2 (after my current pull requests have been merged). All major operations have been added.
@mrocklin
Copy link
Contributor
mrocklin commented Dec 28, 2017 via email

@hameerabbasi
Copy link
Collaborator Author
hameerabbasi commented Jan 2, 2018 •
edited
Loading

I keep thinking of more and more things to add. I think the library is in a pretty mature state. Once #60 is closed, and #43 is merged, I'd be comfortable releasing version 0.2.

Then, the only things left (in my mind) for 0.9-ish would be adding more methods from scipy.sparse, which would just call the scipy.sparse equivalents, and also adding a DOK class which could be "frozen" to or "unfrozen" from COO, which would only implement __setitem__.

@mrocklin
Copy link
Contributor

Version 0.2.0 is tagged released on PyPI

See https://github.com/mrocklin/sparse/blob/master/release-procedure.md and https://github.com/mrocklin/sparse/blob/master/docs/changelog.rst

@hameerabbasi
Copy link
Collaborator Author

I was wondering about uploading documentation. This should be done with the release.

@mrocklin
Copy link
Contributor
8000

Yeah, the question then becomes "where should this go?" Usually we would claim a name on readthedocs, like sparse.readthedocs.org. However this is taken. We would need to find a name. Alternatively, if the talks with NumFOCUS go anywhere then maybe we can claim the name sparse.pydata.org (though I'm not sure that they'll want that to happen).

cc @rgommers

@hameerabbasi
Copy link
Collaborator Author

Not to put you on the spot, but how long do these things usually take?

@mrocklin
Copy link
Contributor

Five minutes, once the necessary people all agree to decide to sit down and make a decision. I've just sent another e-mail on the NumFOCUS thread.

Also cc'ing @rgommers and @aterrel

@rgommers
Copy link

I think we're okay on the decision (@aterrel agreed?), just need to get you access to a repo and the domain name. I don't have admin access to those things myself. Hopefully @aterrel has time to do this, otherwise we need to ping another admin.

@mrocklin
Copy link
Contributor
8000 mrocklin commented Jan 25, 2018

I think that may already have persmissions to do this (Jeff Reback gave me access a while ago). I'm just waiting for authorization. It sounds like I have it from @rgommers . I've already spoken with @aterrel and he seemed fine with it as well, but I'll wait a few hours to give him a chance to change his mind.

@aterrel
Copy link
Member
aterrel commented Jan 25, 2018 via email

@mrocklin
Copy link
Contributor

I've moved this repository over to the pydata org.

I don't have access to the domain name though. Someone needs to do this: http://docs.readthedocs.io/en/latest/alternate_domains.html#cname-support . Andy, if you're busy I can ask around to see if I know anyone with access.

@mrocklin
Copy link
Contributor

https://sparse-nd.readthedocs.org

@mrocklin
Copy link
Contributor

https://sparse.pydata.org is live

@hameerabbasi hameerabbasi mentioned this issue Nov 9, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@aterrel @rgommers @mrocklin @hameerabbasi
0