Currently i’m using the 2.2 Snapshot, almost everything works as expected.
Thanks to everybody involved.
What about after the 2.2 release?
Should i switch to the stable branch?
Will there be still bugfixes in the stable branch or is this an exclusive of the snapshot?
People are tracking this thread because it’s supposed to be about the 2.2 release. Your comments here, while interesting, are off topic.
I respectfully ask that you open a separate forum thread for discussing your topic. Thanks!
Is there a corresponding ESH 0.9 (or the beta version that will be included with 2.2) draft release notes? One thing that popped up on me recently, that is not really a breaking change but may raise concerns, is the deprecation of DateTimeType.calendar. I was recently surprised when I started seeing a lot of these validation issues in my logs when saving rules that use .calendar…
The method getCalendar() from the type DateTimeType is deprecated
It would be helpful if the ESH documentation would include alternatives for .calendar and .getCalendar.
This is great! Nice work all!
How does one go about switching versions?
Is there a link with steps?
I have some issues with groups needing a OH restart to populate changes. Are u guys aware if this might be addressed in the 2.2 release? Thanks
Is there a corresponding ESH 0.9 (or the beta version that will be included with 2.2) draft release notes?
No, we should add such stuff to the openHAB release notes.
I was recently surprised when I started seeing a lot of these validation issues
That’s a good point. Yes, it probably should be mentioned - I tried to do so here. Not sure if this has any further impacts; if so, feel free to amend the wiki page.
That depends on how you installed it. If it is a manual installation, simply get the latest snapshot from here. If you use APT, check out the docs on how to switch the apt repo that is used.
I have some issues with groups needing a OH restart to populate changes.
@waitz_sebastian There was a fix on that about a month ago. If you see critical issues still on the latest snapshots, please let me know, I am not aware of any.
We have the upgrade script in place since early this year (runtime/bin/update) - is that what you are looking for? The info still needs to be added to the release notes though.
There should also be a note about breaking changes in logging configuration. (see Karaf Upgrade)
Right, but the note might depend on the outcome of this issue. But yes, definitely something that needs to be mentioned. Feel free to add it to the wiki page yourself!
It would be also helpful to tell users running OH 2.0 (and may be even 1.x) what to do, e.g. refer to previous release notes or start from scratch.
Yes, the two choices you mention are probably the best advice we could give. Can you add something to the wiki on that? Thanks!
Thank you Kai! I am now running v 2.2 and everything is working so far. I will continue to test and share any feedback.
For others who might be unsure on how to switch, I documented the process here:
To late to submit a new binding for 2.2 I guess?
Considering the amount of bindings waiting for a review and merge, this would be unfair if you can get a merge in a week 
The IoT Marketplace is always open for submitting new bindings. 
I do wonder if there is a version compatibility check. People with OH 2.1 may end up with OH 2.2 only bindings and vice versa?
It appears that there is still a problem with the powerview binding. Please see
Problems with powerview - Could not set field value for field 'id': Can not set int field
Did you created an issue and tried to contact the author?
Merged!
Maybe a stupid answer, but I don’t know how.
The binding is maintained in the openhab2-addons repo on GitHub.
You can file the issue under this link: