Semantic Versioning

[bzgec]

I see that this repository now uses versioning/tags. I think that it would be appropriate to use Semantic Versioning.
As far as I know this is quite a standard for bigger projects (including lvgl - see lvgl tags).

To summarize Semantic Versioning:

Given a version number MAJOR.MINOR.PATCH, increment the:

1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards compatible manner, and
3. PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

[stale]

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tore-espressif]

Commenting to remove stale label.

[stale]

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[septatrix]

Still relevant

[C47D]

@tore-espressif @kisvegabor I guess we could work on this, maybe making a new branch called v7.x, this branch will support LVGL v7.11. The master branch would keep the development for supporting LVGL v8.x, once we achieve it we could make a new branch named v8.x, leaving the master branch for development.

What do you think?

[kisvegabor]

I like this idea. It'd be in sync with the branch names of lvgl repo.

[C47D]

I already have a branch with v8 support, it might be matter of making sure we follow the same naming convention. I will wait for @tore-espressif opinion.