Open strawgate opened 4 weeks ago
@legrego after the config pr merges I think we're ready to start maintain a separate 1.0 branch? Or how do you want to handle that?
Once we have a 1.0 branch we can start merging floor support, the attribute trimming, etc, pull out the legacy index code, legacy config, etc to prepare for 2.0
Do we want to roll back the inclusion/exclusion change and save that for 2.0?
@strawgate maintaining a separate 1.0 branch makes sense to me.
Do we want to roll back the inclusion/exclusion change and save that for 2.0?
I don't mind leaving this in the 1.0
release. Breaking changes are allowed going from 0.x
-> 1.0
.
In preparation for bringing the integration to HASS I'd like to propose the following:
Release a 1.0 with the current capabilities
config
PR: https://github.com/legrego/homeassistant-elasticsearch/pull/272Considerations:
Begin work on a 2.0 release for GA: