8000 0.11.1 by balloob · Pull Request #935 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

0.11.1 #935

8000
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

Merged
merged 6 commits into from
Jan 19, 2016
Merged

0.11.1 #935

merged 6 commits into from
Jan 19, 2016

Conversation

balloob
Copy link
Member
@balloob balloob commented Jan 19, 2016

This will be a bugfix release to fix the following issues:

  • Fix: Telldus Live users could suffer from a race condition (@molobrakos)
  • Fix: Entity attribute types were not enforced which could result in non-string friendly name attributes, breaking the frontend (@rmkraus, @balloob)
  • Fix: MQTT would not re-subscribe to topics after losing connection (@balloob)
  • Fix: Allow forcing the v3.1 protocol for MQTT to work around an outdated Mosquitto package on Ubuntu 14.04 LTS (@balloob)
  • Fix: Add MySensors missing binary sensor types (@MartinHjelmare)

@MartinHjelmare
Copy link
Member

I just realized the mysensors sensors are missing some sensors types. Is there time for adding those, before you release 0.11.1?

It's binary sensors which I had planned to put in a new binary sensor platform, but then changed my mind and postponed that for later, and forgot about it.

* Add missing binary sensor types to sensor/mysensors.
* Remove unneeded pylint disable.
@balloob
Copy link
Member Author
balloob commented Jan 19, 2016

That's not how hot fixes are supposed to work… Merged it anyway as I don't see any harm in it.

balloob added a commit that referenced this pull request Jan 19, 2016
@balloob balloob merged commit a4ee2bd into master Jan 19, 2016
@MartinHjelmare
Copy link
Member

Do you mean it's not considered severe enough bug for hotfix? Thanks for merging anyway!

@balloob
Copy link
Member Author
balloob commented Jan 19, 2016

Yeah. Hot fixes should be used to fix issues that occurred after the last release that are blocking people from using the product in such a way that it cannot wait till the next release. The more stuff that goes into a hot fix, the higher the chances are you mess up something else, getting into a vicious circle.

@MartinHjelmare
Copy link
Member

Thanks for clarifying. I guess this was borderline case, cause I removed functionality that was working previously, by mistake, but it was contained to a few specific parts.

@balloob balloob deleted the 0.11.1 branch January 20, 2016 04:19
@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0