Closed ayan-b closed 5 years ago
That's a good suggestion. Since this is for Xena, I'd like to check with @maryjgoldman or @jingchunzhu to see if this is what we want to have.
@yunhailuo also we need to add a LICENSE file. Which LICENSE does ucscxena follow?
This is a very legitimate suggestion. Again, @maryjgoldman or @jingchunzhu for proper license.
@yunhailuo ,I think Apache 2.0 as per this site: http://xena.ucsc.edu/ .
Yes, we use the Apache 2.0 license
@ayan-b Are you still working on this issue? If not, I would like to work on this issue.
@ayan-b Are you still working on this issue? If not, I would like to work on this issue.
Ideally maintainers should release to pypi.
No issues.
@ayan-b Are you still working on this issue? If not, I would like to work on this issue.
Ideally maintainers should release to pypi.
I have no problem releasing it. As mentioned in my first comment, I'd like to have confirmation from @maryjgoldman or @jingchunzhu.
Just realizing I never got back to you guys on this. I checked with Jing and she said this is fine to do.
Just realizing I never got back to you guys on this. I checked with Jing and she said this is fine to do.
Thanks for checking. I'll do a test release and we can take a look first, @maryjgoldman and @ayan-b
Test release to be reviewed: https://test.pypi.org/project/xena-gdc-etl/
I don't know enough about python to know if this works but the links above works and has a lot of great documentation. As we don't expect many people to interact with the code in this way, I vote we approve this and then if people complain then we can go back and change this.
One potential plan could be releasing this version at the end of GSoC as one end product, @maryjgoldman ?
How does this work? Like if we change the code, will the pypi package update as well? Or is more like we release our code to pypi?
No automatic update. Up to what we release (push). Usually a collection of mature codes for a release.
Gotcha. Then I defer to you, @yunhailuo, when we should release this. Should we put this back in the 'to do' queue until we're ready to release at the end of the project?
Thanks. Leave it there because the releasing command is ready. I will check the code and release when we get close to the end of the program.
The project can be released to pypi so that it can be easily downloaded by pip or other installers.