Closed alexjhawk closed 1 year ago
I misnumbered the last PR as No.3 when it should've been No.4, so this PR is No.5.
I've updated the previously mentioned PR timeline below:
Also, I imagine it's very possible that this PR will quickly grow in size during the review. To make things more manageable, if something has been resolved to your satisfaction, please feel free to 'Resolve conversation'. This will make the PR much easier to follow and hopefully ensure nothing gets buried or missed.
@it-hms @TomKimsey Apologies for another ping.
I meant to include the documentation link originally, but they are visible at https://hms-networks.github.io/IgnitionEwonConnector/.
I did not get a chance to fully review. I did not see any errors or anything that would require changes, but I did have some questions about should the code exit in some places.
Still reviewing, this is not forgotten.
I misnumbered the last PR as No.3 when it should've been No.4, so this PR is No.5.
I've updated the previously mentioned PR timeline below:
45 - Last significant PR, containing documentation and additional source code changes56 - Small follow-up pull request to perform code signing and official release.5a6a - Just prior to v2 release (or after, depending on time constraints), a patch should be performed to finalize the Ewon rebranding efforts.