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.

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

Stable release #166

Closed
kjeldflarup opened this issue Dec 4, 2017 · 7 comments
Closed

Stable release #166

kjeldflarup opened this issue Dec 4, 2017 · 7 comments
Assignees
@jluebbe

Comments

@kjeldflarup
Copy link
Contributor

Is there a stable release of labgrid?

I tried to follow https://labgrid.readthedocs.io/en/latest/getting_started.html but ran into a version related error, and once that was fixed, I soon ran into another.
Then I also tried the docker image, but that also suffered from upgrade issues.

I'm trying to start using labgrid, and don't really want to be on the bleeding edge.
Thus I would like to know if there are some version recommendations regarding to labgrid, but certainly also regarding to which packages besides labgrid has been installed on my system.
@jluebbe jluebbe self-assigned this Dec 4, 2017
@jluebbe
Copy link
Member

jluebbe commented Dec 4, 2017

Yes, we had some issues with out dependencies (pytest, attrs and crossbar), and I'm not sure how to make sure that doesn't happen again. Probably we'll pin all dependencies for now. Then we can make a release that keeps working even if e.g. attrs or pytest change. If you join #labgrid on freenode, we'll try to help you get started.

One way or the other, I'll do a release soon. Just need to find some time to wrangle pypi again...

@leopck
Copy link
Contributor

leopck commented Feb 6, 2018

Any update on this? Would love to have a stable release to deploy labgrid in our side as well. It would help having a fixed version and fixed dependencies that is known to work so that we could deploy in multiple sites for us.

@Emantor Emantor mentioned this issue Feb 12, 2018
Closed
@krevsbech
Copy link
Collaborator

Would it be possible/beneficial to do a minor release tag eg. v0.1.1 from current master as the dependencies seems to be pined in requirements.txt.
This would allow the use of a released and reproducible environment ?

@Bastian-Krause
Copy link
Member

@jluebbe released v0.2.0. I guess we will not do stable releases in the near future.

@bgermann
Copy link
Contributor

Will you release v0.2.0 on PyPI as well?

@Emantor
Copy link
Member

Emantor commented Jul 5, 2019

The primary problem we have with PyPI is that we can't test the dependencies installed by Pypi. This is why our official documentation recommends the installation into a virtualenv using the requirements files. I can see however that pushing to pypi would be beneficial.

@ejoerns ejoerns mentioned this issue Mar 12, 2020
Closed
@Emantor
Copy link
Member

Emantor commented Jan 16, 2021

I just struggled with the github interface to create a v0.3.0-rc1, I will release the final version on friday next week.

@Emantor Emantor closed this as completed Jan 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jluebbe jluebbe

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@Emantor @jluebbe @leopck @bgermann @krevsbech @Bastian-Krause @kjeldflarup