Skip to content
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.

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

Release to pipy #244

Open
muschellij2 opened this issue Feb 26, 2024 · 6 comments
Open

Release to pipy #244

muschellij2 opened this issue Feb 26, 2024 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@muschellij2
Copy link
Contributor

muschellij2 commented Feb 26, 2024

Is there some guidance on when versions will be updated? Currently, the recommendation is to use:

pip install git+https://github.com/onnela-lab/forest

Which will install from GitHub, but the version hasn't changed in 3+ years (Nov 2020 commit): 063558c
where it set the (current) forest version) to 0.1.1:

version = '0.1.1',

which it is still currently at:
version='0.1.1',

Also, is there an intention to version this release to PiPy?

@muschellij2 muschellij2 added the bug Something isn't working label Feb 26, 2024
@hackdna
Copy link
Member

hackdna commented Mar 5, 2024

Hi John, thank you for using Forest and raising this issue. The library is under active development and you can get the latest code by using the develop branch as you described. We simply neglected bumping the version. We are aiming to have a more regular release schedule and publish the package to PyPI starting in the next couple of months.

@muschellij2
Copy link
Contributor Author

I understand, but it's really hard from a reproducibility perspective, especially as things are dropping/moving around and it makes it hard to publish with this method reliably

@hackdna
Copy link
Member

hackdna commented Mar 5, 2024

Yes, the develop branch is meant to support quick feature rollout. This is why we are planning to create tagged releases on the main branch on a semi-regular schedule going forward.

In the meantime, you can reference a particular commit during installation for better reproducibility, for example:

pip install git+https://github.com/onnela-lab/forest@e0bfab42f763e3c76676c5c5085c2b92a7e6e7db

@muschellij2
Copy link
Contributor Author

Agreed, but the issue with this is that we had people working on different commit IDs and it's non-trivial for some users to know their commit ID (e.g. pip freeze) versus all having version 0.1.1. My request was a simple version bump here and there to make it easier to track down issues.

@hydawo
Copy link
Collaborator

hydawo commented Sep 3, 2024

Hi @hackdna @biblicabeebli

Notes from our call on Fri 8/30/24 are here -https://cheddar-fur-3bc.notion.site/Forest-on-PyPi-b411191b931c41bf89dc5396584477aa?pvs=4

One item JP asked me to add is that we should include the screen-time repo in the official release of Forest 1.0. I'll keep you updated on the changelog progress. Thank you!

@hackdna
Copy link
Member

hackdna commented Nov 20, 2024

Published the first draft to TestPyPI: https://test.pypi.org/project/forest-analysis/0.1.1/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

3 participants