[Draft] Preparing for Home Assistant Inclusion

[strawgate]

trafficstars

In preparation for bringing the integration to HASS I'd like to propose the following:

Release a 1.0 with the current capabilities

• [x] Finish merging the config PR: https://github.com/legrego/homeassistant-elasticsearch/pull/272
• [x] Finish merging the documentation site: https://github.com/legrego/homeassistant-elasticsearch/pull/268
• [ ] Soak test the code base with a pre-release version
• [x] Convert include/exclude logic for datastreams pending discussion #273
• [x] #276
• [x] Create a 1.0 release of the Homeassistant-Elasticsearch integration

Considerations:

1. Should we consider requiring users to upgrade to 1.0 before upgrading to 2.0?

Begin work on a 2.0 release for GA:

• [ ] Remove Legacy index support (permissions checking, connection testing, old include/exclude logic, v1 docs, etc)
• [x] #279
• [ ] #278
• [ ] Drop support for 7.x
• [x] #277
• [x] #282
• [x] #275
• [ ] #280
• [x] #283
• [x] #284
• [x] #249
• [ ] #281

[strawgate]

@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?

[legrego]

@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.