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

[feat] Tag stable commits more frequently with OZW version #2042

Closed
robertsLando opened this issue Dec 20, 2019 · 2 comments
Closed

[feat] Tag stable commits more frequently with OZW version #2042

robertsLando opened this issue Dec 20, 2019 · 2 comments

Comments

@robertsLando
Copy link
Member

It is not very clear how to keep ozw updated to latest version, I opened an issue some weeks ago about this and I ended up using releases from http://old.openzwave.com/downloads/ but seems they are not updated very frequently.

I suggest to tag commits more frequently with partials versions to allow users to identify stable commits, actually only minor versions are tagged, why not tag also patch versions?

@Fishwaldo
Copy link
Member

The releases from old.openzwave.com are updated after going through build tests etc. There is nothing wrong there. The last commit to the master branch was 9th of December.

Its automated - and the build infra doesn't use Github releases etc for this. As mentioned countless times - stable, tested releases are on the downloads page.

@robertsLando
Copy link
Member Author

@Fishwaldo Is there any possibility to at least to tag stable releases? For stable I means releases that are puublished on old.openzwave.com, if you tag commits or (even better) you create a stable branch that is updated everytime a new release goes out it would be lot easier to handle. Thoughts?

OpenZWave/Zwave2Mqtt#626

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants