search

renesas-rx / amazon-freertos

A fork/prototype of the Amazon FreeRTOS to support Renesas RX MCUs. Please refer to our wiki for more details.
https://github.com/renesas-rx/amazon-freertos/wiki
MIT License
7 stars 6 forks source link

Amazon FreeRTOS for Renesas MCUs versioning (release tags name) #15

Open HirokiIshiguro opened 4 years ago

HirokiIshiguro commented 4 years ago

Is your feature request related to a problem? Please describe.
Current release tags naming is not good. For example, we do not know reference Amazon FreeRTOS version from current release tags.

Describe the solution you would like.
Following scheme is good.

<aws_version> - <device_name> - <renesas_version> e.g. v1.4.9-rx-0.1.13, 201906.00_Major-rx-0.1.15, 201906.00_Major-rz-0.0.1

Additional context
None

HirokiIshiguro commented 4 years ago
Please refer to the Semantic Versioning 2.0.0 to know basic rules of this versioning. [Semantic Versioning 2.0.0](https://semver.org/) v1.4.9 or 1.4.9 are not clear. We follow Amazon as first. We follow Semantic Versioning as second.
HirokiIshiguro commented 4 years ago
is basically device family name. But it is OK group name for example rza2m. rx rza2m rl78
HirokiIshiguro commented 4 years ago

GitHub REST API cannot detect tag name without "v" in head of tag name. For example: "v1.4.9-rx-0.1.13" can be detected. "201906.00_Major-rx-0.1.15" cannot be detected. "201906.00_Major-rz-0.0.1" cannot be detected.

e2 studio uses GitHub REST API to get tag name to download. So, the tag name without "v" in head is not good for e2 studio.

So, we re-define like:

If includes "v" in head:

-- If does not include "v" in head: "v"-- For example: "v1.4.9-rx-0.1.13" "v201906.00_Major-rx-0.1.15" "v201906.00_Major-rz-0.0.1"
HirokiIshiguro commented 4 years ago

We found "v" is not mandatory for GitHub REST API, for example Amazon can do this. https://api.github.com/repos/aws/amazon-freertos/tags --> includes "name": "201906.00_Major".

I do not know why. Anybody knows answer? We keep "v" in head as temporary.