Skip to content
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

[Draft] Preparing for Home Assistant Inclusion #274

Open
12 of 18 tasks
strawgate opened this issue Apr 19, 2024 · 2 comments
Open
12 of 18 tasks

[Draft] Preparing for Home Assistant Inclusion #274

strawgate opened this issue Apr 19, 2024 · 2 comments

Comments

@strawgate
Copy link
Collaborator

strawgate commented Apr 19, 2024

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

Release a 1.0 with the current capabilities

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:

@strawgate
Copy link
Collaborator Author

strawgate commented May 1, 2024

@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
Copy link
Owner

legrego commented May 2, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants