Release r1.1 with 0.1.0-alpha.1

[YadingFang]

Preparing all files for r1.1 with 0.1.0-alpha.1 versions.

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

Prepare the release r1.1:

• Update CHANGELOG.md
• Update click-to-dial.yaml
• Set versions in all files

Which issue(s) this PR fixes:

Fixes #33

Special notes for reviewers:

[hdamker]

Some comments. They don't need necessarily be addressed for an alpha release, you can alternatively set the lines 2 and 3 within the readiness checklist to "N".

[hdamker]

Please touch the README.md of the repository and uncomment the line

[hdamker]

Please delete the "README.md" placeholder files in API_definitions and API_documention

[YadingFang]

@hdamker, I have made revisions based on your suggestions, thank you!

[hdamker]

@YadingFang We are getting there ... thanks for addressing my previous comments. Please find a few new ones.

[hdamker]

Accidentally approved previously.

See the above comments. Some of them should be addressed before the release.

[YadingFang]

@hdamker, I‘ve finished the revisions based on your recent comments. Please take a moment to review them.

[hdamker]

I will stop here to dig into more details, as an alpha version it looks good to me.

Going forward you might want to revisit documentation/API_documentation/click-to-dial_API.md ... it's not in line with the API anymore and a lot of the information could be embedded into the API definition (where it will be available directly together with the API definition within tools like Swagger or Redoc). Examples how to use the API might be still valuable within the doc file.

[YadingFang]

I will stop here to dig into more details, as an alpha version it looks good to me.

Going forward you might want to revisit documentation/API_documentation/click-to-dial_API.md ... it's not in line with the API anymore and a lot of the information could be embedded into the API definition (where it will be available directly together with the API definition within tools like Swagger or Redoc). Examples how to use the API might be still valuable within the doc file.

Thanks, we'll work on it in the next release version. Now I'll put it into a new issue first.

[HanbaiWang]

LGTM

[YadingFang]

I will stop here to dig into more details, as an alpha version it looks good to me.

Going forward you might want to revisit documentation/API_documentation/click-to-dial_API.md ... it's not in line with the API anymore and a lot of the information could be embedded into the API definition (where it will be available directly together with the API definition within tools like Swagger or Redoc). Examples how to use the API might be still valuable within the doc file.

@hdamker, one more question, if we put the important information from /API_documentation/click-to-dial_API.md into /API_definitions/click-to-dial.yaml, can we delete /API_documentation/click-to-dial_API.md, or should we update it to match the /API_definitions/click-to-dial.yaml file?

[hdamker]

I will stop here to dig into more details, as an alpha version it looks good to me.
Going forward you might want to revisit documentation/API_documentation/click-to-dial_API.md ... it's not in line with the API anymore and a lot of the information could be embedded into the API definition (where it will be available directly together with the API definition within tools like Swagger or Redoc). Examples how to use the API might be still valuable within the doc file.

@hdamker, one more question, if we put the important information from /API_documentation/click-to-dial_API.md into /API_definitions/click-to-dial.yaml, can we delete /API_documentation/click-to-dial_API.md, or should we update it to match the /API_definitions/click-to-dial.yaml file?

@YadingFang there shouldn't be duplication of documentation, so if all information fits from the click-to-dial_API.md fits into the YAML, then you can delete it. The practice has shown that the risk of outdated documentation is much lower if it stays within the YAML. But if there is supplementary information left (e.g. a tutorial how to use the API or other background documentation) you can as well keep it.