document Zephyr base and maintenance

[orangecms]

In order to fulfill SBoM requirements, please document the commit in Zephyr this project is based on, how to maintain it, and who the maintainers are.

Suggestion: Create a MAINTENANCE.md, and a HISTORY.md for tracking.

[orangecms]

Note: This was in part addressed in f7350a3.

[orangecms]

Here is a suggestion to simplify tracking upstream:

1. fork Zephyr (instead of copying) to another repo
2. put your changes on top
3. tag a release
4. include the tagged release in a submodule here

Now for maintenance:

1. rebase your HEAD onto the newer Zephyr release/revision
2. append a release note to HISTORY.md each time doing so
3. tag the new release of your fork
4. update the submodule here

[vigneshs88]

Hi Daniel Maslowski,

Thanks for your suggestions. We are working on this. We will close this issue by End of Jan 2023.

Regards,
Vignesh

[vigneshs88]

Next release is planned in end of Feb/early March. These fixes will be part of the release.