openHAB Milestone builds

Ooops Sorry! I was mistaking it was 2.5.0~S1566-1 (Build #1566) discussed here… my fault…
In my memories it was 2.5.0.M1 …sorry again for my brainsalad :wink:

So please ignore my above post…

I have a ton of automated tests for Mqtt to make sure the binding works in all official releases (milestone + point release). I cannot guarantee a working state for snapshots because other gears are shifting too, like the buildsystem as a recent example.

I’m already talking to various people about having bindings with their own release schedule. That cannot happen before 3.0 unfortunately.

6 Likes

Just wanted to check in and see if there was an updated ETA on 2.5 M2? I remember seeing a post a couple of weeks ago indicating that the new build system was nearing completion.

I need to make a jump and would like to jump forward to 2.5 M2.

Thanks,

Squid

2 Likes

Just track https://github.com/openhab/openhab-distro/issues/866 and you’ll be always up to date!

3 Likes

Issue 886 is closed.
It would be nice to know what’s missing to publish a new version.

I tried to get this going, but there have been very few responses…

What is the syntax to upgrade to 2.5.0.M1?
I tried passing 2.5.0.M1 and 2.5.0-M1 but the script fails:

openhab@pi-openhab ➜  sudo ./runtime/bin/update 2.5.0.M1

#########################################
       openHAB 2.x.x update script
#########################################

Making Temporary Directory
Downloading openHAB 2.5.0.M1...

curl: (22) The requested URL returned error: 404 Not Found
Download failed, version 2.5.0.M1 does not exist.
If you believe this to be an error, please check the openHAB website. (www.openhab.org)

Can someone estimate the release date for the 2.5 version?

Not at this time. There was a massive change to the build system that didn’t go smoothly. There was also the big merge of ESH back into OH. I believe the developers are currently working down a bunch of bugs that have been discovered to get to a more stable state before they make another milestone release.

Because of the lack of milestone releases, I don’t know if they plan on trying to stick to the roughly every six months release cycle for point releases.

2 Likes

I personally would rather they keep working toward a stable release rather than rushing to meet an artificial deadline.

3 Likes

You need to switch to the testing repo:


For manual installation just dl, unzip and put your config back in.

I would have liked to, but we already missed that - so it’s rather gonna be late summer. But as others said: Top priority is to get decent milestones build again. After this, we can decide on a release date.

You need to switch to the testing repo

This is only relevant for apt, but @dbadia is asking for the “plain” update script.
@dbadia: sudo ./runtime/bin/update 2.5.0.M1 is the correct version and it works for me. Not sure, why you get a 404… The requested url is https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/distro/openhab/2.5.0.M1/openhab-2.5.0.M1.zip, can you check whether you can reach it manually?

3 Likes

I am able to access it manually from the server. I downloaded 2.5.0.M1 manually and diffed the update script from the zip to the one in my install. My update script had bintray instead of jfrog. Copied the new script over and the update ran OK

2 Likes

I mentioned point releases over here Development and release process - changes to stable branches (apologies for cross posting if that isn’t allowed), but this seems to be the more relevant thread.

So we have a case now where the much improved mqtt support in 2.4 actually doesn’t work with Homie devices after an OH restart - MQTT 2.4 binding: Items go to UNDEF after reboot. I understand that the whole build system has seen significant changes due to ESH being phased out, but the fix for Homie devices is already in master and seems like probably the most important fix to get out.

Is it realistic to get such changes backported to 2.4.1 and a release cut? I am sure there are plenty of people who would very much prefer to stay on stable but still get fixes in.

Couldn’t people just use the newer binding?
I am running 2.5M1 with a couple of snapshot version bindings.
I think 2.5M2 (or 2.5 Release?) is pretty close anyway.

sorry for the trivial question, I’d like to update from the stable 2.4 version to the 2.5 snapshot version. Since it is the first time I upgrade with a snapshot, can I use these instructions?


thank you
David

Those instructions should work.

thanks

I think homie support is still broken even in current snapshots. Perhaps the specific problem you are referring to was fixed but it’s still not working dependably.

Of course, but instead of telling people to get random snapshot versions of the various bindings that have received fixes (which may be mutually conflicting), isn’t it a far better user experience to cut a new stable release?

I’m thinking something along the lines of what the KDE project does - one feature release every 4 months and then fixes in the point releases (5.16.1, .2, .3) in the weeks following a feature release.

Thanks - I haven’t tried the snapshots.